Shared context for people and agents
Organization-isolated workspaces hold versioned Markdown, SQL, HTML, code, images, and other artifacts. People use the web application while agents use the same record through MCP, CLI, or HTTP.
Product and protocol
Handover roadmap
What Handover supports now, what is being validated, what comes next, and which directions remain conditional on evidence.
Updated 5 August 2026
Direct answer
Handover is usable today; expansion stays evidence-led.
The production platform already supports shared, versioned context for humans and agents, attributable review, human OAuth, scoped agent credentials, MCP and CLI access, and the stable Handoff Continuity Record v1.0. Near-term work focuses on proving continuity outcomes, making migrations repeatable, improving navigation at scale, and expanding tested host workflows.
Production
Available now
Capabilities that are deployed, documented, and available through Handover's current product or open interfaces.
Attributable continuation and review
Immutable revisions preserve authorship. Humans and agents can discuss work, anchor annotations to files, mention collaborators, resolve feedback, and continue an existing handover.
Human OAuth and scoped agent identity
Interactive MCP clients authenticate as a person through browser OAuth. Unattended agents use named, revocable, scoped service credentials. Membership and organization isolation are enforced on the server.
Handoff Continuity Record v1.0
The stable, MIT-licensed JSON format defines objective, state, decisions, evidence, constraints, next action, ownership, and open review without prescribing transport or storage.
Current research
In validation
Shipped or public work where Handover is collecting reproducible evidence before making broader claims or changing a stable contract.
Continuity benchmark expansion
The open pilot currently covers three authored cases and two model systems. The next evidence gate is more cases, repeated runs, additional systems, and independently contributed tasks.
Protocol implementation feedback
Version 1.0 remains stable while real producers and receivers test conformance, extension namespacing, evidence resolution, and review portability.
Real handoff activation measurement
Acquisition is measured through a strict funnel that only counts continuation when a second authenticated actor adds a later revision to the acquired creator's handover.
Prioritized, not date-promised
Next
The next product and ecosystem problems Handover intends to address. Order can change when validation evidence or user needs change.
Repeatable Reporter migration tooling
Turn the completed 44pixels migration work into documented, resumable import tooling with dry runs, validation reports, stable source references, and explicit cutover checks.
Faster navigation across large knowledge spaces
Improve scanning, saved views, filtering, and movement between many handovers without weakening the current space and folder access boundaries.
More host recipes and Agent Skills
Expand tested setup recipes, reusable handoff skills, and end-to-end examples for the agent hosts people already use.
Evidence-gated
Later or conditional
Directions that are useful enough to investigate but will not be presented as commitments until demand, safety, and interoperability evidence support them.
A protocol v1.x revision
A compatible protocol revision will only be proposed when implementation feedback identifies a concrete, recurring gap that extensions cannot address cleanly.
Additional storage and orchestration integrations
New integrations will be selected by demonstrated continuation workflows, not by connector count. Canonical Handover records and access rules remain the boundary.
Broader protocol governance
A multi-party governance model is conditional on independent adoption and sustained external contribution. Handover currently publishes the format and records changes transparently.
How to read this roadmap
Dates describe evidence, not delivery promises.
“Available now” means deployed and documented. “In validation” means a capability or claim is being tested in public. “Next” expresses current priority without a committed date. “Conditional” work requires new evidence before it enters the delivery plan.
Protocol stability takes precedence over novelty. A new protocol version needs a recurring implementation gap, a compatibility analysis, and a public change record.