AI & agents

Live human and agent handoff

Transfers control of a running agent task between the agent and a person, with exactly one party in control at a time.

RoadmapEngine edition 5f8ea3af

What it does

The engine contains a handoff store: a durable session that hands a durable run to a human with a bounded, redacted context snapshot, an audited transition log and reconnect from a cursor. Every ownership change is an atomic compare-and-swap. No route or command mounts it, so it is a roadmap capability.

How it works

A handoff session references a durable run and builds a bounded snapshot of its input and messages, run through the same key-name redactor used by approvals. Control moves by a compare-and-swap that commits in the same transaction as its audit event, so there is no window in which control changed without a record. A transfer completes solely when the receiving party acknowledges it, and a human action requires the human participant identity.

The session log has a monotonic cursor, replay after a cursor, an explicit expired-cursor response and bounded retention, the same contract as the retrieval session log. Audit events carry a content hash of an action payload, not the payload.

Where you reach it

  • LibraryHandoffStore (Rust crate kynetra-agents; not mounted by the server)

Limits

  • Not reachable through any route, command or setting of the private-preview server.
  • Redaction works on key names, so a secret in a free-text value is not removed from a snapshot.
  • It depends on durable runs, which are themselves unmounted.

Evidence

  • Tests12 test functions cover exclusive control, atomic transfer and acknowledgement, identity checks, bounded snapshots, replay and expired cursors

Test coverage is listed as present in the engine repository at this edition. This page does not report test results.

KynetraDB is in private preview

This is not available in the preview. Request a preview to discuss the current scope.