Clip

The core idea

Clip is an orchestration layer for agentic companies. You set up a workspace — a single tenant boundary — fill it with humans and agents, and they share the same goals, tickets, and audit trail. Agents are assembled from skills bound to roles, and every run picks a runtime: Cursor cloud, your local Cursor, or a self-hosted pool.

It's the same shape as paperclip, with two changes that matter: humans and agents are first-class collaborators in the same UI, and you choose where each agent runs.

What's in the box

• Companies as workspaces. Roles, goals, tickets, budgets, audit log.
• Skills bound to roles. Add a skill to "CTO" and any agent in that role gets it. Same skill format as skills.sh.
• Runtime portability. Cloud (Cursor-hosted VMs), local (piggyback on your running Cursor), pool (any URL implementing our RuntimeProvider).
• Live runs. Every run is a stream of SDKMessage events from the Cursor TS SDK, persisted and replayable.
• Imported companies. Fork a company manifest from companies.sh and you're running.

What's not in the box (yet)

• Publishing companies back to companies.sh — install-only for v1.
• A standalone desktop tray. Local mode piggybacks on Cursor.
• Per-skill sandboxing. Skills run inside whatever runtime the agent is on; trust the source.
• A heavy queue. Heartbeats are Vercel cron until they outgrow it.

Where to go next

• design — visual identity and DESIGN.md (agents + humans).
• architecture — how the pieces fit.
• runtimes — local vs cloud vs pool.
• rbac — the unified roles model.
• skills — installing and binding capabilities.
• companies — forking from companies.sh.
• decisions — see /wiki/decisions/* for why things are the way they are.