# Continue in another agent

Source: https://corespeed.io/use-cases/continue-in-another-agent

Continuing a task in another agent works because the state lives in your CoreSpeed organization, not in the client. Before you stop, Claude Code saves the decisions to memory; Codex searches memory and carries on. Connections and the approval policy carry over too. The conversation does not, so save what the next agent needs.

The job: Stop a task in Claude Code and pick it up in Codex, or the other way round, without explaining it again.

## 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 search memory for where I left the pricing page rewrite, and carry on from there.
```

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 clients signed in to the same CoreSpeed organization. The prompt above is the second half: the first half is typed in the agent you leave.

## The tools it calls

- `memory__remember`: Before you stop: save what is decided and open
- `memory__search`: In the next agent: find where you left off
- `memory__get`: Read a long memory in full

## Steps

1. **Save where you are**: In the agent you leave, type: Save where we are on the pricing page rewrite to memory: what is decided, what is open, and where the draft lives.
2. **Open the other agent**: Sign in to the same organization from Codex, Claude Code or Cursor. Your connections and approval policy are already there.
3. **Paste the prompt**: The new agent searches memory, finds the decisions and carries on. If it needs more, restate the task in one sentence.

The full write-up: https://corespeed.io/blog/continue-a-task-in-a-different-agent

## Questions

### Does the new agent see my old conversation?

No. It sees the memories you saved and the pinned index the server sends at the start. Save the decisions before you switch.

### What carries over besides memory?

App connections, the approval policy, spend caps and the activity trail. CLAUDE.md and AGENTS.md stay per repository and per client.

### Do I reconnect my apps in the new client?

No. Sign in to CoreSpeed from the new client and the same connections are there.

### Can a teammate continue my task in their agent?

Yes, when the memories are saved as shared and the connections are shared. Your private memories and private connections stay with you.

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

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.
- [Memory](https://corespeed.io/memory): The memory every agent shares. Say it once, to any agent, and every agent on your team remembers it. Searching is free.
- [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

- Memory: https://corespeed.io/docs/memory
- MCP: https://corespeed.io/docs/mcp
- Approvals: https://corespeed.io/docs/approvals
- Continue a task in a different agent without re-explaining: https://corespeed.io/blog/continue-a-task-in-a-different-agent

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)
