Muesli Agent

Muesli Agent

Use the local muesli-cli CLI as the source of truth for meeting and dictation data.

CLI discovery

Resolve the binary in this order:

1. command -v muesli-cli
2. command -v muesli only when the resolved path is a Homebrew cask alias to Muesli.app/Contents/MacOS/muesli-cli; verify with muesli info
3. /Applications/Muesli.app/Contents/MacOS/muesli-cli
4. A local SwiftPM build path inside this repo

If discovery is uncertain, run the candidate binary with info first and reject unrelated muesli executables.

Core workflow

1. Inspect capabilities with muesli-cli spec if you do not know the exact subcommand shape.
2. To transcribe a local audio file, run muesli-cli transcribe <file> and read plain transcript text from stdout.
3. Use muesli-cli transcribe <file> --format json when you need duration, word count, model, warnings, summary, or saved meeting ID.
4. Add --save-meeting to persist an imported meeting with source = audio_import.
5. List candidate meetings with muesli-cli meetings list --limit 10.
6. Fetch a full record with muesli-cli meetings get <id>.
7. Use the coding agent's own model to analyze rawTranscript and formattedNotes.
8. If you want to persist improved notes, write markdown back with:
   • cat notes.md | muesli-cli meetings update-notes <id> --stdin
   • or muesli-cli meetings update-notes <id> --file notes.md

Rules

• Treat CLI stdout as the API. Data commands are JSON by default; transcribe is plain text by default, Markdown with --format markdown, and JSON with --format json.
• Treat stderr as informational only.
• Do not mutate rawTranscript; only update formattedNotes.
• Prefer the meeting transcript when notesState is missing or raw_transcript_fallback.
• Use --db-path or --support-dir only when the default Muesli data location is wrong.

When to read references

Read references/cli-contract.md if you need the exact command tree, field definitions, or failure behavior.