Releases

What each release of Eidos lets you do, newest first. Each one opens with what you can do now and a one-line summary, then what is New, Improved, Changed, and Fixed. The desktop app and the local page show the same notes under What’s new.

The current release is 0.9.0, carrying standard 5.4.0.

npm install -g eidosmd@latest
eidos --version          # the CLI, and the standard it carries
eidos check              # says once when a root is behind, and points at migrate

0.9.0 · 2026-09-29 · Standard unchanged

Keep what was decided beside the blueprints it shapes

Decisions become records you confirm from an inbox and read in each blueprint they were made for, the desktop app opens pages as tabs, and the look is yours through themes.

New: Decisions. Switch the plugin on and log a decision in a line, typed as Development, Scope, or Meeting, for the blueprints and tasks it concerns. It waits in an inbox until someone confirms it, can be handed to a person, and shows in each blueprint in the section its template gives decisions. An agent logs the choices it made as itself, for you to confirm. Decisions →
New: Tabs and Search. In the desktop app, pages open as tabs above the main area, remembered for each root; Focus mode keeps one page at a time. Search stays open in the sidebar beside the page, and ⌘F finds text in the page you are on. The workbench →
New: Themes. Pick a base color scheme, an accent, fonts, and a theme: six are included, and you can make your own in the theme editor or import one from a CSS file or an Obsidian vault. Your look holds on every root and changes nobody else’s. Settings →
New: Diagrams and highlighted code. A mermaid block is drawn as its diagram, and a code block fenced with a language is coloured in the theme’s colours, in the reader and the editor alike. Reading, Editor, Source →
New: Export to PDF, and tasks to a spreadsheet. The ⋮ beside a title exports the file open to PDF, and the Backlog table exports the view you are on, or every task, as CSV or Excel. Backlog →
Improved: Comments that wait on you. The Comments sidebar lists the open threads you wrote in or are mentioned in, on work not yet done, and a table of every thread filters and saves views. Comments →
Improved: Put a view where you want it. Drag Plato, the Terminal, or any view onto another sector, or right-click it for Move to; it stays there on every root. The workbench →
Improved: Test Plato’s agent. A bar on Plato’s page checks the agent step by step and says in plain words what to do for the step that failed. Plato →
Changed: A reader’s head keeps what changes the file. Reading, Editor, and Source, Delete, Find in file, and Move blueprint to… are in the ⋮ beside the title. Reading, Editor, Source →
Changed: The desktop app’s strip holds roots. Its + is Open Another Root and Close Tab is Close Root, since a tab is now a page inside a root. The Desktop App →
Fixed: Codex signs in with an OpenAI key. With only OPENAI_API_KEY set, Codex opened no session; Plato now signs it in with the key.
Fixed: Images stay drawn. An embedded image no longer goes blank when you show a sidebar or save a setting, and one whose file is gone says so.

Known limitations: the community theme gallery is not built yet, so a theme is shared as its CSS file.

0.8.0 · 2026-09-24 · Standard unchanged

Run Eidos MD on Windows

Eidos MD comes to Windows as a signed installer, New Root… lets Plato read the product you already have and propose its framework, and agents comment as themselves.

New: Eidos MD for Windows. Download the signed installer for Windows 10 and 11 and it installs for you alone, with no administrator prompt, then updates itself in place as on the Mac and Linux. The Desktop App →
New: Set up a root with Plato. New Root… opens a setup page that keeps you there until the root is made: choose where in the folder it goes, then let Plato read what is already there, say which Registry frameworks fit, and propose one of its own when none does. Use these fills the steps, and nothing is written until Create root. The Desktop App →
New: Agents comment as themselves. eidos users add "<name>" --agent adds an agent to the root’s users, and eidos comments add --as <alias> signs a comment as it, so an agent working in your checkout no longer posts as you. Plato signs as a user of its own, set in Plato’s settings. Comments →
New: Save a filtered page as a view. Filter the board, the Backlog table, the Drafts, or a collection’s table, then Save as view, shared with the root or private to you, and move it from one to the other from its menu. Filters live in the page’s address, and every table has a search that finds a task by its id. Saved views →
New: The Registry in the app. Browse every framework the Registry publishes and include a whole one, or a single collection, variant, or role, in the root you are in. The Registry →
Improved: A grilling fits the person. Plato’s /grill asks only what your role can answer and keeps the rest for the closing list, with the role that decides each. Plato →
Improved: Settings you can scan. Every settings page has an icon, the Backlog’s properties each fit on one line with a (?) for what they are, and every on or off setting is a switch.
Changed: Fewer toasts. A success the page already shows no longer toasts; the toasts that stay say what they are about.
Changed: Shared and private. The page, the CLI, and the docs say shared or private, never personal or public. --private is the flag for a private draft; --personal still works.
Changed: Labels are no longer part of a task. Declare a labels List property in the Backlog’s settings to keep them; a task file that still carries the key keeps it as written.
Changed: A new license. Eidos is free for any use, commercial included, under PolyForm Strict with a commercial permission; the code stays closed.
Fixed: The mouse’s back and forward buttons go back and forward in the desktop app, one step a press, and Source control’s commit box stays in view with many changes.

