Eidos

October 16, 2026 · Eidos plugin release 5.5.1

Eidos 0.15.0

This is an older release. The latest is 0.18.0. See what’s new in 0.18.0

Add plugins other people wrote, and move your decisions onto Records

Plugins from the Registry install pinned to their published files and run once your root switches one on and you allow it, and a root that keeps decisions moves them onto Records in one command.

Release highlights

  • Plugins from the Registry: eidos plugin install @owner/name adds a plugin someone else wrote, each file checked against the hash the Registry lists, and it runs only once the root switches it on and you allow it on your machine.
  • Publish to the Registry: eidos publish writes the listing for a framework, a configuration of plugin settings, or a new plugin version, with the address that proposes it.
  • Move your decisions onto Records: eidos decisions migrate --dry-run shows the move and --yes makes it: every file, id, and link stays where it is, and Records serves them from then on.

New

Plugins from the Registry

eidos plugin install @owner/name adds a plugin someone else wrote, each file checked against the hash the Registry lists, and it runs only once the root switches it on and you allow it on your machine. Plugins from outside →

Publish to the Registry

eidos publish writes the listing for a framework, a configuration of plugin settings, or a new plugin version, with the address that proposes it. eidos publish →

Move your decisions onto Records

eidos decisions migrate --dry-run shows the move and --yes makes it: every file, id, and link stays where it is, and Records serves them from then on. Keeping decisions →

Improved

Specs read as records of intent

A new root from the software framework writes specs with Requirements labelled REQ1, REQ2, and no Implementation Notes or Testing; a root you have keeps its own templates until you copy the new ones over. Templates →

Changed

eidos browser is gone

The page lives in the Eidos MD app, which puts eidos on your PATH too; eidos browser now points at the download. Eidos MD →

Decisions hides where it is unused

A root that keeps no decisions no longer sees the deprecated plugin anywhere; one that does keeps it working, marked deprecated, until it migrates.

The CI job runs only when the blueprints change

Run eidos ci --write github or --write gitlab again so a merge request that touches only code starts no job. Checking in CI →

A task's checklist is Acceptance Criteria again

The default task's checklist section is named Acceptance Criteria; a task written with Checklist reads the same and takes the new name when next saved.

Fixed

A record follows its tasks

A record kept as a file now follows a task whose id changes, as a decision always did.

Known limitations

A plugin from outside the package runs in the CLI and the app's server; its part of the page does not load yet. The Decisions plugin leaves in the next release, so migrate before then.