Skip to content
#

Muse Code

Save Muse Code sessions with the SpecStory CLI.

#

Before you start

Install Muse Code and the SpecStory CLI. Muse needs SpecStory CLI 2.10.0 or later, and sessions created with Muse Code 0.1.0-R708.1 or later. Open your project folder in a terminal and run specstory check muse.

#

Run with SpecStory

specstory run muse

Use Muse as usual. SpecStory saves the conversation in .specstory/history/. Cloud sync can run when you are logged in; add --no-cloud-sync to keep the session local.

#

Export existing sessions

specstory list muse
specstory sync muse

# Export a single session
specstory sync muse -s <session-id>

SpecStory reads Muse's session history from ~/.local/share/muse/sessions/ and matches it to your project. You can export conversations even if you did not start them through SpecStory. Muse keeps every session in one place, grouped by date, so the match uses the workspace recorded inside each session: run these commands from the project you worked in.

A subagent's work stays inside its parent conversation instead of becoming its own session, and Muse's encrypted reasoning cannot be exported as readable text.

If you set XDG_DATA_HOME, Muse stores sessions under $XDG_DATA_HOME/muse/sessions/ instead. Set the same variable for SpecStory so it reads the same place.

#

Capture in the background

specstory watch muse

Leave this running while using Muse directly. Stop watching with Ctrl+C.

#

Find and resume a session

Run specstory search to find saved work or specstory resume to choose a previous session. Muse continues one of its own sessions in place with muse resume, and can receive a session from another agent as reconstructed conversation text. See search and resume for the picker and supported handoffs.

#

Troubleshooting

If Muse is not detected, check that muse is on your PATH. If your CLI does not list Muse in specstory run --help, update SpecStory. To launch Muse from another location, set muse_cmd in your config or pass specstory run muse -c "/absolute/path/to/muse"; use an absolute path, because Muse's command setting does not expand a quoted ~. If no sessions appear, run the commands from the project where you used Muse and confirm that its local history still exists.

See the CLI reference for custom commands, configuration, and debug logging.