Handoff

Handoff is an open protocol for the moment a program needs a person. Your agent creates a request, a person answers the declared fields, and your code receives a durable record it can use exactly once.

Make a request

Choose an SDK

The contract in one picture

agent creates request  →  person answers typed fields  →  receipt is redeemed once
        durable wait   ←       delivery record         ←     one effect key

The protocol keeps the waiting and the evidence. Your application decides what to do with the answer.

A small request

import handoff

handoff.configure(base_url="https://your-handoffd.example/v1", api_key=...)

outcome = handoff.approve("Refund $2,400 to Acme Corp?", mode="gated")
if outcome and outcome.redeem("stripe:refund:ch_1B").first_redemption:
    stripe.refund("ch_1B")

The effect key makes a retry safe: the same answer cannot authorize the same effect twice.

What Handoff does and does not do

Handoff stores the request, routes a delivery, validates the answer, and records the receipt. It does not capture a stack, resume your process, or pretend that an email/SMS provider is included. Your code may wait with a blocking call, webhook, or poll, then apply the answer.

The public capability check needs no account:

curl https://handoff.omegas.dev/v1/meta

Authenticated operations require a credential minted by the deployment or a self-hosted instance.

Where to go next

Quickstart — run the first request.
The protocol — read the wire model and signing rules.
SDKs — install from the repository and use Python or TypeScript.
Conformance — run the compatibility suite locally.

⌘I

Overview

Continuity

Operator

Handoff

Make a request

Choose an SDK

The contract in one picture

A small request

What Handoff does and does not do

Where to go next

Make a request

Choose an SDK

​The contract in one picture

​A small request

​What Handoff does and does not do

​Where to go next

The contract in one picture

A small request

What Handoff does and does not do

Where to go next