Logs
Use this skill when logs can help explain runtime behavior or distinguish software bugs from harness/tool failures.
Available log sources may include:
agent_trajectory: planner actions, environment interactions, code-tool interactions, log-tool interactions, and observations recorded by the harness.stdout_stderr: software process stdout/stderr captured by the environment launcher, when declared by the task.software_session_logs: software-owned session log files, when declared by the task.
Use the tools in this order:
- Use
log_listto inspect available log sources. - Use
log_readto read one source by name, orallwhen broader context is needed. - Use
log_analyzeto summarize anomalies, failures, suspicious state transitions, and runtime error signals.
Logs are diagnostics, not ground truth. Prefer using them to guide reproduction and evidence collection rather than reporting log text alone as a bug.