Known limitations: Plato reads a folder through its own tools as well as the app’s, and keeps those inside the folder by its instructions alone.

0.7.2 · 2026-09-23 · Standard unchanged

Open several roots at once in Eidos MD, the desktop app

Eidos MD arrives free for the Mac and Linux, every root opens on a Home that shows what needs you first, and Git can write its commit messages with Plato.

New: Eidos MD, the desktop app. Keep several roots open as tabs in one window, each served by its own process, with your recent roots a click away. It is signed and notarized for the Mac and updates itself in place. The Desktop App →
New: A Home for every root. A root opens on what needs you first: the health check’s findings, then the Backlog tasks assigned to you and the board, then the blueprints by collection. The Browser →
New: Commit and publish with Plato. Summarize asks Plato for the commit message of the changes you ticked, and Publish pushes the branch. Turn on auto save for your machine and Git commits every few minutes, publishing as it goes if you like. Git →
New: Plato can grill you. Type /grill and Plato questions what is open, one question at a time, until the gaps are found, then offers to write what you decided into the blueprint. Plato →
Improved: A root is called by its product. Name it with eidos setup --product or the pencil on the Home. Without a name, a root takes its repository’s name instead of its folder’s.
Improved: Save stays in reach. A reader’s bar stays at the top as you scroll, with Save, Discard, and Delete on the right and the id to copy on the left. Leaving an editor saves what you changed first.
Changed: A property shows on a card only when you say so. Switch Card on for each Backlog property that should show on the board’s cards; 0.7.1 showed every one.
Fixed: Escape and saving. Escape closes one layer at a time instead of everything open, and saving no longer warns that the file changed on disk.

Known limitations: The Windows build waits on code signing, so the desktop app is for the Mac and Linux for now.

0.7.1 · 2026-09-22 · Standard unchanged

Pick up a Plato conversation after the agent restarts

Plato conversations survive an agent restart, and the Backlog’s own properties show on its cards and in its table.

New: Filter and remove tasks from the shell. eidos backlog --where key=value filters by any key a task carries, as eidos list --where does, and eidos backlog remove <task> deletes one. Backlog →
Improved: Plato remembers the conversation. After the agent restarts, the next message reloads the agent’s own session where it offers one, or starts a new session told the turns so far. Plato →
Improved: Your properties on the board. The Backlog’s own properties show on a task’s card and as columns of the Backlog table.
Improved: Comments follow a renamed task. A task’s threads address it by its T- id, so a rename leaves them where they are. eidos backlog ids moves the ones that still name it by file.
Improved: The editor lines up. The text starts where the title field does, with the block handles in the margin beside it.

0.7.0 · 2026-09-22 · Standard unchanged

Rename a blueprint or a task without breaking a link

Blueprints and tasks get generated ids, so two can share a title and a rename strands nothing, and a task now reads and edits like a blueprint.

