Repository navigation
Eunomia 2.0.3
Route connector data to vaults (#93)
Each connector now has a destination vault and optional rules (on each connector's setup page, under Connectors). For example, Pocket calls tagged work go to a team vault and everything else goes to your personal vault. Members of a vault see the records filed there; nobody else does.
- Move existing data re-files what a connector already synced under its current routing. It is safe to run again: nothing is moved twice and facts aren't duplicated.
- After merging vaults, repoint moves connectors that pointed at the old vault.
recall,reflect,searchandentities_searchtakevault_idsto read from several vaults in one call.
Routing applies to records synced from now on. Data synced before 2.0.3 stays in your personal vault until you choose Move existing data.
Your AI knows how to use its memory, whatever it runs in
The memory skill (when to recall, what to save, a short summary before finishing a task) now comes from the MCP server itself. It arrives as server instructions, a prompt and a resource, and in the recall and memory_write tool descriptions, so it works even where hooks can't be installed (for example, Claude Code's auto mode). Hooks in connect-agents.sh are now optional and fail quietly.
Onboarding: "Connect your AI"
The setup wizard and dashboard have step-by-step guides for Claude Code, Codex, ChatGPT and other MCP clients. Each guide creates its own token and fills in your URL and token. See docs/agents.md.
Rename API tokens
Settings → API tokens: click a token's name to rename it.
Faster under load
Built for hundreds of agents connected at once. On a 250-agent MCP load test: about 570 req/s, p99 under 1 s, no errors.
- Verified credentials are cached for 20 s. Revoking a token or session takes effect at once on the server that handled the revoke, and within 20 s on other replicas.
entities_searchpages inside the database instead of loading every entity.memory_writeno longer waits for the model's contradiction check: it runs in the background, sosupersededis no longer part of the result.- 8 database connections behind a first-come-first-served queue (
EUNOMIA_DB_CONNECTIONS,EUNOMIA_DB_INFLIGHT).
Updater
- Slow first start: after an update, the updater retries
docker compose upfor up to 30 minutes when a slow first start outlasts compose's health wait, and shows progress meanwhile. - Stuck services: if an update left a service stuck (for example the frontend in
Created), the next run starts it. Services you stop by hand are left alone.
Includes everything in 2.0.2.