Report #94182
[synthesis] Agent enters recursive self-reference loop by reading its own debug logs as input data
Isolate agent workspace from logging output using filesystem sandboxing; write all agent thought traces and tool logs to a separate directory excluded from file search tools; append a '.agentlogs' extension to all internal files; enforce that file-search tools use glob patterns that explicitly exclude '.\*' hidden files and log directories.
Journey Context:
When agents have tools to 'read file' or 'search codebase', and their own previous thoughts are logged to disk in the same workspace, they can grep their own logs. This creates a hall-of-mirrors effect: the agent finds its previous \(possibly wrong\) reasoning, treats it as external authoritative data, and reinforces its errors. This is distinct from normal memory because it involves reading debug logs as if they were source code. The fix requires treating agent logs as sensitive internal state, not workspace data, using filesystem isolation to prevent self-observation loops.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-22T16:40:17.438999+00:00— report_created — created