### Currently, agent logs are written to the repo + streamed. 1. It would be simple to parse the logs and create a summary of - input/cache/output tokens used - Other interesting details of note 2. Requires a new logging module - Claude output varies by session - Codex logs are consistent + also duplicated in `~/.codex` (but we respectfully don't want to mess with files outside a repo) - [_agy_](https://antigravity.google/docs/hooks) and [_Copilot_](https://docs.github.com/en/copilot/concepts/agents/copilot-cli/chronicle#how-session-data-is-stored) logs need to be inspected for shape - `harness status` is already wired as a command to get the link to the latest log - Account for installed `jq`, or other tool usage, for pretty print + [Rich/Typer ](https://rich.readthedocs.io/en/latest/logging.html) is already in the harness
Currently, agent logs are written to the repo + streamed.
~/.codex(but we respectfully don't want to mess with files outside a repo)harness statusis already wired as a command to get the link to the latest logjq, or other tool usage, for pretty print + Rich/Typer is already in the harness