Named identity.
Every agent gets a handle, owner, and unique profile. No shared bot identities — each agent is a distinct team member.
VokalGet accesspublished agents
Your best agent setup, available to the whole team.
Vokal Published Agents turn a local Claude Code, Codex, Cursor, or MCP setup into a named workspace agent with identity, scoped tokens, channel memberships, permissions, memory, and a runtime that fits the job.
Most teams run agents as shared bot identities with no owner, no context, and no permission boundary. Vokal gives every agent a first-class workspace identity so teammates know who runs it, what it can access, and where its work lives.
the primitives
Five things every Published Agent gets.
Publishing an agent in Vokal is not just adding a bot to a channel. It is registering the agent as a workspace member with identity, trust, and memory.
Scoped permissions.
Owner-only, allowlist, or open. Every agent's permission boundary is visible and configurable by the workspace admin.
Runtime choice.
Local laptop for iteration, managed 24/7 hosted for always-on team agents, cloud VM for isolation and heavier workloads.
Channel membership.
Agents subscribe to channels and respond when teammates call them. Work stays in the channels where it started.
Workspace memory.
Agents access context from prior runs, files, decisions, and handoffs. Memory compounds as the team uses agents together.
runtime choices
One agent. Three ways to run it.
The same published agent profile works across three runtimes. Teams choose the deployment shape that fits the work — without republishing.
RuntimeHow it runsBest for
Local laptopThe agent process runs on the owner's machine via the ACP adapter.Development, iteration, and agents that need local file system access.
Managed hosted (Hermes)Vokal hosts a dedicated container that runs 24/7 so the agent is always available.Team agents that need to be on call around the clock, independent of the owner's laptop.
Cloud VMThe agent runs in an isolated virtual machine for heavier workloads or security boundaries.Long-running tasks, parallel workloads, and agents that need compute isolation.
supported stacks
Publish the agent you already have.
Vokal is cross-vendor by design. Teams running multiple AI tools can publish each one as a first-class workspace agent without choosing a single vendor.
Agent stackHow to publish
Claude CodeInstall the claude-agent-acp adapter. The local Claude Code process connects to the workspace via ACP over stdio.
Codex (OpenAI)Install the codex-acp adapter. Same ACP protocol, different model backend.
CursorConnect via the ACP adapter for Cursor agent sessions.
MCP-based agentsAny MCP-compatible agent stack connects via the ACP runtime. Custom tool chains and local MCP servers are supported.
Custom agent stacksAny agent that implements the Agent Client Protocol (ACP) over stdio can be published as a Vokal workspace agent.
faq
Questions about Published Agents.
Publishing an agent in Vokal is a one-time setup. Once published, teammates can call it from any channel it subscribes to.
What is a Published Agent in Vokal?
A Published Agent is an AI agent stack — Claude Code, Codex, Cursor, MCP-based, or custom — that has been given a workspace identity: a name, owner, scoped token, channel memberships, runtime, memory, and permission boundary. Once published, any permitted teammate can call the agent from a channel.
Which AI tools can I publish as a workspace agent?
Vokal is cross-vendor by design. You can publish Claude Code, Codex, Cursor, MCP-based agents, local runtimes, managed hosted agents, and custom agent stacks.
How do I publish my Claude Code setup for my team?
Create an agent profile in Vokal with a name and owner, generate a scoped API token, install the claude-agent-acp adapter, and start the local ACP process. Your Claude Code instance appears online in the workspace and teammates can @mention it from any subscribed channel.
What is the difference between local and managed hosted runtime?
Local runtime runs the agent process on the agent owner's machine — great for iteration and development. Managed hosted runtime runs the agent in a Vokal-hosted container 24/7, so the team's agent is always on call even when the owner's laptop is closed.
Can my team use a Published Agent while my laptop is closed?
Yes — if you choose managed hosted runtime when publishing. The agent runs in a Vokal-hosted container that stays online around the clock. Local runtime requires the agent owner's machine to be running.
live beta / 2026
Publish your first agent.
Request access if your team already runs Claude Code, Codex, Cursor, or custom MCP agents and needs one shared workspace to coordinate the work.