golem-debug-agent-history

name	golem-debug-agent-history
description	Querying the operation log. Use when dumping or searching the oplog, or debugging agent behavior from its recorded history.

Debugging Agent History

Both golem and golem-cli can be used — all commands below work with either binary.

The <AGENT_ID> format depends on the agent's language — refer to the language-specific invocation skills for the exact syntax.

To check agent metadata and status, load the golem-get-agent-metadata skill. To revert agent state, load the golem-undo-agent-state skill.

agent oplog — Query the Operation Log

Stream or search an agent's operation log (oplog). The oplog records every operation the agent has performed — invocations, side effects, persistence boundaries, etc.

golem agent oplog <AGENT_ID> [OPTIONS]

Flags

Flag	Description
--from <INDEX>	Start from a specific oplog entry index. Cannot be combined with --query.
--query <LUCENE_QUERY>	Search oplog entries using a Lucene query string. Cannot be combined with --from.

If neither --from nor --query is provided, the entire oplog is streamed.

Output

Each text entry is printed with its index (e.g. #00042:) followed by a labeled header and fields. In structured formats (json, yaml, toon), agent oplog emits one output document per entry with , , and ; parse stdout as a sequence of documents, not as one array or object. The entry types rendered are: