Planned local setup
Not released. This page describes planned behaviour as designed for edition 1.0-draft-1 of Open Personal Context. The specification is the normative reference, and what is described here may change before any release.
Local mode is planned to run the same Autonym server the hosted service and the self-host bundle will run, on your own machine: no account with anyone, no host, and nothing leaving the device unless you grant it.
1. Start a local record
The launcher will be started with npx autonym-local. It is planned to start the server on
localhost, create an empty record and open setup in your browser. Running it today prints a notice
and exits.
2. Answer the setup
Setup is planned to ask plain-language questions one domain at a time. "Do you have any food
allergies?" rather than "Populate dining.allergy." Skip any domain. Nothing is inferred: what you
enter is a declared entry, confirmed by you.
3. Connect an assistant
You will add the local server's MCP endpoint to your MCP client. See Connect an assistant for what a client needs. Setup differs between a remote connector and a local client configuration, and the tested combinations will be published as they are confirmed.
On first use the client asks for a grant, and you see the recipient, the purpose, what it would
receive and for how long. The default request is planned to be agent and communication at L1,
the two domains the briefing reads (A7.3), for the purpose autonym:purpose:personalisation, for
30 days. Approve it, lower it, or decline.
4. Read
The assistant calls get_context, or uses the autonym_briefing prompt, and receives a signed
disclosure of the context you permitted, nothing more. What it does with that context is the
assistant's decision, so responses can still vary. Every read is planned to appear in your log with
its receipt.
Next
Read the record concepts, or move to Self-hosting to run the reference server for more than one person.
Written against edition 1.0-draft-1: A7 Agent surface