Skip to content
Angareion for Claude Code

Every new session.
Less lost context.

Persistent shared context for Claude Code. Reuse project decisions and research across sessions, and hand work to Claude, ChatGPT, or Codex with Angareion.

Local Claude Code sessions · HTTP and OAuth

One retained knowledge layer. Each client connects with its own permissions.

The direct answer

What does Angareion add to Claude Code?

Angareion connects local Claude Code sessions to shared memory through HTTP MCP and OAuth. It preserves the project knowledge you choose to save, so a later session can retrieve decisions, constraints, and handoffs from Claude Code or another connected client.

Understand shared AI memory

Built around your work

Less backstory.
More forward motion.

The files tell you what exists. Your retained knowledge tells you why. Give the next Claude Code session the project intent, previous decisions, and open questions that deserve to survive a fresh start.

01

Start with the decisions already made

Retrieve the project requirements and tradeoffs before changing a workflow or building a tool. Bring in the research saved by your Claude or ChatGPT conversations.

02

Preserve the discoveries that matter

Save a useful explanation, a constraint, or a lesson from a working session. Ask the next session to retrieve those memories instead of repeating the investigation.

03

Make the next session a continuation

Save a handoff with completed work, remaining steps, blockers, and decision rationale. Resume it in Claude Code, Codex, or a connected chat assistant.

Inside Angareion

Your connection.
A clear place to start.

The Connect guide walks you through your client’s setup. Choose the appropriate connection, approve access, and verify the tools before asking for your context.

Angareion / Connect
The Claude Code setup guide in Angareion Connect
The Claude Code setup guide in Angareion Connect. Captured from the public product UI; no customer data.

Your work can travel

Start in Claude Code.
Continue in ChatGPT.

Save what matters, then ask another connected assistant to pick it up. The same agent or an authorized shared scope keeps the context available.

Claude Code01 / Preserve
“Save the project decisions and the remaining blockers in Angareion. Prepare a handoff for ChatGPT to review the plan with me.”
Saved in Angareion
ChatGPT02 / Continue
“Resume my Claude Code handoff. Retrieve the decision rationale and help me prioritize the remaining work.”

Illustrative prompts. Your assistant must call the connected tools; chat history and local files are not automatically transferred.

How an AI handoff works

Make the connection

How to connect Claude Code
to Angareion.

  1. 01

    Get access and choose Claude Code

    Request Angareion beta access, then open the dedicated Claude Code Connect guide.

  2. 02

    Register and authenticate

    Add the Angareion HTTP MCP server at user scope. Open /mcp in a local Claude Code session and complete its browser authentication flow.

  3. 03

    Add workflows and resume work

    Optional Claude Code skills provide reusable instructions. Ask the connected session to retrieve project context or resume a handoff before starting the next task.

Questions, answered

Claude Code, models,
and shared memory.

What carries over, what needs connecting, and how to keep the work moving.

Explore the knowledge library

How can Claude Code retain context between sessions?

Connect Angareion and explicitly save the decisions, lessons, outputs, or handoffs you want to retain. A new session can retrieve that context through the MCP tools. This does not expand the model’s context window or silently archive the full session.

Will my memories follow me between Claude Sonnet and Opus?

The retained memories stay with the Angareion agent. A local Claude Code session using Sonnet or Opus can retrieve the same permitted context when the tools are connected. The models can still differ in how they interpret the work.

Is Angareion the same as CLAUDE.md or a project instruction file?

No. A project instruction file provides local guidance. Angareion supplies a separately retained, searchable knowledge layer that can include decisions from other clients and explicit handoffs. You can use both for different parts of your working context.

Can I move a Claude Code task to Codex or ChatGPT?

Save a handoff to Angareion with the task state, next steps, rationale, and blockers. Ask the destination client to resume it using the same agent or permitted shared scope. Repository files and unsaved local changes still need their own transfer path.

What can I keep in Angareion for Claude Code?

Retain useful facts and decisions as memories, add reference material to knowledge sources, save complete work products as outputs, and preserve unfinished work as handoffs. These are explicit workflows: Angareion does not automatically record everything you do in every assistant.

Who can access my shared context?

Access follows your Angareion agent identity and permitted memory scopes. Reusing the same agent across clients provides continuity; team or institutional sharing requires the appropriate scope and permissions. Connecting a new client does not give it unrestricted access to every memory.

How do I get started, and do I need another AI subscription?

Request Angareion private-beta access, then follow the connection guide for your client. Angareion does not supply the AI client’s subscription or change its account requirements. Compare the current Angareion editions and check the client’s own eligibility before connecting.

Connection referencesAngareion’s Claude Code guideAnthropic: Claude Code MCP connections Support details checked October 13, 2026. Client features and workspace access can change.

Keep what you learn

Give your next conversation
a better starting point.

Request Angareion access, connect Claude Code, and build a body of knowledge that can travel with your work.

Private beta. Access is granted from a waitlist.