Skip to main content
This is the day-to-day loop. Something crashed — maybe once on your machine, maybe fifty times across CI runs. Here’s how to go from “something is wrong” to a fix, entirely in the terminal.

​
1. Triage: slomo issues

One row per bug, not per crash — fingerprinting already collapsed the duplicates. Filter when the list grows:
Count, category, and stability tell you where to spend attention: a recurring Null Reference with 50 occurrences beats a one-time Unknown.

​
2. Understand: slomo issue show

Full detail for the issue: title, category with confidence, severity, stability, first/last seen, affected sessions, a sample traceback, and possibly-related issues. For the incident-by-incident view:

​
3. Diagnose: slomo doctor

The doctor walks the recorded timeline backwards from the crash and applies heuristics to name:
  • the first bad function — where the failing value entered the picture
  • the first bad variable — the value that was already wrong at the crash site
  • the context — the SQL/HTTP/log events immediately preceding the crash (above: the query returned 0 rows, which is why inventory was None)
For a one-paragraph version — useful for pasting into a ticket — use slomo issue explain SM-8b6f710a.

​
4. Dig deeper when the doctor isn’t enough

Replay

slomo replay SM-8b6f710a — step through the recorded execution event by event.

Timeline

slomo issue timeline SM-8b6f710a — the latest incident’s session, focused on its trace.

Typed views

slomo vars, slomo sql, slomo http scoped to the issue.

Search

slomo search timeout module=checkout across all sessions.

​
5. Fix, verify, resolve

Make the fix, run the app again, confirm the issue’s count stopped growing, then:
Resolution is honest by design: if the same fingerprint ever appears again, the issue auto-reopens. You don’t need to remember to check — a resurfaced bug puts itself back on the list. (slomo issue reopen exists for manual reopening.)

​
Sharing a diagnosis

Hand a teammate the whole story without them installing anything:
See Exporting.