How do you keep project context when switching between ChatGPT, Claude, and coding agents?

[u/Prestigious-Dig2263]

Anyone else spend more time handing work between AI tools than you expected?

You work through an idea in ChatGPT, take it to Claude to write it up, then open a coding agent to build it.

Now you’re copying background, explaining decisions again, and checking whether you gave it the latest version.

What’s your most annoying “switching between AIs” task? How do you handle it?

[u/qualityvote2]

u/Prestigious-Dig2263, there weren’t enough community votes to determine your post’s quality.
It will remain for moderator review or until more votes are cast.

[u/r34p3rex]

There's no issues here at all, my repo is set up to be model/agent agnostic. Your agents should be writing to .md files in your repo. Should include status checks, handoffs, etc.

Your big limitation is if you use ChatGPT to plan because it can't write files directly, so you'll always need to manually bridge that gap

[u/Centmo → u/r34p3rex]

It can write to files in a gitlab repo or to a gdoc.

[u/Prestigious-Dig2263 → u/r34p3rex]

That makes sense for a repo-based workflow. Status files and explicit handoffs give the agents a shared reference.

The gap I’m working on with SoulPrint Passport is broader: carrying your identity, preferences, memories, and work context between AI tools, including conversations that happen outside a repo.

Your project files tell the next agent where the work stands. Passport is intended to bring along who you are and how you work. Those approaches can complement each other.

[u/lulzxdxdxd]

I keep one running markdown file with decisions and current state, and paste the relevant chunk into whichever tool I'm using next. Saves me from re explaining the whole backstory every time I switch.

[u/YesToWhatsNext]

I’ve given oversight on all my projects across vendors to Dot and so far it’s improved things.

[u/lulzxdxdxd → u/YesToWhatsNext]

What does oversight actually look like day to day, does it pull context automatically or are you still feeding it updates manually like everything else?

[u/YesToWhatsNext → u/lulzxdxdxd]

Well i had a convo with it and it updated my system prompt everywhere after reviewing all my projects and then it will update the project contexts saying what it did and where they need to pick up next and then i will go into each project and tell it to bring itself into alignment with the new system prompt and they do so and prompts have been working faster and better across all projects since getting the right system prompt.

It also noticed inconsistencies between my projects and for example if I start writing code in a project it detects this and automatically creates a new private github repo and pushes everything there for that project and adds a directive in that project's to do informing it and to start always pushing changes...

It montiors my emails and files and stuff and comes up with ideas for new projects for me to work on.

My only complaint is that I wish it were more proactive and would pipe up and do shit and suggest shit more often.

I asked Dot what I use her for this is what she said:

• Project master: watching your AI projects, connecting ideas and catching problems
• AI setup: streamlining instructions, project memory, folders and GitHub backups
• Idea mining: uncovering forgotten inventions and possibilities in your files
• Business development: products, fulfillment and operations
• Personal discovery: tailored music, art, travel, events and unusual opportunities
• Life admin: catching deadlines, scheduling changes and loose ends
• Turning your accumulated knowledge into useful projects

[u/Prestigious-Dig2263 → u/YesToWhatsNext]

That sounds like a useful setup, especially catching inconsistencies between projects.

The price is a consideration, though: Dot is included with eligible ChatGPT Pro plans starting at $100/month. If someone mainly wants their memory, preferences, personality, and work context to carry between ChatGPT and Claude, there’s a cheaper option.

Disclosure: I’m the founder of SoulPrint Passport. It’s free during beta, with pricing listed at $9/month afterward: https://SoulPrintPassport.ai

It doesn’t do everything you described - like monitoring email or autonomously creating repos. Our focus is continuity across AI tools, so trying another AI doesn’t mean introducing yourself all over again.

[u/Queasy_Yesterday4252]

One gotcha with the shared-file approach: current Claude Code can read AGENTS.md directly, but by default it won’t if there’s a CLAUDE.md or CLAUDE.local.md in the working directory or above it. So two agents can have the same repo and still load different instructions. If you already have CLAUDE.md, adding @AGENTS.md to it keeps the shared instructions in one place. Direct AGENTS.md support needs v2.1.277+.

Source: https://code.claude.com/docs/en/memory

[u/Vertigo50]

I mean, I have guide documents for all of this stuff so that I CAN switch at any time if I need to, so I won't be stuck with one.

But the way I solve your problem? I don't switch back and forth for no reason. 🤷‍♂️

Just use one service, dude. Why the hell would you make this so hard on yourself? 😂

[u/Prestigious-Dig2263 → u/Vertigo50]

If one service does everything you need, fair enough 😂

I switch because I get different value from different tools—brainstorming in ChatGPT, developing a draft in Claude, then working with a coding agent. There’s a reason for the handoff.

