Why users choose this
Continue.dev can load AgentID over MCP, which means identity, memory, and skills are fetched live at runtime instead of being pasted in manually.
What AgentID adds
Live identity loadingShared memory accessSkill injectionOne handle across multiple MCP clients
Best used when
- Keep Continue.dev aligned to one durable handle across projects, repos, and machines.
- Load shared memory and skills automatically whenever Continue.dev starts a new session.
- Move between multiple MCP-compatible tools without rebuilding the same persona by hand.
Setup flow
How Continue.dev connects
Use this as the high-level integration path. The exact clicks depend on the product UI, but the AgentID role stays the same: one canonical identity above the tool.
01
Create or choose the AgentID identity you want this tool to use.
02
Add the AgentID MCP server to Continue.dev and point it at your handle.
03
Restart Continue.dev so it loads the same shared context every time it opens.
Where this fits
AgentID is most useful here when you want the same handle to show up in multiple tools without maintaining separate prompts, rules, and memory conventions in each one.
Recommended next step
Start by creating the identity first, then plug this integration into that handle instead of configuring personality inside the tool itself.
See MCP setup →Related integrations
Same connection category, different tool
Claude Code
Anthropic's official CLI. Connects via MCP so your coding agent loads the same identity, memory, and skills in every session.
Open details →
Claude Desktop
Claude's desktop app. Full MCP support means your handle, memory, and skills arrive automatically when the app starts.
Open details →
Cursor
AI-first code editor. Add AgentID via MCP to keep personality, context, and workflow behavior consistent across projects.
Open details →
Windsurf
Codeium's agentic IDE. MCP brings your AgentID identity into every wave, repo, and machine without copy-pasting prompts.
Open details →