October 29, 2026 · Standard 5.8.0
Eidos 0.17.0
This is an older release. The latest is 0.18.0. See what’s new in 0.18.0
Build your own workflows, and keep editing while an agent changes the same file
Automations take the next step for you when something happens in your project, your save now merges with what an agent, the CLI, or git changed in the same file, and a new project is the folder you choose, with nothing for an existing project to change.
Release highlights
- Automations you build yourself: When something happens in the project (a spec added, a task moved to Done, a commit), an automation runs the steps you chain: one that does something (a commit, a comment, a task, one of your AI Agent commands), one that asks you first, one that checks the result before going on.
- Your save merges with changes made outside the app: When an agent, the CLI, or git changes a blueprint, a doc, a draft, a Backlog task, a file-based record, or a canvas while you edit it, your save is merged with their change instead of refused.
- A Home you arrange: Add widget puts Health check, The project, Assigned to you, or On the board on your Home, and each widget's menu moves it or removes it.
- Tables you edit as a grid: In the editor a table is its cells: Tab, Enter, and the arrows walk them, the dots on its edges add a row or a column where you point, and a row's or a column's pill moves, aligns, or deletes it.
- Link and move blueprints from the page: Type `
- Develop a plugin without publishing it:
eidos plugin new <name>starts one from a template that builds,eidos plugin link <folder>runs your build in place of an install and reloads it as it rebuilds, andeidos plugin install github:<owner>/<repo>installs one from a GitHub release. - A section that links to another collection: A template section bound to a collection lists the items linked from a blueprint, with Add to make a new one and Link to pick one that exists.
- Usage and error reports, asked once: The app asks whether to send anonymous reports of what is used and what breaks, No as plain as Yes, and sends nothing until you answer.
New
Automations you build yourself
When something happens in the project (a spec added, a task moved to Done, a commit), an automation runs the steps you chain: one that does something (a commit, a comment, a task, one of your AI Agent commands), one that asks you first, one that checks the result before going on. Each reads back in sentences before you turn it on, can be tried once on something you already have, and asks before anything leaves your machine. It works the same from the app, a terminal, or an agent, keeps every run, and waits for your answer under Waiting on you. Ideas for this project has the AI Agent suggest ones that fit. Automations →
Your save merges with changes made outside the app
When an agent, the CLI, or git changes a blueprint, a doc, a draft, a Backlog task, a file-based record, or a canvas while you edit it, your save is merged with their change instead of refused. Edits that touch the same words, or the same value on a canvas, are still refused and shown as a conflict. Saving →
A Home you arrange
Add widget puts Health check, The project, Assigned to you, or On the board on your Home, and each widget's menu moves it or removes it. A framework editor can pick Use as the project's Home to set where everyone starts. The workbench →
Tables you edit as a grid
In the editor a table is its cells: Tab, Enter, and the arrows walk them, the dots on its edges add a row or a column where you point, and a row's or a column's pill moves, aligns, or deletes it. Pick a new table's size from a grid, or paste rows from a spreadsheet. Reading, Editor, Source →
Link and move blueprints from the page
Type [[ to link a blueprint, a task, or an asset, picked by title. Move to collection…, or a drag onto a collection's folder, moves a blueprint to another collection and says what will change first. eidos move →
Develop a plugin without publishing it
eidos plugin new <name> starts one from a template that builds, eidos plugin link <folder> runs your build in place of an install and reloads it as it rebuilds, and eidos plugin install github:<owner>/<repo> installs one from a GitHub release. Develop a plugin →
A section that links to another collection
A template section bound to a collection lists the items linked from a blueprint, with Add to make a new one and Link to pick one that exists. Templates →
Usage and error reports, asked once
The app asks whether to send anonymous reports of what is used and what breaks, No as plain as Yes, and sends nothing until you answer. Never a name, a path, or anything you wrote; Preferences shows every report as it left and turns them off. Privacy →
Improved
The Health Check beside your work
⌘J opens it in the Panel, as VS Code keeps its Problems: every finding on a line, grouped by file, each opening its file at the line it names. The workbench →
Hot keys and roles, with AI
Changing a key records the next one you press and says whether it is free, and Suggest a key with AI offers three that fit. A role is edited as its guidelines, and Create with AI writes a new one from who it is for. Settings →
A Community plugins page like Obsidian's
Browse the Registry's plugins, install, update, or uninstall one, and switch on Restricted mode to keep every plugin from outside from running. Plugins from outside →
Filters and columns from the table
Add filter sits after the last filter, Configure columns and the + on a header pick the columns, and dragging a header reorders them. Collections as tables →
Changed
A new project is the folder you choose
eidos install makes the project in the folder you run it in, every file there kept, and New Project offers the folder itself; Blueprints is no longer a default. Name a folder (eidos install <package> Blueprints) to keep the old layout. eidos install →
A root is now a project, and its Core
The app, the docs, and the CLI say project, and --project <path> is the flag (--root still works). The top-level docs, the blueprints, and their records are the project's Core, which the Project Core view opens on. Standards 5.7.0 and 5.8.0 change only words, so every project conforms as it is; eidos migrate sets the version. eidos migrate →
Automations and Assets on, Metrics off, in a new project
A project you already have keeps its switches. Switch any plugin under Built-in plugins. Plugins →
The Decisions plugin is gone
Decisions are a Records type now (eidos records add <blueprint> decision). A project still on Decisions gets a warning from eidos check: move it with eidos decisions migrate on 0.16 first, since 0.17 no longer has that command. Keeping decisions →
render replaces project
Use eidos backlog render, eidos comments render, and eidos records render; the old name still works. The Backlog from the shell →
Fixed
Names like Plans & Rates
A group, a collection, or a folder named as people say it was refused; it now gets a folder in your project's naming convention, and a name that cannot be a folder says why.
A new blueprint always lands in its collection
A title with a slash or ../ in it could write a file outside the project; the title now names one file in the blueprint's own folder.
The Board's count matches the board
The count beside Board in the sidebar is its open tasks, as the board says; it counted the done ones the board hides too.
Known limitations
The merge happens in the app: a save from the shell is refused as before when the file moved under it. An automation has no branches, loops, or timers, and a step that runs an AI Agent command waits for the app to be open.