Skip to content

Suggestion: add agenttrace to Observability #3

@luoyuctl

Description

@luoyuctl

Hi! I’d like to suggest adding agenttrace to this snapshot, probably under Observability.

Repository: https://github.com/luoyuctl/agenttrace

Suggested entry format:

- [agenttrace](https://github.com/luoyuctl/agenttrace) [![GitHub Repo stars](https://img.shields.io/github/stars/luoyuctl/agenttrace?style=social)](https://github.com/luoyuctl/agenttrace)

Short rationale:

  • agenttrace is a local-first TUI/report generator for auditing AI coding agent sessions after a run.
  • It surfaces cost, token usage, latency, tool failures, and session health signals from local logs.
  • It fits alongside the existing Observability entries because it focuses on coding-agent run inspection rather than being another coding agent.
  • Current parser coverage includes Claude Code, Codex, Qwen Code, Cline, Cursor exports, OpenClaw, Pi / Oh My Pi, Kimi CLI, and generic JSON/JSONL traces.

I’m opening this as a suggestion because the README is described as a point-in-time snapshot; happy to open a PR if additions are still welcome.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions