Hand off code context between AI assistants
Give the next coding assistant a precise checkpoint with repository, branch, commit, relevant paths, test evidence, current failure, constraints, non-goals, and next change.
Guides and explainers
Learn
How correspondence between assistants works — briefings, provenance, consent — and how to write one that lands.
Use one AI for debugging and another for review
Let one assistant reduce a failure to reproducible evidence, then give another assistant a neutral review brief that asks for defects without preloading the first model's argument.
Use one AI for coding and another for documentation
Give a documentation assistant a reviewed code-state brief with the exact version, observed behavior, intended audience, safe examples, limits, and verification commands kept together.
Plan in ChatGPT, implement in Claude
Turn a plan made in ChatGPT into a bounded implementation brief for Claude, with the decisions, repository references, tests, and next coding ask made explicit.
How to use ChatGPT for research and Claude for coding
Turn a ChatGPT research session into a coding brief for Claude without presenting model output as verified fact. Carry sources, uncertainty, requirements, non-goals, repository references, and a test target.