Get Moshi
help

Reporting a bug

A report with the setup, the versions, a side-by-side of expected and actual, and the transcript or logs usually gets fixed without a single follow-up question.

updated 1 week ago2 min readpage 42 / 42

Where to send it

Use Settings -> Support in the app. The email it opens already includes the app version, device, and OS. For connection or keyboard problems, turn on the matching log before you send. You can also write to [email protected] directly.

What to include

  1. One problem, named in the subject. "Chat View shows task progress as separate items" gets triaged faster than "bug in chat mode". Two problems, two emails.
  2. Your setup. The agent and its version, any extensions or plugins that change its output, the multiplexer (tmux, Herdr, or Zellij) and its version, and the host OS. Link the extensions if they are not well known.
  3. Versions — and a retest on the latest. The app version comes with Settings -> Support. For the host, run moshi-hook version. If you can, update and say whether it still happens on the latest release.
  4. Expected vs. actual, side by side. A screenshot of how it looks in your desktop terminal next to how it looks in Moshi says more than a paragraph. Add one sentence that names exactly what is wrong.
  5. The shortest steps that reproduce it.
  6. Something we can replay.
    • Chat View or agent problems: the agent's session transcript — the .jsonl file for that session.
    • Host, hook, or gateway problems: the output of moshi-hook doctor and the recent daemon log.
    • Connection or keyboard problems: the logs from Settings -> Support.
host
$moshi-hook version
$moshi-hook doctor
$moshi-hook logs -n 200
note

Transcripts and logs can contain code, file paths, or secrets from your session. Skim them before you attach them, or reproduce the problem in a throwaway session.

Let your coding agent collect it

Your agent already runs on the host, so it can gather most of this in one pass. Ask it something like:

Collect a Moshi bug report: run moshi-hook version and moshi-hook doctor, show the last 200 lines of moshi-hook logs, find this session's transcript file, and list the versions of the agent, its extensions, and the multiplexer.

Then attach what it found, add your screenshots, and send it from Settings -> Support.

A template

Subject: <what is wrong, in one line>

Setup: <agent + version>, <extensions>, <tmux/Herdr/Zellij + version>, <host OS>
Versions: moshi-hook <x.y.z> (still happens on <latest>: yes/no)

Expected: <what the desktop terminal shows>   [screenshot]
Actual:   <what Moshi shows>                   [screenshot]

Steps:
1. ...
2. ...

Attached: session transcript (.jsonl), moshi-hook doctor output

Before writing in, the Troubleshooting page and the debugging guides for the gateway, Chat View, and the session picker cover the common causes.