Skip to main content

handover

Design in chat. Build in terminal. Zero context lost.

handover is an open-source CLI tool that bridges AI chat interfaces (Claude, ChatGPT, Gemini, and others) to local terminal coding agents (Claude Code, Codex CLI, Copilot, Aider, Goose, etc.). It extracts decisions, plans, and intent from a chat conversation and generates agent-specific handover artifacts — the exact files each coding agent expects — so a local agent can immediately act on your intent without re-explaining anything.

Each target adapter knows what its agent needs: Claude Code gets CLAUDE.md + PLAN.md, Codex gets AGENTS.md + TASKS.md, Copilot gets .github/copilot-instructions.md, and so on. The parsing and extraction happen once; each target decides how to express the result.

PyPI version Python versions License: MIT CI


Install

pip install handover

Optional extras:

pip install 'handover[watch]'   # enables: handover watch (session file monitoring)
pip install 'handover[mcp]'     # enables: handover mcp (MCP server for Claude Code)

zsh users: the brackets must be quoted. Unquoted pip install handover[watch] fails with zsh: no matches found because zsh interprets [...] as a glob.


Quickstart

# Basic usage — single conversation file
handover --input conversation.json --output ./my-project/

# List all conversations in a bulk export
handover list export.jsonl

# Bulk export — select a specific conversation by title
handover --input export.jsonl --title "API Design Discussion" --output ./my-project/

# Incremental update — merge new context into existing .handover/ (v1.2.0)
handover update --input follow-up.json --output ./my-project/

# Sync backlog task status from codebase evidence (v1.2.1)
handover sync --project ./my-project/

# List conversations grouped by project (v1.2.0)
handover list export.jsonl --by-project

# Merge conversations by project name (v1.2.0)
handover merge --input export.jsonl --project "API Design" --output ./my-project/

--dry-run Demo

$ handover --input chat.json --output ./my-project/ --no-llm --dry-run

Parsing: 'API Design Discussion'
  Source : claude (single-json v1.0)
  Messages: 34

Extracted:
  Goal       : Build a FastAPI REST API with JWT auth and PostgreSQL
  Tech Stack : Python, FastAPI, PostgreSQL, pytest
  Decisions  : 2
  Tasks      : 6
  Constraints: 2
  Questions  : 1

Target: claude-code  |  Would write to ./my-project/:
  -> CLAUDE.md
  -> PLAN.md

Run without --dry-run to write files.

Supported Input Formats

Source Format How to Export
Claude.ai bulk export .jsonl Settings → Privacy → Export Data
Claude.ai single chat .json / .md Claude Conversation Exporter browser extension
ChatGPT .json Settings → Data Controls → Export Data
Gemini .json Google Takeout → Gemini Apps Activity
Perplexity .json Settings → Account → Export Data

Two-Layer Output (v1.1.0)

Every run produces two layers:

  1. .handover/ — vendor-neutral knowledge base (always generated): manifest, context (overview, architecture, ADR-style decisions, constraints, risks, acceptance criteria), work plan (spec, tasks, milestones, backlog JSON), standards, and 6 drop-in prompts. Portable across any agent.
  2. Per-target workspace — for claude-code, a thin CLAUDE.md index plus .claude/agents, .claude/skills, .claude/commands, .claude/hooks, and settings.json, populated by domain detection on the chat.
your-project/
├── .handover/
│   ├── manifest.yaml
│   ├── context/   overview.md, architecture.md, decisions.md, ...
│   ├── work/      spec.md, tasks.md, milestones.md, backlog.json
│   ├── standards/ coding-standards.md, testing-standards.md, ...
│   ├── prompts/   implement.md, review.md, debug.md, ...
│   └── codebase/  structure.json, symbols.json, dependencies.json, index.md
├── .claude/
│   ├── agents/    backend-agent.md, database-agent.md, ...
│   ├── skills/    rest-conventions.md, ...
│   ├── commands/  run-tests.md, lint.md
│   ├── hooks/     pre-tool-use.sh
│   └── settings.json
├── CLAUDE.md      (thin index pointing into .handover/)
└── PLAN.md

