Your project takes the next step for you.
Your agent reviews a new spec. A task moved to Done gets committed, and published once you say so. An automation is a trigger plus the steps you chain after it, built by you, for how your project works. It reads back in plain sentences before it runs.
Free for macOS, Windows, and Linux. No account, no subscription.
Do, ask, check
Three kinds of step, chained in order
A Do step runs a plugin’s action: a commit, a pull or push, a task added or moved, a comment, or one of your AI Agent’s custom slash commands. An Ask me step waits for your answer, in your words. A Continue if step goes on only when the step before found something, or the agent says yes to your question. Each step gets the result of the one before.
- Triggers: a blueprint added or saved, a task added or moved, a record, a commit, a push or pull, a view, or a command
- Run one by name from a script or a git hook
Every run kept
See what it did, and answer what it asks
The Automations activity lists each automation with its trigger, where it runs, and its last run. Each run keeps every step’s result, what it changed, what left your machine, and its AI Agent use. A run that reaches an Ask me waits under Waiting on you, even if the app closes. It never goes on without your answer.
Yours, or the team’s
Local until you share it
An automation starts as yours alone. A framework editor can share one with the project, and it reaches each teammate switched off. Turn on reads it back in sentences, says where it runs and whether anything leaves your machine, and offers Try once on an existing spec or task.
Anywhere, or in the app
A change in the app, from eidos in a terminal, or by an agent fires the same triggers. When the app has the project open, a command hands the trigger to it, so a workflow runs only once. A step that needs the app, such as an AI Agent command, waits for it to open.
Ideas for this project
Not sure where to start? Ideas for this project asks the AI Agent for automations that fit your project, each with why, opened as a draft. Nothing turns on just by being suggested.
Nothing leaves without asking
An automation asks before its first run unless you say otherwise. The first time a run reaches a step that sends something off your machine, such as a push, it asks again, whatever you chose. A run’s own changes never start another automation, so nothing can set off a loop.
How it connects
Every plugin brings its triggers and its steps.
- AI Agent
Your custom slash commands become steps, and a Continue if can ask the agent a yes or no question.
- Backlog
A task added or moved starts a run, and a step can add a task or set its status.
- Git
A commit, push, or pull starts a run, and steps can commit, fetch, pull, and push.
- Comments
A step leaves a comment, and an agent step’s answer lands as a comment on the blueprint or task.
- Blueprints
A blueprint added to a collection, or saved, starts a run on that blueprint.
From the shell
Automations, from a terminal
A command that starts a run says so on stderr and leaves its own output alone. A run that asks waits for an answer from the app or the shell.
$ eidos backlog set T-X65 --status Done
✓ backlog/t-x65-watchlist-sync-across-devices.md T-X65 Watchlist sync across devices · Done [Done] medium tomas → B-W17
automations: Ship finished work (run 2) is waiting on you: Publish the commit for the team?; eidos automations answer 2 continue|stop
$ eidos automations runs 2
run 2 of Ship finished work: waiting, on Watchlist sync across devices
done Commit: 6fac987 Finish Watchlist sync across devices
waiting Ask me: Publish the commit for the team? (Publish or Not now)
pending Ask me
pending Push
$ eidos automations answer 2 continueWrite 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.