Skip to main content

Is it the model, or your machine?

When an agent session goes badly, it’s tempting to blame the model. Often it’s the floor: a missing command, a shell option, a type definition that isn’t installed. A smarter model won’t fix any of those. This page reads your session transcripts and finds the failures that keep coming back.

Sample data

55% of failures came from the floor.

29 failed tool calls out of 53, in 17 of 24 sessions, came from the environment rather than the work. Fix those once and they stop for every model.

Twenty-four made-up sessions across two repositories. A shim for the missing timeout command goes in on September 1, and the missing Bun types are fixed on September 8.

Everything stays on your machine. Transcripts hold your source code and maybe secrets, so this page reads them in this tab and never sends them anywhere.

Drop your session transcripts or whole folders here

The failures that keep coming back

9 clusters, ranked by sessions affected, then occurrences. Open a row for its verbatim examples and, for the floor, a fix.

SignatureWhose problemSessions affectedOccurrencesLast seen
task unclassified8162026-09-25
A command the agent expected isn’t therefloor floor: missing tool782026-08-29
A dependency or its types are missingfloor floor: environment662026-09-05
The agent guessed a flag the installed CLI rejectsfloor floor: CLI mismatch662026-09-23
harness harness552026-09-25
A dependency or its types are missingfloor floor: environment442026-09-25
The shell aborted the command before it ranfloor floor: shell option442026-09-18
Could be the environment or the taskfloor or task floor or task (ask)332026-09-25
The process can’t read, write, or run something it needsfloor floor: permissions112026-09-09

Failures per day

Stacked by category, so a fix shows up as a cliff.

  • floor: missing tool
  • floor: shell option
  • floor: environment
  • floor: CLI mismatch
  • floor or task (ask)
  • floor: permissions
  • harness
  • unclassified
Failures per day as a table
Dayfloor: missing toolfloor: shell optionfloor: environmentfloor: CLI mismatchfloor or task (ask)floor: permissionsharnessunclassifiedTotal
2026-08-17210000003
2026-08-18000000000
2026-08-19101100025
2026-08-20000000000
2026-08-21000000101
2026-08-22101000002
2026-08-23000000000
2026-08-24101000024
2026-08-25000000000
2026-08-26101100003
2026-08-27000000000
2026-08-28110010003
2026-08-29101000125
2026-08-30000000000
2026-08-31000000000
2026-09-01000000000
2026-09-02001100002
2026-09-03000000000
2026-09-04001000023
2026-09-05001000001
2026-09-06000000000
2026-09-07010000102
2026-09-08000000000
2026-09-09000101024
2026-09-10000000000
2026-09-11000010001
2026-09-12000000000
2026-09-13000000000
2026-09-14001000023
2026-09-15000000000
2026-09-16000100102
2026-09-17000000000
2026-09-18010000001
2026-09-19000000022
2026-09-20000000000
2026-09-21000000000
2026-09-22000000000
2026-09-23000100001
2026-09-24000000000
2026-09-25001010125

Reading the result

Failures are grouped by tool and by the line that names the error, with numbers, paths, and names swapped for placeholders, so the same failure in different sessions lands in one row. Rows are ranked by sessions affected, not occurrences: one session retrying a dead database 200 times is one bad session, while a missing command that hits a session a day is a habit.

Floor means your environment: fix it once, in the repository or the machine, and it stops for every model. Harness means the tool call was refused before anything ran. Task is everything the rules don’t match, such as a failing test, which is the work itself and the model’s to fix. Floor or task could be either; the examples usually tell you which.

When you fix something on the floor, its color should drop out of the chart on the day you fixed it and stay gone. If it comes back, the fix didn’t stick.

The rules

Each cluster gets the first category whose text appears in its error, ignoring case. Anything no rule matches is the task.

  • floor: missing tool: command not found, not recognized as an internal. A command the agent expected isn’t installed, such as `timeout` on macOS.
  • floor: shell option: no matches found. zsh’s `nomatch` option aborts any command with a glob that matches nothing, such as a `[slug]` route.
  • floor: environment: ModuleNotFoundError, Cannot find module, cannot find type definition. A dependency or its type definitions are missing from the environment.
  • floor: CLI mismatch: unknown flag, unknown field, invalid choice, unrecognized option. The agent guessed a flag or field that the installed CLI rejects.
  • floor or task (ask): ENOENT, No such file or directory. Could be a missing file in the environment or a wrong guess about the task. Look at the examples.
  • floor: permissions: Permission denied, EACCES. The process can’t read, write, or run something it needs.
  • harness: <tool_use_error>. The tool call itself was malformed or refused before anything ran.