golem-debug-agent-history

You can debug unexpected golem agent behavior by dumping or searching the agent's operation log. This allows you to inspect recorded history, locate relevant events, and pinpoint the sequence that led to faulty actions.

You can search a golem agent's oplog by running golem agent oplog <AGENT_ID> --query "error" with a Lucene query string. This filters the operation log to locate specific errors, invocations, and side effects.

The golem agent oplog records structured entries for creation, calls, invocations, persistence, snapshot events, plugin lifecycle, and errors. These categorized entries provide actionable debugging context for agent behavior.

Yes, you can retrieve the entire operation log for a golem agent by dumping the full oplog. This outputs all recorded history without applying a starting index or Lucene query filter.

No, you cannot use both a starting index and a Lucene query simultaneously. The golem oplog search enforces mutual exclusivity between the from index parameter and the query string.

Yes, the golem oplog debugging skill supports querying operation logs across both golem and golem-cli. It renders categorized oplog entry types with relevant fields for investigation.