Skip Layer 1 with --no-handover-dir, write only Layer 1 with --handover-dir-only, replace existing layers with --overwrite-handover-dir. See docs/handover-directory.md for the full layout and how to extend it.

Agent-Aware Output

handover parses your chat once and generates the files your chosen coding agent expects. Each target adapter owns its own filenames and format — Claude is one target, not the default mental model for the whole product.

Target Generated Files Agent
claude-code (default) CLAUDE.md + PLAN.md Claude Code
codex AGENTS.md + TASKS.md Codex CLI
copilot .github/copilot-instructions.md GitHub Copilot
aider .aider.conf.yml Aider
goose goose-context.json Goose
all All of the above All agents
handover --input chat.json --output ./my-project/ --target codex
handover --input chat.json --output ./my-project/ --target copilot
handover --input chat.json --output ./my-project/ --target all

CLI Reference

Chat export → agent context

handover --input <file> --output <dir> [OPTIONS]
Flag Default Description
--input, -i required Chat export file (.json, .jsonl, .md)
--output, -o required Directory to write output files
--source auto Force parser: claude, chatgpt, gemini, perplexity
--title — Select conversation by title (substring match, for bulk exports)
--id — Select conversation by ID (for bulk exports)
--target claude-code Output target (coding agent): claude-code, codex, copilot, aider, goose, all
--no-llm off Rule-based extraction only — no API key required
--dry-run off Preview what would be written, without writing
--launch off Run claude in output directory after writing
--template — Path to custom Jinja2 templates directory (claude-code target only)
--publish off Publish generated artifacts to GitHub Gist after writing (requires gh CLI)
--no-handover-dir off Skip the .handover/ knowledge base (legacy v1.0.x output only)
--handover-dir-only off Generate .handover/ only, skip target-specific files
--overwrite-handover-dir off Replace an existing .handover/ (and .claude/) directory
--no-index off Skip the .handover/codebase/ index pass

Incremental update (v1.2.0)

Update an existing .handover/ directory with new conversation context — preserves completed task marks and manual edits.

handover update --input follow-up.json --output ./my-project/
handover update --input follow-up.json --output ./my-project/ --no-llm --dry-run
handover update --input follow-up.json --output ./my-project/ --no-conflict  # no conflict markers
Flag Default Description
--input, -i required New chat export file
--output, -o required Directory containing existing .handover/
--source auto Force parser
--title — Select conversation by title
--id — Select conversation by ID
--no-llm off Heuristic-only extraction
--dry-run off Show delta summary without writing
--no-conflict off Take latest decision silently (no conflict markers)

Explore exports

handover list <export_file>            # list all conversations in a bulk export
handover list export.jsonl --source claude
handover list export.jsonl --by-project  # group by project (v1.2.0)

Scaffold custom templates

handover init       # copies default templates to ~/.handover/templates/ for editing

Reverse handover — Claude Code session → HANDOVER.md

Generates HANDOVER.md from Claude Code session logs: what was accomplished, files changed, decisions made, and recommended next steps.

handover reverse --project .                          # auto-discover latest session
handover reverse --session ~/.claude/projects/…/abc.jsonl
handover reverse --project . --no-llm --dry-run

handover sessions                                     # list recent Claude Code sessions
handover sessions --project ~/my-app --limit 20

handover watch --project .                            # auto-generate when session goes idle
handover watch --project . --idle 30 --daemon         # background mode
# requires: pip install handover[watch]

Local bridge for browser extension

Starts an HTTP server that the Chrome/Firefox extension uses to send conversations directly from the browser.

handover serve                                   # port 7437 (H-A-N-D on phone keypad)
handover serve --port 7437 --output ~/my-app/
handover serve --no-llm --daemon                 # background mode

Endpoints: GET /health, POST /handover, POST /config
See docs/browser-extension.md for extension setup.

History & re-run

Every successful non-dry-run invocation is logged to ~/.handover/history.jsonl.

handover history                          # last 20 runs
handover history --limit 50
handover history --project ~/my-app/     # filter by output directory

handover rerun h_4a2955ab                # re-run a past handover by ID

Merge multiple exports

Combine two or more chat sessions into one unified CLAUDE.md + PLAN.md. Deduplicates tasks and decisions automatically.

