muse

picks are typed into your muse code prompt as chips, and attached when you send.

set up#

$ el install --muse

this adds element's hooks to ~/.config/muse/settings.json. restart open muse windows afterwards.

chips#

like codex, muse has no way for extensions to edit its prompt, so element types the chip in when muse runs in tmux, iTerm2, cmux, WezTerm, herdr, Zellij, GNU screen, kitty, Konsole or Ghostty on macOS (the settings kitty and Konsole need).

• only chips left in your message are sent. a chip is plain text, so delete it a character at a time.
• in other terminals every waiting pick goes with your next message.
• to turn chips off, set {"museChips": false} in ~/.element/config.json.

sessions#

each muse window is its own session, in the browser as soon as it starts.

the sandbox#

muse's sandbox blocks the el cli from reaching element. when the agent wants to run el, muse asks you to approve running it outside the sandbox.

remove#

el uninstall removes element's hooks.