Eidos

Free for macOS, Windows, and Linux

Plan what you’re making, and keep it straight as it grows.

Eidos gives every part of your project its own page: a character, a feature, an episode. A board, a canvas, comments, and your AI agent all work from those pages, kept as plain files in a folder you own.

Made foran appa novel seriesa worlda gamea channela coursea businessa renovation

Free forever, no account needed. Viewing, commenting, and agents are free online too.

Eidos open on a fantasy series bible. The character page for Ilse Varro is in the middle, the collections (places, factions, characters, arcs, chapters) are in the sidebar, and the AI Agent beside it points out two places where part two contradicts her page, changing nothing until the author answers.
A character page in a series bible, and an agent that checks continuity and asks before it writes.
Eidos open on a streaming app. The Resume Playback blueprint is in the middle, the specs collection is in the sidebar, and the AI Agent beside it asks three scoping questions before it changes anything.
A feature blueprint for an app, and the same agent pressing on what is out of scope.

Works with

How it works

Three steps, whatever you make.

Write it down once, and everyone works from the same page, your AI agent included.

  1. Pick a framework for your kind of project

    Choose the one closest to your work: software, a book, a course, a channel. It sets the kinds of pages you keep, a template for each, and the fields they carry. Change it whenever it stops fitting.

  2. Give each part its own page

    A character, a feature, an episode: each is one markdown page saying what it is and why. Its id never changes, so links survive a rename, and the health check flags any page that’s missing something.

  3. Plan and talk around it

    Sketch on the canvas, plan on the board, comment, and ask your agent. Everything links back to the same page, so nothing falls out of date.

Built in

Every tool works from the same pages.

A canvas, a backlog, comments, git, and your own AI agent, in one free app. Each links to the page it’s about. Switch one off and your files stay as they were.

Your own agent, with your team’s commands

Claude Code, Codex, or the agent you already use, beside every page, with what you have open as context. Use /grill to poke holes in a draft, /task to turn a decision into a task, and add commands of your own for the team.

Explore AI Agent
The AI Agent beside a blueprint, its slash command menu open: built-in commands such as /check and /task, the Git plugin’s /git-commit, and three custom commands the team added, /review, /release-notes, and /handoff.

Tasks linked to what they build

A real board made of markdown: task types, subtasks, checklists, and your own statuses. Every task links to the blueprint it’s for. When the work ships, the task closes and the blueprint stays as the record.

Explore Backlog
The backlog board with To Do, In Progress, In Review, and Done columns, each card naming the blueprint it serves.

Draw how the parts connect

Blueprints drawn live from their files, with groups, labelled arrows, sticky notes, and sketches you turn into blueprints when they’re ready.

Explore Canvas
A canvas for book one of a novel series: places, people, and chapters in three frames, joined by labelled arrows, with a sticky note and a sketch for book three.

The discussion stays on the line it is about

Threads on a section, with reactions and @mentions, from people and agents. They’re saved in the file, so every reader and every diff sees them.

Explore Comments
A blueprint at its Out of Scope section, a comment thread anchored there with a reaction, and the tasks attached to the blueprint in the side panel.

History without a terminal

Every blueprint’s history and diffs, commit and publish in a click, and auto save with commit messages your agent writes.

Explore Git
A diff of a blueprint against an earlier commit, with added lines highlighted.

Also built in

  • AssetsImages and PDFs linked to the blueprints they belong to, renamed without breaking a link.
  • LinterOne markdown style for the whole project, applied every time a file is saved.
  • TerminalYour own shell in the panel, started in the project.
  • Several projectsEvery project you work on open at once, each in a tab of its own.
  • The RegistryFrameworks to start from, and a place to publish your own.
  • The CLIThe same core as one command, for scripts, CI, and any agent with a shell.

Where Eidos fits

Not a wiki, a tracker, or a prompt kit.

Each does its own job well. None keeps an up-to-date description of what you’re making in your own files. Eidos does that one thing, and works alongside the rest.

  • WikisNotion, Confluence

    Good at
    Everyone in the company reads and comments, with nothing to install.
    What it leaves open
    A template is only a starting page. Nothing checks it later, and it lives away from the work it describes.
  • Work trackersJira, Linear

    Good at
    Planning and tracking the work, more and more with agents in the loop.
    What it leaves open
    Specs hang off issues that close, so what the product is gets archived with the work.
  • Spec-driven AI toolsGitHub Spec Kit, Kiro, OpenSpec

    Good at
    Getting an agent to plan in writing before it writes code.
    What it leaves open
    Built around the agent and the next change. The agent drafts the spec, and the audience, market, and architecture have no home.
  • A docs folder and AGENTS.mdPlain markdown

    Good at
    Free, instant, and read by every editor and agent.
    What it leaves open
    No template to check against and no permanent ids, so nothing notices a file drifting or a link breaking.

