Turn on only what your root needs
The CLI becomes a host for plugins, the browser becomes a workbench in VS Code's shape, and Backlog, AI Agent, Assets, Linter, and Terminal arrive.
New
Plugins you switch per root
plugins.<name>insettings.yamlturns one on for everyone,local.yamloverrides it on your machine, andeidos plugin,eidos setup, and the Plugins page switch them. Plugins →A workbench
A command center and palette, an Activity Bar of views, and an Auxiliary Sidebar and a Panel the plugins fill, each remembered per person. The reader has Reading, Editor, and Source. The browser →
Five plugins
Backlog keeps tasks beside the blueprints they serve, the AI Agent talks to the coding agent you already run, Assets manages the files that are not markdown, Linter keeps markdown in one form on save, and Terminal opens your shell in the Panel.
Drafts
eidos draftstarts a blueprint before it belongs to a collection, shared or personal, and publishes it undernew's rules.eidos draft→
Improved
One record of conversation
Comments keep one file per thread, on a blueprint, a doc, a canvas page, or a task, and Source control commits what changed under the root.
Changed
features.gitisplugins.gitRun
eidos migrateto rewrite it and move a root's canvas maps and their comments into the plugins' folders.