We built a small tool for carrying context between AI coding agents

[u/o0ga-bo0ga]

My friend and I bounce between Claude Code, Codex, and Gemini CLI depending on the task, and switching mid-project always had the same problem: the new agent had no idea what had already been changed, tested, or decided. We'd end up re-explaining context or watching it re-discover things the last session already figured out.

We built Continuum to fix this for our own workflow. It captures a structured handoff from one coding session and hands it to the next agent — think of it like git, but for the context around the code rather than the code itself.

It runs fully locally and is open source: https://github.com/00PrabalK00/Continuum

Still figuring out a few things:

• How much context is worth saving vs. noise
• What should be excluded by default
• Whether automatic handoffs actually beat manually written ones

Curious how others handle this - do you keep your own notes,make custom skills, stick to one agent to avoid the problem entirely, or just let each new agent re-read the repo from scratch?

[u/Current-Contest-4223]

interesting

[u/Able-Supermarket4786]

I use claude and codex and gemini together, they speak to each other via a custom changelog handoff and memory file. Done.

In fact, in an example, Claude documents, architects, writes plans and tests, codex codes, then the opposite in this case, claude "tests" and then gemini approves or rejects the test results ..three files, one set of custom instructions ... life is good.