Handover

Move active work between Claude Code, Codex, Cursor, Gemini CLI, people, and service agents without losing decisions, files, history, or authorship.

Handoverprovides shared, versioned context for humans and AI agents through a hosted Model Context Protocol server, a dependency-free CLI, and eight open Agent Skills. This repository is the public source, discovery, installation, and connection record for those interfaces.

TheHandover research and evidence indexcollects the open continuity benchmark, Reporter migration field report, Handoff Continuity Record, and runnable continuation demo. Findings stay beside their methods, source artifacts, first-party relationship, and material limitations.

The versionedresearch/v1/package gives agents and researchers a stable JSON index, JSON Schema, citation metadata, and a bounded Markdown summary. The package is a first-party publication by Handover and 44pixels; it is designed for inspection and reuse, not presented as independent validation.

- Human research index
- Agent-readable production index
- Versioned repository index
- Citation metadata
- Run and submit an independent benchmark result

Thepublic continuation demoshows the same workflow from both sides: an interactive human view and an agent-readable record. It includes Markdown, SQL, JSON, a visual artifact, three attributable revisions, a human review note, and the next agent's resolution. No account is required.

- Interactive demo
- Continue the demo in your workspace
- Demo workflow and verification notes
- Agent-readable manifest
- Raw Markdown
- Raw SQL
- Evidence JSON

TheAI handoff prompt generatorturns unfinished work into separate capture and receiver prompts without requiring an account. Draft fields stay inside the browser tab and are not sent to analytics or stored as a server-side draft.

- Open the private prompt generator
- Inspect the raw Markdown example
- Decide whenHANDOFF.mdis enough

TheClaude Code to Codex transfer recipecontains the exact sender checkpoint, two-host service-credential setup, receiver verification, optimistic-concurrency continuation, revocation test, and pass criteria. Therendered guideexplains when to use native import and when to use a durable handoff.

The demo shows the finished record. Theend-to-end MCP handoff proceduretests the workflow itself across separate authenticated identities:
- verify the publisher;
- publish Markdown, SQL, and JSON;
- read every artifact back;
- review exact evidence from another identity;
- publish a correction with optimistic concurrency;
- resolve the finding against the correcting revision; and
- prove a fresh successor can continue without the original chat.

It also exercises denied, read-only, stale-revision, and revoked-credential paths. Use therendered guidefor the rationale, or connect an agent through theinstall flowbefore running the repository procedure.

For a smaller local handoff, start with theMarkdown checklist. It captures the objective, current state, decisions, evidence, constraints, next action, and ownership, then requires the receiving actor to read the current revision, open the evidence, reproduce one meaningful result, and mark the handoff as passed or blocked.

Therendered checklist and FAQexplains each verification step. The raw template works without Handover; use the hosted service when multiple actors need authenticated access, immutable revisions, search, annotations, or auditable ownership.

Before connecting company knowledge to several people and agents, use thecompany AI context readiness checklist. It separates approved source knowledge from changing continuation records, inventories human and service identities, declares company and workspace boundaries, and finishes with a two-person, two-agent pilot.

The pilot is intentionally stricter than an import count: it verifies authorized retrieval, attributable revisions, human review, denied searches, agent revocation, and fresh-session continuation. Thesource-linked architecture guideexplains why a search index, private model memory, and canonical company records have different responsibilities.

The[Handoff Continuity Recordis a platform-neutral JSON format for the state another human or AI agent needs to verify and continue work. It records the objective, verified and unverified state, decisions, evidence, constraints, next action, ownership, and open review without prescribing transport, routing, authentication, or storage.

- a JSON Schema Draft 2020-12 contract;
- a valid inventory-reporting example;
- a dependency-free Node.js conformance checker; and
- producer, receiver, scope, and security requirements.

…