# Two accounts, one app

Source: https://corespeed.io/use-cases/two-accounts-one-app

Two accounts of one app, such as two Slack workspaces or a personal and a company X handle, sit under one CoreSpeed connector. Each account has an alias, and connector tools take an account argument that names it. With two in scope and none named, the call answers ambiguous_account and runs nothing.

The job: Connect two accounts of one app, name each one, and send every call to the right account.

## 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 name my two Slack accounts work and community, and post that office hours start at 3 in #general of community only.
```

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

Both accounts, connected in Dashboard → Connectors: connect Slack, then choose Add account on it for the second workspace. Your agent's connect link answers with the account you already have, so it cannot add a second.

## The tools it calls

- `manage__accounts_list`: List both accounts and their aliases
- `manage__accounts_rename`: Name them work and community
- `slack__post_message`: Post with account set to community

## Steps

1. **Connect both workspaces**: In Dashboard → Connectors, connect Slack, then choose Add account and authorize the second workspace.
2. **Name both accounts**: Paste the prompt. Your agent renames the aliases to work and community, short names a model types right.
3. **Name the account on each call**: Your agent passes account on every call. Left out with two in scope, the call answers ambiguous_account and nothing runs.

The full write-up: https://corespeed.io/blog/connect-two-accounts-of-the-same-app

## Questions

### What if my agent leaves out the account?

With one account in scope, the call uses it. With two or more, it answers ambiguous_account with the aliases, and nothing runs.

### Can the two accounts have different visibility?

On most apps, yes: each account is private or shared on its own. A Slack member account is private only; an admin installs the workspace bot for the team.

### Does my agent see account ids or tokens?

No. The alias is the whole address. CoreSpeed keeps each credential and gives your agent tools, never the token.

### How do I keep my agent on the right account?

Write the rule in your project's instruction file or in shared memory. For a hard stop, name the account in your approval policy.

Every tool and price: https://corespeed.io/catalog/slack

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

## Related pages

- [Slack for Claude Code, Codex, and Cursor](https://corespeed.io/integrations/slack): Bring the Slack conversation into your agent. Find the decisions, the open questions, and what happens next.
- [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.
- [Claude Code and Codex for teams, on one set of rules](https://corespeed.io/use-cases/team-of-agents): Each teammate keeps Claude Code, Codex or Cursor. Connections, memory, approvals, budgets and the activity trail are the organization's. One prompt to paste.

## Sources

- Connectors: https://corespeed.io/docs/connectors
- Authentication: https://corespeed.io/docs/authentication
- Errors: https://corespeed.io/docs/errors
- How to connect two accounts of the same app to one agent: https://corespeed.io/blog/connect-two-accounts-of-the-same-app

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)
