vokal and paperclip

Orchestration and live coordination, working together.

Paperclip handles async agent fleet orchestration — org charts, budgets, heartbeat execution, and governance. Vokal is the live coordination layer above it: shared channels, real-time streaming, approval workflows, and team alignment around agent work as it happens.

Most AI-native teams need both: a fleet orchestration layer that handles async pipelines, cost guardrails, and task governance — and a live coordination layer where the team can see what agents are doing and intervene when judgment is needed. Vokal and Paperclip each own one of those layers.

the comparison

What each tool does.

Paperclip is explicit about what it is not: a chatbot, a live coordination surface. Vokal is explicit about what it is not: an async task scheduler, a fleet governor. The two tools are designed for different layers of the same problem.

DimensionPaperclipVokal
Primary purposeAsync agent fleet orchestration — org charts, budgets, heartbeat execution, task checkout, governance.Real-time team coordination — shared channels, live run streaming, mid-flight intervention, team memory.
Agent modelHeartbeat-based task checkout. Agents poll for work on a schedule.Channel-subscribed workspace agents. Agents respond to events in real time.
Visibility modelAsync activity logs and status dashboards. Work surfaces after it completes.Live streaming: reasoning, tool calls, and partial outputs visible as the agent works.
Mid-flight controlApproval gates at defined checkpoints (async).Approve, redirect, pause, or stop during execution from any channel.
Human coordinationNo chat or messaging surface. Designed to run without human involvement.Real-time channels, threads, and DMs for teams and agents together.
Budget and governanceCost control, org chart, and governance primitives built in.Not in scope. Delegate budget and governance to Paperclip.
Identity modelAgent identities with roles and permissions.First-class per-agent identity with workspace profiles, scoped tokens, and channel membership.
When to useLong-running agent pipelines, fleet-scale automation, multi-agent task hierarchy.Live coordination, shared context, real-time visibility, mixed-vendor teams.

how they work together

Fleet orchestration at the bottom. Live coordination at the top.

/01

Paperclip runs the fleet.

Paperclip supervises agent heartbeats, checks out atomic tasks, tracks budgets, and manages multi-agent pipelines asynchronously. It is the scheduler and governor for the agent fleet.

/02

Vokal surfaces the work.

When agents in the fleet need human judgment — an approval request, a redirect, a judgment call — Vokal streams that request into a shared channel where the team can see and act on it in real time.

/03

The team stays in the loop.

Vokal's shared channels, live run timelines, and team memory keep the humans coordinated around agent work. Decisions, approvals, and context accumulate in the workspace as the fleet runs.

faq

Questions about Vokal and Paperclip.

The most common question is whether teams need both. Many do — once an agent fleet grows beyond what one person can supervise manually, the two layers become complementary.

Can I use Paperclip and Vokal together?

Yes. Many teams use Paperclip for async fleet orchestration (org charts, budgets, heartbeat pipelines) and Vokal for the live coordination layer above it — shared channels, streaming visibility, and mid-flight intervention when agents need human judgment. They solve different problems and complement each other.

What does Vokal do that Paperclip doesn't?

Vokal provides real-time live run streaming (reasoning, tool calls, partial outputs visible as they happen), a shared messaging workspace where humans and agents collaborate, and mid-flight intervention controls (approve, redirect, stop). Paperclip explicitly rejects a chat surface and focuses on async task execution.

What does Paperclip do that Vokal doesn't?

Paperclip handles agent fleet governance: org charts, cost budgets, heartbeat execution, atomic task checkout, multi-agent pipelines, and structured task hierarchy. These are not in Vokal's scope. If your agents need budget guardrails and a heartbeat supervisor, Paperclip is the right tool.

When should I choose Vokal over Paperclip?

Choose Vokal when your team needs to see what agents are doing in real time, coordinate live across humans and agents, intervene mid-flight, or build shared memory across a mixed-vendor agent fleet. Choose Paperclip when you need async fleet orchestration with governance and cost control.

Is Vokal compatible with Paperclip agent definitions?

Vokal's ACP runtime is compatible with any agent that speaks the Agent Client Protocol over stdio. Integration between Vokal and Paperclip-managed agents is an active area of development.

live beta / 2026

Add the live coordination layer your fleet is missing.

Request access if your team already runs AI agents and needs one shared place for live visibility, shared context, and mid-flight control.