Companies

The core idea

A company is a forkable manifest: roles, default agents, goal templates, MCP servers, skill bindings, an org chart. companies.sh is the public directory of these manifests. Clip is a runtime for them — fork one into a workspace and you have a working org in seconds.

Forking

Browse companies in-app, hit Fork, pick a workspace. The importer creates rows: roles, agents, goals, skills_installed. Existing rows aren't touched — forking adds, never overwrites.

You can fork the same company more than once (different workspaces, or two variants in one workspace with different role names). The manifest is a starting point, not a contract.

Why fork

Most agentic workspaces start with the same shape: a CEO/CTO/CMO ish org chart, a few standard agents, the same first ten skills. Companies.sh is that shape, shared. You don't have to design your org from scratch every time.

What we don't do (yet)

Publishing back. v1 is install-only. When publishing lands, it'll be a "PR your manifest to companies.sh" flow — until then, pretend that button doesn't exist.

Schema fidelity. We treat the manifest as a starting point. If companies.sh evolves the schema, we update the importer; we don't try to keep our internal tables 1:1 with the public format.

Tips and tricks

• After forking, audit the role permissions before inviting people. The fork is someone else's design.
• Rename the agents. "CEO Bot" from a manifest doesn't have your context — give it a name that signals which workspace it belongs to.
• If a company has skills you don't want, uninstall them after the fork. The fork is a one-time copy.

What's optional

All of it. You can build a workspace by hand, role by role, agent by agent. companies.sh is a shortcut, not a requirement.