Making AI coding sessions persistent across agents
Drift is a tool designed to make AI coding sessions persistent and transferable across different AI agents like Claude, GPT, and Gemini. It captures reasoning, decisions, and rejected approaches in a structured markdown format, enabling seamless handoffs when switching models. By integrating with git, it preserves AI-generated context and supports auditability, blame tracking, and collaboration without relying on any single vendor.
- ▪Drift captures AI coding session context, including decisions made and approaches rejected, into a portable markdown brief.
- ▪It integrates with git to bind AI sessions to commits using git notes, preserving attribution across agents.
- ▪The tool supports local-first operation, ensuring session data stays on the user's machine and does not leave unless explicitly configured.
- ▪Drift enables cross-agent handoffs, allowing a new AI agent to resume work without re-explaining context.
- ▪It provides commands like drift blame and drift log to trace code back to its originating AI session, prompt, and agent.
Opening excerpt (first ~120 words) tap to expand
🌐 English · 日本語 · 简体中文 · 繁體中文 drift_ai Vendor-neutral handoff for AI coding tasks — between Claude, GPT, Gemini, DeepSeek, local LLMs. Reads from Claude Code, Codex, Cursor, Aider. Local-first. 🧠 AI coding breaks when you switch agents Claude stalls. Codex refuses. Cursor goes off-track. You spend 30 minutes re-explaining context you already solved. What decisions were made? What approaches already failed? Which file you were editing? 👉 None of that survives a session. ❌ Git tracks code — not AI reasoning Git shows what changed. It does NOT tell you: why it was written what was rejected which agent produced it what context led here That reasoning disappears.
…
Excerpt limited to ~120 words for fair-use compliance. The full article is at GitHub.