Aider

Make Aider follow an instruction: instruction.md keeps a file current, and Aider reads it again with every message you send. The same setup for other tools, and how each one takes a new version, is on Other coding agents.

At a glance

How it followsa file it reads again
A new version arriveswith every message
Set upwatch, and a setting
Checked againstAider, against its source
SystemsAny; the commands below are for a POSIX shell

What you need: Node.js 20.19 or later, the instruction.md package (npm i -g instruction.md, 0.11.0 or later) and @instruction.md/agents 0.4.1 or later, which instruction agents … runs. Every instruction agents … command also runs, without installing anything, as npx -y @instruction.md/agents …, and every instruction … command as npx -y instruction.md ….

Set up

Aider reads its read-only files again with every message. instruction connect --host aider <uri> prints the command that keeps the file current and the setting:

Shell and .aider.conf.yml
# Aider re-reads its read-only files with every message: instruction.md keeps .instruction/current.md current
npx -y instruction.md watch instruction://acme/support-agent@stable --out .instruction/current.md --url https://instruction.md/mcp &
# .aider.conf.yml (Aider takes no MCP server)
read: [.instruction/current.md]
# sign the watcher in once: npx -y instruction.md login

What happens

With each message you send, Aider reads .instruction/current.md again. A new version reaches the next message after watch writes it.

Caveats and what isn't verified

Check it worked

Read the instruction once, as watch does, and write it:

Shell
instruction watch instruction://acme/support-agent@stable --out .instruction/current.md --once

It prints applied v… and the file it wrote, and exits 0; 6 means nothing could be applied. Then start the tool and ask which instructions it follows.

Stop following

  • Stop instruction watch (Ctrl-C, or the service you made for it).
  • Remove .instruction/current.md from read: in .aider.conf.yml.
  • Delete .instruction/current.md.

If it doesn't work

What you seeWhyWhat to do
A new version doesn't reach the toolinstruction watch isn't running, so the file keeps the version it last wroteStart it again, or run it as a service (Keep watch running)
live updates are taken: … Still reading on schedule.Another agent or app has your plan's live updatesNothing breaks: watch reads every 60 seconds (Plans and live updates)
A private instruction isn't readThe command isn't signed ininstruction login (--device on a machine without a browser)
Still stuckAsk us

Last checked against the product:

Was this page helpful? Report a problem