Repository navigation
v0.8.0 — Muse Code as a sixth client
Muse Code joins Claude Code, Grok, Codex, Copilot CLI, and Antigravity: capture and recall, set up with rutter-memory install-hook --client muse.
Install
Claude Code:
/plugin marketplace add shinytoyrobots/rutter
/plugin install rutter@rutter
Choose your notes folder when asked, then run /reload-plugins. Already installed? Run /plugin marketplace update rutter, update the plugin, and restart Claude Code. Requires Node 22 or newer.
Other clients: npm install -g rutter-memory, then follow your client's path in Getting started. Grok uses the Claude Code plugin. Muse Code has its own setup path.
What changed
- Muse Code is a sixth client.
rutter-memory install-hook --client museadds capture for Meta's
terminal agent (muse). It adds the Stop hook and an optionalrutterserver entry to
~/.config/muse/settings.json, and a marked block to~/.config/muse/AGENTS.md. The block is
required: in testing, Muse's model wrote summary lines only with it in place. Muse runs hooks with a
cleared environment, so the notes folder and an absolutenodeare baked into the hook; pass
--vaultto choose the folder. The installer keeps your other settings, hooks and servers, refuses a
symlinked or unparseable file, never changes text outside its own block, and recordsclient: muse.
Verified with Muse Code 1.4.10. In an untrusted workspace that has its ownAGENTS.md, the rule loaded
in only 1 of 4 trial runs. Setup is in
Getting started. - The Stop hook now bounds its capture process, for every client.
hooks/librarian-stop.shruns the
capture under a small supervisor that stops it after 20 seconds (LIBRARIAN_CAPTURE_TIMEOUT_SEC
changes that) and always exits cleanly with nothing on stdout. Muse holds a turn for as long as a
hook runs. The cost is one extra Node process per capture.