New: Generated ids. A new blueprint gets an id such as B-1AC3 instead of one taken from its title. The file is still named for the title, --id still sets one by hand, and existing ids stay. eidos reid →
New: Move a root onto generated ids. eidos reid --all gives every blueprint a generated id, and every comment thread, canvas node, task, and asset link that names an old one follows.
New: Tasks have ids. Each task gets a T- id that every eidos backlog command takes, so dependencies and parents survive a rename. eidos backlog ids gives ids to the tasks a root already has. Backlog →
New: Filter by your own properties. Switch Filter on for a Backlog property and it becomes a dropdown over the board and the tables.
Improved: A task reads like a blueprint. It opens in the blueprint reader’s frame, and New task asks for a type and a title before it makes the file.
Improved: Pages load in their own shape. Every table and view draws a skeleton of what is coming while it waits, instead of a blank.
Changed: Two settings moved. The on-save rules are on the Linter’s page, and the check’s switches are on the Health Check page.
Fixed: A view that cannot read says so. A failed read shows its error instead of an empty view.

0.6.4 · 2026-09-22 · Standard unchanged

Bring your own headings without a wall of warnings

A heading the template does not declare is no longer a warning, and each section rule is now a switch the root shares.

New: Every section rule is a switch. Set them in .eidos/plugins/eidosmd/settings.yaml (check.warn_unknown_sections off, check.warn_missing_sections and check.warn_section_order on), with eidos setup --warn-unknown-sections on and its siblings, or from Checks on the Plugins page. What check reports →
Improved: The order rule minds only the template. It compares the headings the template declares, so a heading of your own never puts the rest out of order.
Changed: Unknown sections are quiet by default. A template is the starting point, not a fence, so section-unknown stays off unless the root turns it on.

0.6.3 · 2026-09-22 · Standard unchanged

Start with Plato and the Linter already on

Plato and the Linter are on in every root that never switched them, and the Properties page draws again.

Improved: Framework Settings in a clearer order. Its pages read Root, Folders, Templates, Properties, Vocabulary, Roles, Me, and every plugin the package ships is a core plugin. Plugins →
Changed: Plato and the Linter are on by default. Plato waits in the Auxiliary Sidebar and starts no agent until you send a message. The Linter writes its default rules the first time it runs and applies them on every save. eidos plugin disable turns either off.
Fixed: The Properties page draws again. In 0.6.2 it was empty whenever Canvas Maps was on. A page that fails to draw now says so where it sat.

0.6.2 · 2026-09-22 · Standard unchanged

Read the page in Spanish or Portuguese

The local page reads in English, Spanish, and Portuguese, following your browser’s language or the one you pick.

New: The page in three languages. Pick one under Preferences → Appearance. System, the default, follows the languages your browser asks for. The choice is yours alone, kept in local.yaml. The browser →
New: Plugins translate too. A plugin brings its own words, so one from outside the package translates as well. What your framework names (a collection, a property, a term) stays as you wrote it.

0.6.1 · 2026-09-22 · Standard unchanged

Keep a canvas to yourself

A canvas can now be private: one person’s, on one machine, never committed.

New: Private canvases. The New canvas form asks public or private, and the menu beside a canvas’s title flips it and moves the file. A private canvas wears a struck eye. Canvas Maps →
New: Private from the shell. eidos canvas new --private and eidos canvas move <id> public|private do the same.

0.6.0 · 2026-09-21 · Standard unchanged

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, Plato, Assets, Linter, and Terminal arrive.

New: Plugins you switch per root. plugins.<name> in settings.yaml turns one on for everyone, local.yaml overrides it on your machine, and eidos plugin, eidos setup, and the Plugins page switch them. Plugins →
New: 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 →
New: Five plugins. Backlog keeps tasks beside the blueprints they serve, Plato 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.
New: Drafts. eidos draft starts a blueprint before it belongs to a collection, shared or personal, and publishes it under new’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.git is plugins.git. Run eidos migrate to rewrite it and move a root’s canvas maps and their comments into the plugins’ folders.

0.5.0 · 2026-09-19 · Standard 5.4.0

Say who owns each folder at the root

The CLI takes standard 5.4.0, in which each folder at the root belongs to its owner: the standard, a tool, or you.

New: Folders from the shell and the browser. eidos configure:folder add <name> [--owned-by @<tool>/<kind>] declares one, and Framework Settings → Folders shows and edits each folder’s owner. Commands →
Improved: The check leaves tools alone. A tool’s owner is never faulted, a malformed one is framework-invalid, and folder-missing names the owner. What check reports →
Changed: owned_by replaces type. In Framework.yaml, "@eidos/collections" is a collection, "@<tool>/<kind>" a tool’s folder, and no owned_by your own. Run eidos migrate to make the hop in place. The root →