handover merge --input session1.json --input session2.json --output ./my-project/
handover merge --input s1.json --input s2.json --output . --no-llm --target all
handover merge --input export.jsonl --project "API Design" --output ./my-project/  # v1.2.0

Share via GitHub Gist

# Publish after generating (requires gh CLI authenticated)
handover --input chat.json --output ./my-project/ --publish

# Pull shared handover artifacts
handover pull https://gist.github.com/user/abc123
handover pull abc123 --output ./my-project/

MCP server for Claude Code

Exposes handover as an MCP server so Claude Code (or any MCP client) can call it directly. Since v1.1.1 the server exposes four tools.

handover mcp
# requires: pip install handover[mcp]

Add to ~/.claude/mcp.json:

{
  "mcpServers": {
    "handover": {
      "command": "handover",
      "args": ["mcp"],
      "env": { "ANTHROPIC_API_KEY": "${ANTHROPIC_API_KEY}" }
    }
  }
}
Tool What it does
run_handover Parse a chat export and write .handover/ + .claude/
handover_status Read .handover/work/backlog.json and report progress
handover_reverse Summarise the latest Claude Code session into HANDOVER.md
handover_list List conversations inside a chat export file

Full reference: docs/mcp-server.md.


Roadmap

Version Phase What ships Status
v0.2.0 1 + 2 Claude, ChatGPT, Gemini, Perplexity → Claude Code ✅ Released
v0.3.0–v0.4.0 3 + 4 handover serve + browser extension; reverse handover (handover reverse, handover sessions, handover watch) ✅ Released
v0.5.0 5 Multi-target: Codex CLI, Aider, Goose; --target all ✅ Released
v1.0.0 6 MCP server, handover history, handover merge, Gist publish/pull ✅ Released
v1.1.0 — Two-layer scaffold (.handover/ + .claude/) ✅ Released
v1.1.1 — MCP server: four tools (run_handover, handover_status, handover_reverse, handover_list) ✅ Released
v1.1.2 — Codebase indexer (.handover/codebase/): structure, symbols, dependencies, change impact ✅ Released
v1.2.0 — Incremental update (handover update), multi-chat project grouping (--by-project, --project) ✅ Released
— — VS Code extension, GitHub Action Coming soon

Contributing

The primary contribution path is adding a new source adapter or output target. Each adapter is an isolated Python class anyone can own end-to-end.


License

MIT © 2026 Mohan Krishnaa Alavala

Metadata

Release files for handover 1.2.1

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for handover 1.2.1
File Size Uploaded Provenance
handover-1.2.1.tar.gz 184.1 kB With provenance Details

Built distribution (wheel)

Table of built distributions (wheels) for handover 1.2.1
File Interpreter ABI Platform
handover-1.2.1-py3-none-any.whl Python 3 none any Details

Total release size: 307.6 kB

Release files / handover-1.2.1.tar.gz

Download URL handover-1.2.1.tar.gz
Size 184.1 kB
Tags Source
SHA-256 checksum
How to use checksums
fd676a11ede83f915c21203d77285a7478b6f1af9b4b3aca5259af4bdb99378e
BLAKE2b-256 checksum
How to use checksums
5b6a544a6646abb87acc72dd40b0e72b8e1066a048a57e5b506df1a26b05198e
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/6.1.0 CPython/3.13.12

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Apr 12, 2026.

Transparency log

Release files / handover-1.2.1-py3-none-any.whl

Download URL handover-1.2.1-py3-none-any.whl
Size 123.6 kB
Tags Python 3
SHA-256 checksum
How to use checksums
d56cd408200575b02a13f003f148492a9fadce64731aaa192e69548179581a37
BLAKE2b-256 checksum
How to use checksums
0628129ece273a1602ed4e9ad22f46c3e71bc2bb90a9a3b206d3ed9d1aad9297
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/6.1.0 CPython/3.13.12

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Apr 12, 2026.

Transparency log

Security for handover 1.2.1

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

Full provenance

All 2 files in this release have been uploaded with provenance metadata.

Select from 2 files

Attestation for handover-1.2.1.tar.gz

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Apr 12, 2026.

Transparency log

A note on package security

PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.

To learn more about protecting yourself from malicious actors, visit our package security documentation.

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page