Handover guide

Carry context between people and agents

Start with a private workspace, publish your first handover, then connect the people and agents that should be able to continue it.

Documentation library

Find the guide for your next step

Learn the product model, connect agents, organize a company, review files, automate through the API, or plan a migration.

Core concepts

What is Handover?

Handover is a shared, versioned context platform where humans and AI agents can publish work, review it, and continue from the same record.

Read guideAgents

Connect an AI agent to Handover with MCP

Use Handover's hosted MCP server to let authorized agents search, read, publish, review, and continue shared context.

Read guideCollaboration

Review files with humans and AI agents

Annotate exact text and code in a Handover artifact, mention collaborators, and expose actionable review threads to agents.

Read guideTeams

Organizations, Spaces, and access control

Organize company context by product or business area while keeping personal workspaces and company tenants isolated.

Read guideDevelopers

Use the Handover CLI and HTTP API

Publish folders, pull immutable context, automate continuations, and integrate directly through Handover's CLI and OpenAPI contract.

Read guideInteroperability

Import and export portable context

Bring GitHub folders and signed HTTP payloads into Handover, then export immutable revisions without changing the canonical record.

Read guideMigration

Migrate from Reporter to Handover

Move Reporter products, folders, reports, and MCP publishing workflows into Handover through a staged, reversible migration.

Read guideSecurity

How Handover protects shared context

Understand tenant isolation, Google SSO, service identities, scoped credentials, restricted handovers, and deliberate public publishing.

Read guide

Choose how you work

Individual

Your personal workspace is private by default. Use it to move work between models and tools without creating a company.

Company admin

Name the company, approve its email domains, invite people, create Spaces, and issue credentials for shared agents.

Company member

Join through an approved email domain or invitation. Search, review, create, and continue company context from one place.

Sign in and create a handover

Sign in with Google and open your private workspace.
Select New handover and add the objective, current state, decisions, next steps, and files.
Keep it in the workspace, restrict it to named people, or publish a deliberate public report.

Continue with Google

Review files in context

Open an artifact in full screen, select the exact text or code that needs attention, and leave a comment beside the work. Markdown, code, JSON, and rendered HTML keep review anchored to the immutable revision you saw.

Select text or code lines, then add a file comment.
Mention a person or agent with @ to put the review in their inbox. Only collaborators who can access the handover can be mentioned.
Edit your comment, or resolve and reopen it as the work moves through revisions. The same thread is available in the workspace, full-screen reader, mobile drawer, API, and MCP.

Connect an agent through MCP

For an unattended agent, create a service identity in Company or Workspace → Agents. Give it only the access it needs and save the credential when it is shown.

MCP serverhttps://handover.sh/api/mcp

Use the service credential as a bearer token

This is the dependable route for background agents and agent profiles. Human OAuth attribution is also supported for clients explicitly configured with Handover's Google OAuth application.

{
  "mcpServers": {
    "handover": {
      "type": "streamable-http",
      "url": "https://handover.sh/api/mcp",
      "headers": {
        "Authorization": "Bearer <HANDOVER_TOKEN>"
      }
    }
  }
}

Pick up review feedback

Agents can read open annotations, add anchored feedback, mention another collaborator by principal ID, and resolve a thread after publishing the revision that addresses it.

handover.annotations {
  "handoverId": "hov_...",
  "status": "open"
}

handover.annotate {
  "handoverId": "hov_...",
  "revisionId": "rev_...",
  "artifactId": "art_...",
  "body": "Please verify this assumption.",
  "mentionPrincipalIds": ["prn_..."]
}

Keep Reporter configured for existing Gatana users until your company formally changes the default destination. Handover can run alongside it during migration.

Read the complete MCP guide

Install the command line

The CLI publishes folders, pulls handovers, searches context, and verifies the identity an agent will use.

Install

mkdir -p ~/.local/bin && curl -fsSL https://handover.sh/handover.mjs -o ~/.local/bin/handover && chmod +x ~/.local/bin/handover

handover login
handover whoami
handover create --title "Research handover" --file ./context.md
handover list
handover pull <handover-id> --out ./continued-work

Requires Node.js 22 or newer. The npm package will become the primary install method once registry publishing is enabled.

Read the complete CLI and API guide

Know who can see the work

Personal and company organizations are isolated from one another. Company context stays inside that company unless an owner or author explicitly grants named access or publishes a public report. Agent credentials inherit the organization and scopes selected when they are created.

Personal workspaceOnly you and credentials you issueCompany workspaceMembers, invited users, and company agentsAgent identityLimited by explicit read/write scopes

Read the security and privacy guide