0.4.0 · 2026-09-18 · Standard unchanged, plugin release 5.3.1

Install a framework from the Registry in one command

eidos install takes the place of init and adds a published framework, a repository, or a folder to a new or existing root, and the Registry opens.

New: eidos install. Give it a Registry package (@owner/name), a GitHub owner/repo@tag or git URL, a repository on this machine, or a folder. On an existing root it adds what the source has that the root lacks, and always shows the plan first. Install →
New: The Registry. eidosmd.com/registry lists every published framework, with a page per package and its install counts. An install sends one request with the package name and nothing else; --offline or EIDOS_NO_TELEMETRY skips it.
Improved: The seeds are roots. The bundled software, book, and research seeds are laid out the way plugin release 5.3.1 lays them out, so the copy in the CLI and the published package are the same thing.
Changed: init is now install. init stays as a hidden alias for this one release.

0.3.1 · 2026-09-18 · Standard unchanged

Dropdowns in dialogs open where you can see them

A browser patch: dropdowns inside dialogs, canvas exports, and a property’s options behave.

Improved: A property’s options are rows. Each sits in the order it runs, with its place, arrows, and a remove, and an Add field below.
Fixed: Dropdowns in dialogs. Every dropdown inside a dialog opened behind it; it now opens above.
Fixed: Canvas exports. An export no longer paints black boxes over edge labels or a selection, and hover handles stay out of the image.
Fixed: Editing in place. A card’s editor fits the field it edits, and a table filter lists a property’s options in their declared order.

0.3.0 · 2026-09-18 · Standard 5.3.0

Edit the framework from the shell

The CLI takes standard 5.3.0 and edits the framework from the shell with a plan shown first, and the browser reads every top-level doc.

New: eidos configure. eidos configure:<noun> <operation> edits properties, collections, folders, groups, variants, terms, top-level docs, and roles, printing each change as a plan before it runs and rewriting every link a move breaks. Commands →
New: One blueprint’s frontmatter. eidos property get|set|unset @<blueprint> edits it, typed by the Properties table.
New: Top-level docs in the browser. A top-level doc reads in the same reader as a blueprint and can be added from the sidebar, and Show in Finder (Explorer, Files) sits beside Editor. The browser →
Improved: Edits stay yours. A change on disk never replaces what you are editing, and a rename is a git mv where git is on.
Improved: The check sees the whole root. New findings cover a value off a property’s list, an unclosed region, and a file or folder the framework does not describe, and strictness is the root’s own setting. What check reports →
Changed: Standard 5.3.0. Every folder at the root is declared under folders and every file under top_level. eidos migrate makes each hop in place and reports what only you can decide. The hops →

0.2.0 · 2026-09-17 · Standard 5.0.0

Work in the standard’s new vocabulary

The CLI takes standard 5.0.0, which renames its core words and keeps the framework document in one form, and eidos migrate moves a root in one pass.

New: Roles. Roles live under .eidos/roles/. eidos roles lists them and eidos whoami says who is in the seat.
New: The Vocabulary is back. It returns to the framework document, and check reports a near-miss as term-near-miss.
Changed: New words. Schema is Properties, a shape is a template, a flavor is a variant, and _eidos/ is .eidos/ again. Run eidos migrate to convert a markdown root or move a 4.x root.
Changed: One framework document. Framework.yaml is its one form, with the index inside it.
Changed: Versions are the CLI’s. The framing collection and the root’s versions leave the standard, and eidos version keeps the record.

0.1.0 · 2026-09-15 · Standard 4.5.0

Start a root and check it from the shell

The first release of the eidos CLI: make a root from a bundled seed, write blueprints, check them, and read them in a local web page.

New: The commands. init from a bundled seed, seeds, framework, list, show, new, check, index, roles, and whoami, with --root on every one.
New: Instructions for your agent. instructions and agents hand a coding agent what it needs to work in the root.
New: eidos browser. The root in a local web page.

Versioning: the standard, the CLI, and the plugin version separately.
Commands