I saw that @heydittoai walked through Ditto v2 at Exploit Summit, including the bit where an agent switches platforms and keeps the context. Their own write-up uses a case that is basically one sentence: point the new agent at the old one and tell it to mind meld. No rebuild. To give you some more context on this, a normal chat remembers you only inside that app. Claude does not know what you told Cursor, and a new agent starts from zero. But if the spec changed in Telegram, or you moved from one coding agent to another, Ditto v2 keeps one memory under the tools and waits for a yes before it sends or edits anything risky. So the flow would look something like this: ▸ You say it once, in Claude, Cursor, Codex or Grok, and the others can already use it. ▸ Telegram and Slack sit next to the docs and the code, so the agent can search the decision, not just the repo. ▸ A workflow or browser agent runs the job, and the step that could do damage waits for your approval. Depending on the tool, you stay in that chat or leave with the memory exported. This ties back to what I wrote before: the models got good at answering, but you are still the switchboard between them. That’s the part Ditto v2 is building for, even when the handoff is a single sentence. What other agent handoffs should I look into?