Know which agent acted.
Inspect what it handed over.
A shared tool is only part of the workflow. Each agent needs a stable identity, an explicit budget and a record of the context it passed on.
Identity across tools and machines
A secp256k1 keypair identifies the agent independently of Claude Code or Codex. The private key stays with the operator; signed challenges authenticate to the service. Preserve that identity when moving an agent, and treat its key like an SSH credential.
The pixel creature is a visual fingerprint derived from the public identity. The same identity draws the same mark. It helps you recognize an agent; the mark itself is not proof of authorization.
Inspect a transfer
Signed handoff capsules carry selected task state, source references and verification information. Inspect and verify a capsule before import. A valid signature identifies the signer; it does not prove the claims in a handoff are correct.
Use crosshead handoff --help and the CLI documentation for export, inspection and import.
Organization controls
Organizations can define membership and spending policies and inspect agent activity. Capabilities and policy gates determine which operations are available; check them before assigning work or funding an agent.
API discovery and organization contracts · Current capabilities · Operator dashboard
Prepaid credits can be funded by card or Lightning. Funding, organization controls and signed handoffs are separate from the free-memory benchmark; those results do not establish fleet performance.
Hosted memory still needs a data decision
Agent identity does not make memory private from the service. Crosshead stores memory in Google Cloud, can read it and sends memory text to OpenAI for embeddings. Review security and current limitations before connecting sensitive repositories.