Common questions
Current public tooling, identity authority, persistence and interoperability.
What should I install?
Use create-openagent@0.5.2 for the working starter, @openagentid/sdk@0.7.2 for an existing application, and optional @openagentid/oidc@0.2.0 for the OIDC provider. SDK/starter need Node 20+; OIDC needs Node 20.19+. These are public npm packages. Other component/language manifest names do not by themselves establish public registry distribution or feature parity.
Do I need Life or a hosted resolver?
No. The public local workspace persists keys, trust and replay/revocation on your single host. The application explicitly approves a public identity at the receiver. Shared deployments supply authoritative root/resolver/revocation and atomic durable replay adapters. LifeID, Blinds and Genesis are optional service integration choices.
Must every agent have a human root?
No. The verifier supports owned roots and explicitly authorized self roots. A self result has owner: null with an explicit self-root authorization/revision. It can receive normal application permissions under policy. A DID, signature or a kind named HMR does not establish personhood or automatically grant access.
Did Base replace Sigil?
The source supports a separate configurable EAS anchor adapter with a Base example. That is not proof of a completed Sigil migration, a default on-chain owner registry or a trusted deployed contract. The local developer path requires neither. Production integration explains the actual optional anchor boundary; version-specific names/signatures remain in the official published references.
What survives restart?
Private keys, exact DID/audience, explicit receiver trust, consumed challenge/proof IDs and revocations survive a local workspace restart. Opening does not mint a new key, restore revoked trust or repair corrupt state. Keep state private on persistent storage. Proofs remain short-lived and cannot be replayed. See identity.
Which avatar is default?
Autos with plush finish, on-face eyes and a square face crop. SpaceX and fifteen other families are optional; all share eighteen pill-bar expressions and live gaze/blink. Glasses and headphones are optional/combinable. An explicit avatarSkin: null selects the OAS Glyph. Avatar guide.
Is an avatar status proof of work?
No. SVG generation and the browser controller are presentation. Real activity must come from the application's authorized runtime channel. Demo status controls preview expressions; they do not certify an agent execution or profile binding.
Are keys portable across languages?
Do not assume the same seed restores the same encryption key in each implementation. The historical key facades have different derivation/binding contracts. ACT token vectors test a separate byte-format contract, not key custody or session interchangeability. Key management.
Does creating an MHR perform a threshold ceremony?
No. The published Rust 1.1.1 helper creates a keypair/local document. Actual multi-party control needs its ceremony/custody integration. MHR and FROST.
Where are the APIs?
The SDK provides a Fetch verification handler and public stateless character/SVG handler. The hosted character service is a rendering service, not DID/key CRUD or identity authority. OIDC routes belong to the configured provider. Older standalone, HTTP adapter and Arsenal contracts remain distinct.
Can an agent read these docs?
Use task-scoped Markdown, manifests and read-only docs MCP. Never send private keys, sessions, seeds or bearer proofs to a documentation search.