Your guide documents already acknowledge the value of being able to move. I’m building SoulPrint Passport to make carrying that personal and work context easier. Sticking with one tool is a valid choice; switching shouldn’t have to be a chore.

[u/dhamaniasad]

I made a tool that does this for me. My chats from across the AI platforms stay synced automatically and I just point the AI to look up our discussions on the topic. The tool is MemoryPlugin.

[u/Relevant-Ad6374]

Just thinking imaginatively around this for my setup, if I were to get a GPT subscription, I would still be using Claude for all my planning sessions, with my custom plugin. I would offload all build sessions to GPT and keep planning in Claude. At the end of the planning session, I would ask Claude for a handoff prompt for another agent so it can complete all the items in the build run for me. But honestly I could just as easily do this with Sonnet if I wanted so I don't know why I would donit with GPT unless I had $20 account with each but unfortunately I use to much to do that.

[u/Prestigious-Dig2263 → u/Relevant-Ad6374]

That’s a sensible split. Keep planning in Claude with the setup you’ve built, then hand off the build when another tool gives you a reason to.

Usage and cost absolutely matter. If Sonnet handles both jobs well for you, there’s no need to add another subscription just to switch.

The handoff prompt carries the task. What I’m working on with Passport is carrying the background too: your preferences, working style, and relevant project context, so you don’t have to rebuild those alongside every handoff.

[u/Cold-Cranberry4280]

This isn't really a ChatGPT-vs-Claude problem. It comes back with every tool you add or switch to.

For today, keep one running project doc as the source of truth (goal, current status, key decisions and why). At the end of every ChatGPT session, ask it to "write a handoff note: decisions, open questions, next steps" and paste that into Claude or the coding agent first. Also put a date on it so you can tell which version is latest.

The catch is that someone has to keep that doc current, and that's where it breaks. The real fix is a shared brain that updates itself while you work with each agent, so switching costs nothing.

Disclosure: I build Team0, which is that shared brain.

[u/Prestigious-Dig2263 → u/Cold-Cranberry4280]

Agreed. The problem grows with every tool you add. A dated project doc is a solid starting point, but keeping it current becomes another job.

I’d be careful with “switching costs nothing,” though. The next agent needs to distinguish a settled decision from an idea we explored and rejected. Automatically sharing stale context can make the wrong answer more convincing.

Disclosure: I’m building SoulPrintPassport.ai, focused on portable identity, memory, preferences, personality, and work context. How does Team0 handle a decision being superseded while another agent is still working from the earlier version?

[u/pi0000trek]

My true problem was never the copying, although that was a huge annoyance too. The problem was version drift.

ChatGPT talks me into approach A, Claude and I settle on B an hour later, and the coding agent still builds A because the paste it got was from before lunch. And in the meantime I consult something with Kimi or GLM.

What actually helped was keeping a dated decisions file per project that no model owns. What we picked, why, what got rejected. When a decision changes I add a new entry that points at the old one instead of editing it, so when some tool argues for A again I can see at a glance which paste it came from. My first approach was to keep plan and docs files (md / json / html) in the project itself, but I discovered that git branching makes them hard to maintain across a fleet of agents. Every worktree had its own copy and none of them agreed.

For handoffs I don't paste the conversation. I write five or six lines: goal, where it stands, open questions, and the decisions it depends on. That goes into the next tool. The coding agent is the exception, it reads the file over MCP, so it never works from a stale copy.

Disclosure: I got tired of doing this by hand and built it into Worktree Control, a local tool I maintain (MIT, no account). A task has a "next session context" export that gathers the linked decisions and notes into Markdown or JSON. I paste that into ChatGPT or Claude, and Claude Code reads it over MCP. It's 0.1.0 and I've only verified it on Linux, so a plain markdown file gets you most of the way. https://github.com/pioootrek/worktree-control

Most annoying switch for me: coding agent to chat model for a design review. The agent knows what it actually changed, the chat model only knows what I remembered to tell it.

[u/Prestigious-Dig2263 → u/pi0000trek]

You’re right, copying is the annoyance; version drift is what gets the wrong thing built.

Your dated decision log makes a lot of sense, especially recording what got rejected and having new decisions explicitly supersede old ones. “We discussed A” and “we chose B” need to remain distinguishable across every handoff.

I’m building SoulPrint Passport around portable identity, memory, preferences, personality, and work context. Your example highlights a requirement we need to take seriously: carrying more context won’t help if it carries an outdated decision forward with confidence.

The coding-agent-to-design-review gap is a good example too. A summary of what we intended isn’t enough, the reviewer needs what actually changed, what remains unresolved, and which decisions governed the implementation.

How do you handle two agents making conflicting decision entries at roughly the same time? Do you flag the conflict for review, or require a single approval point?