Eidos

What you are making, kept up to date.

  • One file per part of what you make, with a permanent id
  • Checked against a framework you choose
  • Tasks, canvas nodes, and comments that link to those files
  • Your own agent, your folder, and a free app

Other apps have a canvas, a board, or an agent panel. What Eidos adds is underneath: every part of your project is its own markdown file, checked against templates you chose, with tasks that link to it. All in one free, local app.

Frameworks

Start from a framework for your kind of work.

A framework is the shape of your files: the kinds of pages, their templates, and their fields. Install one whole, take a single collection from it, or make and publish your own.

An app, a service, or a system

Software@BuildableWorks/software

Frames for architecture, audience, criteria, and market, and specs grouped by domain.

  • Frames
  • Specs
See it in the Registry

A book, a long argument, or a course

Book@BuildableWorks/book

Frames for premise, reader, voice, and market, and chapters grouped by part.

  • Frames
  • Chapters
See it in the Registry

A video channel, a podcast, or a stream

Channel@The-Virtual-Panda/channel

Videos and posts by series, pages, a content calendar, a brand kit, and a rate card.

  • The Channel
  • Videos
  • Posts
  • Pages
See it in the Registry

A fictional world, for a series or a table

World@The-Virtual-Panda/world

Places by region, factions, characters, arcs by campaign, a history, and a player role that sees only what is revealed.

  • The World
  • Places
  • Factions
  • Characters
  • Arcs
See it in the Registry

Human-first

The human authors. The agent facilitates.

A plan can only check the work if it comes from somewhere else. Let an agent write both, and everything agrees while nobody decided anything.

So the intent, the scope, and the decisions stay with a person. Your agent reads the files, asks where you were vague, and pushes hardest on scope. Eidos never writes a blueprint for you, and the agent works only when you ask.

A blueprint nobody thought through is worse than none.
Resume Playback

Help me tighten the Out of Scope before Tomás starts on it.

Before I add anything, three questions, because each one changes what the spec promises:

  1. Should trailers and extras resume too?
  2. If a viewer removes a film from their history, should it still resume?
  3. Is live sync between two devices a goal, or a non-goal?

I won’t write any of these in until you’ve answered.

Free, local, yours

Free where you work, and free to share.

No account, no subscription, no trial. Online, viewers, commenters, and agents are free.

See what’s free and what’s paid
  • Nothing held back

    The desktop app, the CLI, and every plugin are free for personal and commercial work. Nothing is a trial.

  • An open standard underneath

    Blueprints are plain markdown in your repo, written to EIDOS.md, an open standard under Apache-2.0. Eidos MD is what sits on top, and your files never depend on it.

  • Your work stays yours

    A project is a folder on your machine, and nothing leaves it unless you put it online. The AI is the agent you already run. The app sends only anonymous usage reports, and one switch turns them off.

  • Pay only to edit online

    Online, you and two other editors work free, with 1 GB. Past that, a seat is $4.99 a month per editor and covers every project they’re invited to.

Questions

What people ask first.

Is it only for software?

No. The same app plans a novel series, a world, a channel, a course, a business, or a renovation. Each kind of project starts from its own framework, with the page types and templates that work needs.

What does it cost, and which AI does it use?

The app, the CLI, and every plugin are free, with no account. Online, viewers, commenters, and agents are free, and you plus two editors edit free. Past that, a seat is $4.99 a month per editor (pricing). Eidos has no AI of its own: it runs Claude Code, Codex, or the agent you already use, only when you ask.

Where do my files live?

On your computer, in a folder you choose, as plain markdown. Nothing you write is uploaded unless you put a project online, and then it stays a plain folder on your machine too. How Eidos handles your data.

Do I need to know git?

No. A project is a folder of markdown files, and the app saves as you go. If you use git, Eidos shows each page’s history and commits, pulls, and publishes in a click.

Can people without the app see my work?

Yes. Put a project online and invite them. Viewers and commenters are free and see changes live in the desktop app. Pages are also plain markdown, readable on GitHub or GitLab. There’s no browser view of a project yet.

Does it work with Jira?

Yes, through the Jira plugin. It brings a Jira Cloud board into the Backlog, issues as tasks and comments as threads, and sends your changes back one ticket at a time.

What if I stop using Eidos?

Your work stays exactly where it is. Pages are plain markdown written to an open standard, so any editor, agent, or other tool reads them, with nothing to export.

εἶδος eidos, from the Greek: the form or essence of a thing.

Write down what you’re making.

Download Eidos MD, open a folder, and start from the framework closest to your work. You can reshape it all later.

macOS (Apple Silicon and Intel) · Windows 10 and 11 · Linux (AppImage and deb)

Rather have the terminal?
curl -fsSL https://eidosmd.com/install | sh