Eidos

Features

Write each part down once. Every tool works from it.

A canvas, a backlog, comments, git, and your own AI agent, built around one idea: every part of your project is its own page, a plain file shaped by a framework you choose.

Free for macOS, Windows, and Linux. No account, no subscription.

The model

Every tool works from the same page.

  • One markdown file per part of what you make, with a permanent id that survives every rename.
  • Tasks, canvas nodes, comments, and your agent all link to it by that id, and the page shows them back.
  • When something changes, your automations take the next step: a commit, a comment, a task, or an agent command. They stop to ask you where it matters.
  • All of it is plain text in one folder you own, and in git if you use it.
One blueprinta markdown file with a permanent id
On by default

Automations

When something happens in the project, it runs the steps you chain.

  • Triggers from every plugin: a spec, a task, a commit
  • Your AI Agent commands as steps
  • Asks before anything leaves your machine
The automation editor for Review new specs. When a blueprint is added to Specs, then four steps: run the team’s /review command with its answer as a comment, continue if the AI Agent says the review found gaps, ask whether to open a task, and add a task to close the gaps. Beside the steps: ask before the first run, where it runs, and that it is shared with the project.
Explore Automations

The core

Always there

Blueprints

One markdown file per part of what you make, checked against a framework you declare.

  • Typed properties and a permanent id on every file
  • Collections, templates, and properties you choose
  • A health check in the app and in a terminal
The Resume Playback blueprint open in Eidos: its id B-V63 and its path, a one-line summary, typed properties (variant, status, dates, domain, type, and a Depends On link to Profiles), then the body under the template’s headings, Intent, Assumptions, and Open Questions, with the sections listed down the right.
Explore Blueprints

The plugins

Four that change how you work, and the ones that keep it tidy.

On by default

AI Agent

The agent you already run, beside every page, with your team’s own slash commands.

  • Claude Code, Codex, or any ACP agent
  • Built-in and custom slash commands
  • /grill asks before anything is written
The AI Agent beside a blueprint with its slash command menu open: built-in commands such as /check and /task, the Git plugin’s /git-commit, /git-publish, and /git-fetch, and three the team added, /review, /release-notes, and /handoff.
Explore AI Agent
One switch to turn on

Backlog

A board where every task is a markdown file tied to its blueprint.

  • Your statuses, columns, types, and priorities
  • Subtasks, links, and checklists
  • Attached tasks beside every blueprint
The backlog board with To Do, In Progress, In Review, and Done columns. Each card shows its type icon, its id, its priority, who it is assigned to, and the blueprint it serves.
Explore Backlog
One switch to turn on

Canvas

A whiteboard whose nodes are your blueprints, drawn live from their files.

  • Nodes drawn live from your files
  • Sketches that become blueprints
  • Frames, flows, stickies, and pages
A canvas for a streaming app: blueprints grouped into Getting in, Finding a film, and Watching, joined by labelled arrows, each node edged in the colour of its status, with two sticky notes and a sketch.
Explore Canvas
On by default

Comments

Threads on a section, with reactions, saved in the file.

  • Anchored to a heading or a requirement
  • Reactions and @mentions
  • Readable in the file and in git
Comment threads at the foot of the Resume Playback blueprint. One is on Functional › REQ3: Tomás Reyes asks whether every film carries a credits marker, Claude answers and offers to add a requirement, and Maya Okafor says yes. Each message has reactions, and each thread has Close and Reply.
Explore Comments
On by default

Git

File history, diffs, commit, and publish, without a terminal.

Explore Git
On by default

Assets

Images and PDFs linked to the blueprints they belong to.

Explore Assets
On by default

Linter

One markdown style for the whole project, applied on every save.

Explore Linter
One switch to turn on

Terminal

Your own shell in the panel, started in the project.

Explore Terminal

Only what you need

Every plugin is a switch.

Switch a plugin off and your files stay exactly as they were. A new project starts with the AI Agent, Automations, Assets, Comments, and the Linter on, plus Git in a git repository. The Backlog, the Canvas, and the Terminal are one switch away under Built-in plugins.

The Built-in plugins page: the AI Agent, Automations, Assets, Comments, the Linter, Canvas, Backlog, and Git switched on, and Records, Metrics, Authorship, and the Terminal off, each with a line on what it does.

Works with what you use

Your agent, your repository, your editor.

  • Your agentClaude Code, Codex, or another agent that speaks ACP (the open Agent Client Protocol), signed in with your own account.
  • Your git hostGitHub, GitLab, or anywhere git pushes. Eidos commits, pulls, and publishes. The repository stays yours.
  • Your editorOpen any file in VS Code, Cursor, Zed, or another editor you list. The page follows your changes.
  • ObsidianExport a canvas as JSON Canvas, bring an Obsidian theme, or lay the ACE framework over a vault.
  • JiraBring a Jira Cloud board into the Backlog with the Jira plugin, and send your changes back one ticket at a time.
  • SpreadsheetsExport a collection or the backlog as CSV or an Excel workbook.

Why it’s different

What other apps don’t have.

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.

Eidos for…

Find the page written for you.

Each starts from your problem and shows the framework and plugins that fit your work.

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.

Free for macOS, Windows, and Linux. Your files stay plain text in a folder you own.