Factory Droid

Make a project follow an instruction in Factory Droid: one command writes its hooks, and a new version arrives at your next prompt. The same setup for other tools, and how each one takes a new version, is on Other coding agents.

At a glance

How it followshooks
A new version arrivesat your next prompt
Set upone command
Checked againstFactory Droid 1.14.0, from its documentation
SystemsWherever the tool and Node.js 20.19 or later run

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

In your project's folder, signed in (instruction login), run:

Shell
instruction agents follow instruction://acme/support-agent@stable --host droid --write

It writes, merged into what is already there:

  • .instruction/follow.json: the instruction the project follows. Commit it.
  • .instruction/.gitignore: keeps the fetched copy (current.md), state.json and given/ out of git.
  • .factory/hooks.json: the hooks. Commit it.
.factory/hooks.json
{
  "SessionStart": [
    {
      "matcher": "startup|resume|clear|compact",
      "hooks": [
        {
          "type": "command",
          "command": "npx -y @instruction.md/agents hook droid",
          "timeout": 10
        }
      ]
    }
  ],
  "UserPromptSubmit": [
    {
      "hooks": [
        {
          "type": "command",
          "command": "npx -y @instruction.md/agents hook droid",
          "timeout": 5
        }
      ]
    }
  ]
}

Droid runs a project's hooks in a trusted folder; commit .factory/hooks.json for everyone working here.

What happens

Droid runs hooks the way Claude Code does: the instruction's whole text when a session starts, and a new version at your next prompt.

The MCP server

Droid reaches instruction.md through the instruction command's stdio server. instruction connect --host droid <uri> prints:

.factory/mcp.json
// .factory/mcp.json (or: droid mcp add) — Factory Droid reaches instruction.md through this CLI's stdio server
{
  "mcpServers": {
    "instruction-md": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "-y",
        "instruction.md",
        "mcp",
        "--follow",
        "instruction://acme/support-agent@stable",
        "--url",
        "https://instruction.md/mcp"
      ]
    }
  }
}
// sign the bridge in once: npx -y instruction.md login
// to give every session this instruction, and a new version at the next prompt: npx -y @instruction.md/agents connect --host droid instruction://acme/support-agent@stable --with-hooks --write
// (Droid also loads the instruction.md plugin: its hooks do the same)

The plugin instead

Droid also loads instruction.md's plugin, instruction-md/ at github.com/instruction-md/plugins, through its Claude Code manifest. Its hooks run npx -y @instruction.md/agents hook auto, which answers as Droid. Use the plugin or the project's hooks, not both.

Caveats and what isn't verified

  • The answer's shape comes from Droid's documentation; it is the shape Claude Code takes.

Check it worked

Run the hook by hand, as the tool would at that event. It prints what the tool receives: the instruction's whole text the first time, and nothing when you run it again right away, because a session gets each version once.

Shell
echo '{}' | npx -y @instruction.md/agents hook droid --event SessionStart --dir .

Then start a new session and ask which instructions it follows. Once a session has read it, .instruction/current.md holds the copy the hooks keep, and the instruction's Agents card counts the follower under this tool.

Stop following

  • Remove the entries that run @instruction.md/agents hook droid from .factory/hooks.json.
  • Delete .instruction/follow.json, or the whole .instruction/ folder.

If it doesn't work

What you seeWhyWhat to do
Running the hook by hand prints nothingNo .instruction/follow.json in the folder or above it, up to the repository's root; or it gave this version moments agoRun the setup in the project's folder, or pass --dir. A version the session already has isn't given again: nothing is wrong
instruction.md: couldn't read …; this session goes on without itOffline, not signed in, or the address is wrong, and there is no copy yetinstruction login, then check the address in .instruction/follow.json
instruction.md: a newer version of … is held (…)The new version's signature doesn't check out, and the follow file asks for oneNothing to do on this machine: the session keeps the version it has. See How following works
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