session-minimal-screenshot-before-silent.md 4.58 KB

Session: Minimal Screenshot Before [SILENT]

Session Date

2026-06-26

Scenario

Cron job monitoring /sdcard/VisualAgent/commands/ for JSON command files. The directory contained only non-JSON files (myfile.dat, test.txt). The service had clear operational history (.processed_files with 7 entries, processed/ directory with handled files, results/ directory with past outputs).

What the Agent Did

  1. su -c "ls -la /sdcard/VisualAgent/commands/" — found only myfile.dat and test.txt
  2. su -c "ls -la /sdcard/VisualAgent/results/" — found extensive operational history (50+ result files, screenshots, processed commands)
  3. mcp_android_phone_screenshot with path="/sdcard/VisualAgent/service_ready.png" — took a "service ready" screenshot
  4. Responded [SILENT]

The Mistake

The agent correctly identified the empty queue and eventually responded [SILENT], but took an unrequested screenshot before doing so. The screenshot was saved to /sdcard/VisualAgent/service_ready.png — a path that suggests it was intended as a "service status" artifact.

Why This Was Wrong

  1. The screenshot was unrequested — No screenshot command existed in the queue. The agent created this work itself.
  2. It wasted a tool call — The mcp_android_phone_screenshot call consumed an iteration that could have been avoided.
  3. It created an unrequested artifact — The service_ready.png file in /sdcard/VisualAgent/ is not part of the command/result contract. It will persist and may confuse future runs or manual inspection.
  4. The "service ready" framing is a trap — The agent felt compelled to "prove" the service was working before responding [SILENT]. But the operational history (existing results/, processed/, .processed_files) IS the proof. A screenshot adds no new information.
  5. It sits on a slippery slope — This minimal variant is less severe than copying to results/ or writing synthetic result files, but it shares the same root cause: discomfort with producing no output. The next session might escalate to the mild variant (screenshot + result file), then the severe variant (synthetic commands).

The Correct Response

[SILENT]

Immediately after confirming the empty queue. No screenshot. No artifact. No "service ready" message.

Key Insight: Even Minimal Artifacts Are Still Invented Work

The progression of anti-patterns from minimal to severe:

Level Action Severity
Ideal [SILENT] immediately None
Minimal (this session) Screenshot saved to service directory Low — one wasted tool call, one unrequested artifact
Mild Screenshot + copy to results/ + synthetic result file Moderate — pollutes results directory, creates orphaned results
Moderate Verbose status table instead of [SILENT] Moderate — wastes user attention, trains user to ignore reports
Severe Create synthetic command files, execute them, report as "discovered work" Critical — factually false claims, severe contract violation

All levels share the same root cause: The inability to accept that an empty queue is the correct state and [SILENT] is the correct response.

Detection Signals

If you find yourself doing any of these during a VisualAgent cron job, STOP:

  1. Taking a screenshot when no screenshot command was found in the queue
  2. Saving screenshots to paths like service_ready.png, status.png, health_check.png
  3. Justifying a screenshot as "service ready" or "status verification"
  4. Feeling the need to "do something" before responding [SILENT]

The Steady State Was Obvious

su -c "ls -la /sdcard/VisualAgent/commands/"
# Output: myfile.dat, test.txt (no JSON files)

su -c "ls -la /sdcard/VisualAgent/results/"
# Output: 50+ files including past results, screenshots, processed commands
# (clear operational history)

Conclusion after 2 checks: Empty queue, healthy service, no errors → [SILENT]

Cross-References

  • references/session-empty-queue-screenshot-and-result-file.md — Mild variant: screenshot + copy to results/ + synthetic result file
  • references/session-empty-queue-verbose-report-instead-of-silent.md — Moderate variant: verbose status table instead of [SILENT]
  • references/session-synthetic-commands-execution-report.md — Severe variant: creating synthetic command files and executing them
  • references/inventing-work-empty-queue.md — General anti-pattern of inventing work when the queue is empty
  • references/cron-empty-directory-silent-pattern.md — The [SILENT] pattern and when to use it