October 1, 2026 · Standard 5.5.0
Eidos 0.10.0
This is an older release. The latest is 0.18.0. See what’s new in 0.18.0
Choose who shapes the framework, and how each group starts a blueprint
Framework editors and owners decide who may change the framework, a group can start its blueprints from a template of its own, and the CLI takes standard 5.5.0, which eidos migrate brings a root up to.
Release highlights
- Framework editors and owners: Give a person Editor or Owner in the Access select on the Users page, or with
eidos users set <user> --access editor|owner. - Who you are, set once: Your name, email, technical capacity, and how you like to be helped live under Preferences → Me, or
eidos whoami --global, and are copied into each root'sme.mdas it opens; your role stays each root's. - A default template for each group:
eidos configure:group set <collection> <group> --default-variant <variant>, or Framework Settings → Folders, gives a group its own default variant, andeidos newand the new-blueprint dialog start from it. - Start a root from another root's setup:
eidos install <root> --setup-only, or Copy another root's setup in the desktop app's setup, brings over its framework, templates, roles, and plugin settings, and nothing written in it. - Let Claude Code run eidos: Allow Claude Code to run eidos on the AI Agent's page, or the desktop app's setup, adds the rule Claude Code needs to
.claude/settings.json, shown to you first, so an agent is no longer stopped at everyeidoscommand. - Images nothing links to are cleaned up: With Assets on, an image whose last link you delete or save away is removed a few minutes later, and the Assets page lets you delete it now or keep it.
New
Framework editors and owners
Give a person Editor or Owner in the Access select on the Users page, or with eidos users set <user> --access editor|owner. Anyone else reads the framework's settings pages without changing them, Edit offers to make you an editor, and a configure: command refuses and says who the editors are. A root that marks nobody leaves everyone an editor. eidos users →
Who you are, set once
Your name, email, technical capacity, and how you like to be helped live under Preferences → Me, or eidos whoami --global, and are copied into each root's me.md as it opens; your role stays each root's. Ask your AI fills the form from the AI Agent for you to review before you save. Your me.md →
A default template for each group
eidos configure:group set <collection> <group> --default-variant <variant>, or Framework Settings → Folders, gives a group its own default variant, and eidos new and the new-blueprint dialog start from it. A collection may now have no default, and then you pick one with --variant. Variants →
Start a root from another root's setup
eidos install <root> --setup-only, or Copy another root's setup in the desktop app's setup, brings over its framework, templates, roles, and plugin settings, and nothing written in it. eidos install →
Let Claude Code run eidos
Allow Claude Code to run eidos on the AI Agent's page, or the desktop app's setup, adds the rule Claude Code needs to .claude/settings.json, shown to you first, so an agent is no longer stopped at every eidos command. Letting Claude Code run eidos →
Images nothing links to are cleaned up
With Assets on, an image whose last link you delete or save away is removed a few minutes later, and the Assets page lets you delete it now or keep it. Turn off remove_unlinked to keep every image. Assets →
Improved
Rename a blueprint with its file
eidos move @<id> --title "<Title>", or eidos mv, sets the title, renames the file, and rewrites every link to it, the id kept. eidos move →
Agents log fewer, weightier decisions
An agent logs a decision only when it changes something already settled, not every choice it makes while drafting, and a call you settled in the conversation is logged as yours. Decisions →
Open in a new tab
Middle-click a link, a sidebar entry, a search result, a table row, or a card on the board to open it in a new tab, the desktop app's or the browser's, and keep the page you are on. A reader shown in a modal has Open in new tab and Open in this tab where it had Expand. The workbench →
Changed
Standard 5.5.0
A group may name its default variant, a collection marking none has no default, the files kept on one machine are called local, and the Framework Owner role leaves the standard. Run eidos migrate to make the hop: it marks the first variant the default wherever a collection marked none, so the root reads as it did. The hops →
Plato is now the AI Agent
The plugin is AI Agent and its view Chat. A root that used Plato moves over by itself the first time it opens, and plato still works in your scripts. AI Agent →
A plugin's users are the plugin's
The AI Agent's @agent is listed on the Users page as the plugin's: its name, alias, and role are read-only, it has no email or access, and it stays while the plugin is on. It runs a configure: command only once you turn on Let the agent change the framework on the AI Agent's page, unless the root marks no person an editor. A plugin's users →
Local, not private
What stays on one machine and is never committed is called local and shows a laptop. --local is the flag for a local draft or canvas; --private still works. eidos draft →
Fixed
A very long title is logged
eidos decisions add and eidos backlog add failed with ENAMETOOLONG; the file name is now cut to fit and the whole title kept.
An install leaves local files behind
eidos install <folder> copied each person's plugin local.yaml and local/ into the new root; it no longer does.
Reading a root writes nothing
eidos check, eidos migrate --dry-run, and any command that loaded a root wrote the Linter's default settings, leaving an untracked .eidos/plugins/linter/settings.yaml; the file is now written only when you change a Linter setting or switch the plugin on. Linter →