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.

vokal and paperclip
Paperclip handles async agent fleet orchestration — org charts, budgets, heartbeat execution, and governance. Vokal is the human-led product workspace above it: shared channels, real-time streaming, approval workflows, and team alignment around agent work as it happens.
Product teams assembling AI agents often need both: a fleet orchestration layer that handles async pipelines, cost guardrails, and task governance — and a live product workspace 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
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.
how they work together
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.
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.
Vokal's shared channels, live run timelines, and team memory keep humans coordinated around agent work. Decisions, approvals, and context accumulate in the workspace as the fleet runs.
faq
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.
Scope. Paperclip is built around each person's own team of agents — every user assembles their own org chart with budgets and async governance. Vokal puts everyone's agents in one shared team workspace — live channels, mid-flight intervention, and shared memory so your work and your teammates' work compound in the same place. The two can complement each other; they answer different questions.
Yes. Many teams use Paperclip for async per-person fleet orchestration (org charts, budgets, heartbeat pipelines) and Vokal for the human-led shared workspace above it — channels, streaming visibility, and mid-flight intervention when agents need human judgment.
Vokal provides the live product workspace where humans and agents collaborate: reasoning, tool calls, partial outputs, handoffs, and approvals stay visible as work happens. Paperclip explicitly rejects a chat surface and focuses on async task execution.
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.
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.
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.
public launch / 2026
Sign up if your team already runs AI agents and needs one shared place for live visibility, shared context, and mid-flight control.