Muse
The support matrix is the main reference for what Farhelm does with Muse. This page only adds what is specific to Muse.
Restarting a conversation
Section titled “Restarting a conversation”With Muse 1.4.14 or later, Restart becomes available after you submit your first prompt. Farhelm adds hooks for that
launch without installing a Muse plugin or changing Muse’s saved configuration. They also let Muse learn how to handle
your $farhelm requests; see Agent hook injection.
Muse reports its conversation again at the end of a turn. After /clear or /new, it reports the new conversation at
your next prompt, so restarting before then can bring back the previous conversation. Restart keeps your launch’s
permission choices and resumes the last conversation Muse reported.
Muse works through wrappers that stay running. A custom command must declare Muse and
pass {farhelm_args} to it; its resume command can use muse resume {conversation} {farhelm_args} with the same
permission flags as its start command.
Muse sessions created before this support was added keep their old launch. They gain the hooks at their next start, but have no resume command for Restart to use; recreate them through Clone or Replace with. If a new session never becomes restartable after a prompt, see When something goes wrong.
Status
Section titled “Status”Farhelm reads Muse’s working indicator and idle prompt to show whether the session is running or idle. It shows waiting for Muse’s directory-trust question. Questions and approval dialogs during a conversation have not been verified, so they may look idle while Muse waits for you.
Gotchas and quirks
Section titled “Gotchas and quirks”- Guarded selects Muse’s auto-review profile with
--permission-profile :auto-review, overriding an unrestricted default. Your approval rules, sandbox settings and later mode switches still matter; see Permission modes. Farhelm also tries to notice YOLO on Muse’s status line and show a YOLO shield; this is best effort, not a check of your approval or sandbox settings. - Muse’s switch in agent trust settings can skip its directory-trust question for directories Farhelm manages, on every host. It is off by default. Farhelm passes a trust argument for each new launch without changing Muse’s saved configuration; trusting the directory allows the repository’s own hooks, settings and commands to run as if you had approved them. While the switch is off and Muse asks this in a managed checkout, a note above the session’s terminal says Farhelm can answer it, and its Settings opens Agent trust at Muse’s switch. Sessions started from the Command tab show no note.
- YOLO also makes Muse trust the session’s directory. Turning the setting off cannot take back trust granted by YOLO or Muse’s own configuration. Directories outside managed checkouts keep Muse’s own trust behavior.
For what survives closing Farhelm or rebooting a host, see What survives what.