Crews
Build an expert once. Your whole team can ask it.
A Crew is an AI agent with your team's skills, tools and memory. Talk to it in Slack or WhatsApp like a teammate, or share it as an expert anyone can ask from Claude, ChatGPT, Cursor or the terminal.
Not just a skill
A skill tells an AI how. A Crew does it.
People already share skills: instructions you copy into your own AI. A Crew shares the whole expert instead, set up once by the team that knows the subject.
diagnose_service(name)Why not just share a skill?
| Shared skill | Crew | |
|---|---|---|
| Copies | Everyone installs their own | One live expert, asked by all |
| Updates | Goes stale on each laptop | Owners update once, for everyone |
| Your systems | Instructions only | Connected tools it can check |
| Memory | Forgets between chats | Keeps your team's knowledge |
| Control | Each person's own access | Scoped access, every call logged |
Illustrative conversation.
Three ways to use a Crew
One Crew. Wherever the work is.
A teammate in chat
Hand it a job in Slack or WhatsApp. It keeps one ongoing conversation, runs on schedules, uses its own browser and reports back when it's done.
An expert anyone can ask
Share it with your team. People ask it from Claude, ChatGPT, Cursor, Claude Code or Codex through MCP, or with
agentworks crews ask. Each person gets their own conversation.A specialist for your Goals
A Goal can hand a step to a Crew, like "write the first email", and Crews can call each other when a job needs a different specialist.
Inside a Crew
A specialist with a memory, a desk and a phone.
A crew is an agent turned into a long-lived teammate. It keeps its own workspace, skills and memory, has its own browser, answers in Slack or WhatsApp, runs on schedules, and can call other crews when a job needs a different specialist.
- AgentAny of the five native agents from Layer 1, with every command it runs sandboxed.
- SkillsPicks from your shared skill library and writes its own as it learns the job.
- MemoryA written memory of your customers, preferences and decisions, plus one ongoing conversation that survives restarts.
- WorkspaceIts own files, database and live dashboard.
- BrowserIts own managed browser for any web app, with a live view you can watch.
- ChannelsTwo-way Slack and WhatsApp. Gmail for updates and for mailbox work you grant.
- Crew-to-crewCrews call each other like colleagues: ask a question or call a typed function, each in its own private thread.
- Triggers & schedulesRuns on schedules, signed webhooks, function calls or a message in chat.
What teams build first
A library of experts. Owned by the teams who know best.
The owning team keeps improving each one, while everyone else just asks. Or start from one of 79 open-source premade Crew agents for sales, support, finance and operations.
- DevOps agent: deploys, pipelines, on-call runbooks
- Database agent: RDS and Postgres health, slow queries, safe changes
- Product agent: requirements, acceptance criteria, how a feature is tested
- Security agent: policies, approved libraries, review checklists
- Data agent: where a metric comes from and how to query it
- Onboarding agent: how the codebase, services and tools fit together
Control
Shared, not exposed. Every call on the record.
Scoped access
Admins issue tokens per person and per Crew. Revoking one stops its calls immediately.
Private by default
Callers get answers and the files owners choose to share, never the Crew's owner chats, database or settings.
Every call logged
Who asked, what the Crew did, which tools it used and what it cost.
FAQ
Crews, answered.
What is a Crew, exactly?
An AI agent set up as a long-lived specialist: one of the native agents (Claude Code, Codex, Cursor, Pi or Muse) with its own skills, memory, connected tools, browser and workspace. It keeps working on the same job and remembers what it learned.
How is a Crew different from a skill file?
A skill is instructions you copy into your own AI. A Crew is the whole expert: the agent, its skills, the tools it can check and the functions it offers. Owners update it once and everyone gets the new version.
Can I use a Crew without setting up a Goal?
Yes. A Crew works on its own. Talk to it in the app, in Slack or WhatsApp, or ask it from an MCP client. Goals can also hand steps to a Crew when you want both.
How do engineers reach a shared agent?
Through MCP from any client that supports it, such as Claude Code, Codex, Cursor, ChatGPT or Claude, or with the agentworks CLI. They can ask in free text or call its typed functions.
Can people see the agent's private data?
No. Callers get the agent's answers and the files its owners choose to share. Its chats with owners, its database and its settings stay private.
Who controls access?
Admins issue scoped tokens per person and per agent. Revoking a token stops its calls immediately, and every call is recorded.
Does every caller share one conversation?
No. Each caller gets their own continuing conversation with the agent, and the owners' main chat stays separate.
Can Crews work with each other?
Yes. A Crew can ask another Crew a question or call one of its functions, each in its own private thread, subject to the access you grant.
Pick one expert to share first. See it answer in week one.
We build your first Crew with the team that owns the knowledge, then connect it to the tools your people already use.