# Team of agents

Source: https://corespeed.io/use-cases/team-of-agents

A team of agents on CoreSpeed is every teammate's own client, Claude Code, Codex, Cursor or claude.ai, signed in to one organization. Shared app connections, shared memory, the approval policy, spend caps and the activity trail belong to the organization, so the same rules hold whichever agent makes the call. A bot gets an identity of its own.

The job: Let each teammate keep their own agent while connections, memory, approvals, budgets and the trail are the organization's.

## The prompt

Paste this line into Claude Code, Codex or Cursor:

```text
set up https://corespeed.io/SKILL.md (read it raw, e.g. with curl), then tell me which app connections in our organization are shared and which are mine, and which agents exist and who owns them.
```

It starts with the setup line, so it works on a machine without CoreSpeed: the agent fetches https://corespeed.io/SKILL.md, adds the MCP server and signs you in, then does the job.

## Set up first

Each teammate adds CoreSpeed to their client once per machine and signs in to the same organization. An admin writes the approval policy in Dashboard → Approvals; a prompt cannot set it.

## The tools it calls

- `manage__whoami`: Confirm which organization you are in
- `manage__accounts_list`: Sort the connections: shared and yours
- `manage__agents_list`: List every agent and its owner

## Steps

1. **Everyone signs in once**: Each teammate adds CoreSpeed to Claude Code, Codex, Cursor or claude.ai and signs in to the same organization.
2. **Share what the team uses**: Connect GitHub and Notion as shared, and keep Gmail private. An admin installs the Slack or Linear app for the team.
3. **Give the bot its own key**: Create an agent for the nightly job and mint it a capped key. Its held writes come to you, its owner.

The full write-up: https://corespeed.io/blog/one-org-many-agents

## Questions

### Do teammates have to use the same agent?

No. Each teammate keeps their own client. The organization owns the shared state, and the MCP server is the same for every client.

### Do we still need our Claude or ChatGPT plans?

Yes, for the client each teammate uses. CoreSpeed adds what every agent shares: connections, memory, approvals, spend caps and one activity trail.

### Can the team's bot read a teammate's private Gmail?

No. An agent key reaches shared connections and accounts shared with that agent, never a member's other private ones.

### Can a teammate loosen the approval policy for themselves?

No. A member's own text only makes their own calls stricter. The organization's policy is the ceiling.

All use cases: https://corespeed.io/use-cases (Markdown: https://corespeed.io/use-cases.md)

## Related pages

- [Agent memory across chats and clients](https://corespeed.io/solutions/agent-memory): Keep preferences, project decisions, and shared team context in persistent memory across Claude Code, Codex, and Cursor.
- [Shared agent tools and controls for teams](https://corespeed.io/solutions/teams): Manage shared connections, approval policies, and tool usage for teams working across Claude Code, Codex, and other MCP clients.
- [Let a cloud agent use your Mac](https://corespeed.io/use-cases/cloud-agent-on-your-mac): Tie your Mac so a cloud agent can run commands, read files and use apps on it, sharing only what you turn on. One prompt to paste.
- [Continue a Claude Code task in Codex](https://corespeed.io/use-cases/continue-in-another-agent): Save where you are to memory in Claude Code, then pick the task up in Codex without explaining it again. What carries over, and what does not.
- [Connect two accounts of one app to your agent](https://corespeed.io/use-cases/two-accounts-one-app): Connect two Slack workspaces or two X handles to one agent, give each an alias, and send every call to the right account. One prompt to paste.
- [Run an unattended agent job with its own key](https://corespeed.io/use-cases/unattended-agent-job): Give a cron job or CI runner you host its own agent, a key with a monthly cap, and an owner who answers for it. One prompt to paste.

## Sources

- Authentication: https://corespeed.io/docs/authentication
- Connectors: https://corespeed.io/docs/connectors
- Approvals: https://corespeed.io/docs/approvals
- Activity: https://corespeed.io/docs/activity
- MCP: https://corespeed.io/docs/mcp
- One org, many agents: Claude Code, Codex and a bot on one rulebook: https://corespeed.io/blog/one-org-many-agents

Reviewed 2026-11-14.

## Links

- Product overview: https://corespeed.io/ (Markdown: https://corespeed.io/index.md)
- Documentation: https://corespeed.io/docs
- Pricing: https://corespeed.io/pricing (Markdown: https://corespeed.io/pricing.md)
