Agents and Claws
What an agent is, what a Claw executes, and how identity, instructions, Drive, Skills, and channels come together into one AI worker.
The bottleneck for most founders and small teams isn't ideas — it's hands. An agent is a pair of those hands: a focused AI worker you recruit once, direct in plain language, and reuse across many jobs. You decide the outcome; the agent does the work.
Agent vs. Claw
Two words, one idea seen from two angles:
- Agent — the role: an AI employee with a name, a mission, instructions, files, and connected channels. This is what you hire, configure, and review.
- Claw — the worker that executes: the same agent doing real work inside its cloud computer. When you watch a Claw run, you're watching your agent read files, browse the web, run code, and commit to Git.
You manage agents. Claws are how those agents get things done.
What an agent is made of
| Part | Role |
|---|---|
| Identity | Name, description, and the job the agent owns |
| Instructions | System prompt, behavior rules, and operating constraints |
| Cloud computer | An isolated, long-running sandbox the Claw works in |
| Drive | The agent's private file workspace and knowledge base |
| Skills | Extra capabilities and SOPs the agent can call |
| Channels | External surfaces — WhatsApp, Slack, Telegram — bound to the agent |
| Sessions | Independent conversation contexts created as you and others interact |
Where an agent sits
Space (your company)
└─ Agent (an AI employee)
├─ Cloud computer (where the Claw works)
├─ Drive (private files + knowledge)
├─ Skills (reusable SOPs)
├─ Channels (external entry points)
└─ Sessions (one per task or conversation)A Space can hold many agents, each focused on a different job — support, finance ops, recruiting, research, coding.
What each agent gives you
Recruiting an agent provisions three things:
- A dedicated cloud computer — isolated CPU, RAM, and persistent SSD for that agent.
- A human member seat — invite one teammate to collaborate with the agent.
- Monthly credits added to the Space pool — credits accumulate at the Space level, not as a per-agent cap. See credits and billing.
When to create a new agent
Create a separate agent when you need a different knowledge base, a different role or tone, different channel routing, or cleaner isolation between teams.
Don't over-split. If it's the same worker doing related jobs (blog, Xiaohongshu, LinkedIn), use multiple sessions under one agent. Split into a new agent only when identity, permissions, tools, and files all need isolation.
Good agent design
- Keep one agent focused on one job, with a clear name and mission.
- Put only the files it should actually use in its Drive.
- Install Skills deliberately instead of turning everything on.
- Connect channels after the core behavior is stable.