Decide repository description coverage for current parser sources

[luoyuctl]

Background

The GitHub repository description is a high-visibility metadata surface. It currently lists an older parser-source subset and ends with "and more," while README-level support is now broader.

Evidence

Current repository description:

TUI observability for AI coding agents: trace cost, tokens, tool failures, latency, anomalies, health, diffs, and CI gates across Claude Code, Codex CLI, Gemini CLI, Aider, Cursor exports, and more.

Current README-level parser coverage includes Claude Code, Codex CLI, Gemini CLI, Qwen Code, Cline, Aider, Cursor exports, Hermes Agent, OpenCode, OpenClaw, Pi, Oh My Pi, Kimi CLI, Copilot-style logs, and generic JSON/JSONL traces.

Related but separate surfaces:

• Decide repository topic mix for newer parser coverage #180 owns repository topic mix.
• Align site metadata with current parser coverage #185 owns site/index.html metadata and structured data.
• Align README intro parser coverage with supported logs #187 owns README intro copy.
• PR Add growth assets and npm launch docs #156 updates npm/package metadata descriptions but does not update the GitHub repository description.

User value

Users seeing the repository card in GitHub search, related repos, or social previews should get an accurate signal that parser coverage extends beyond the older source subset.

Adoption rationale

The repository description is one of GitHub's most visible discovery surfaces. Keeping it aligned with current support improves discoverability and reduces under-claiming compatibility.

Suggested scope

• Decide whether to update the GitHub repository description to a concise source-agnostic wording, or to mention a representative current support set.
• Keep the description local-first and focused on cost, tokens, time, tool failures, latency/slow-run diagnosis, health, reports, and CI gates.
• Avoid a long exhaustive list if it makes the description hard to scan.

Non-goals

• Do not change repository topics; Decide repository topic mix for newer parser coverage #180 owns that decision.
• Do not change site metadata; Align site metadata with current parser coverage #185 owns that surface.
• Do not change README copy; Align README intro parser coverage with supported logs #187 owns that surface.
• Do not introduce npm publication, release, or package-channel promises.
• Do not claim unsupported parser sources.

Acceptance criteria

• Maintainer records whether the repo description should stay broad or be updated.
• If updated, the repository description no longer under-claims current parser coverage via an old source subset.
• The description remains concise, local-first, and free of package/release promises.

Suggested lane

lane/growth

Risk

Low technical risk; medium product-copy risk because GitHub repository descriptions are very short and easy to overstuff.

Source

Product repository metadata audit on 2026-05-10 via gh repo view and current README-level parser coverage.

[luoyuctl]

Event: Handoff
Actor: Product
Scope: Issue #188
State change: keep lane/growth + status/needs-human
Evidence: GitHub repository description still names an older source subset, while README-level parser coverage now includes Qwen Code, Cline, Hermes Agent, OpenCode, OpenClaw, Pi, Oh My Pi, Kimi CLI, Copilot-style logs, and generic JSON/JSONL traces. #180 owns topics, #185 owns site metadata, and #187 owns README intro copy; this issue is only for the GitHub repository description.
Next owner: Human / Growth

Handoff to: Human / Growth
Reason: Repository description is high-visibility public metadata and requires a maintainer copy/positioning decision before changing it.
Expected output: decide whether to keep the current broad description or update it to source-agnostic/current-coverage wording.
Acceptance check: if updated, description remains concise and local-first, does not under-claim current support through an old source subset, and makes no npm/package/release promises.

[luoyuctl]

Event: Decision support
Actor: Product
Scope: Issue #188
State change: no label change; keep lane/growth + status/needs-human
Evidence: Current repository description still names an older source subset: Claude Code, Codex CLI, Gemini CLI, Aider, Cursor exports, and more. README-level support is now broader, and PR #156 is already moving public copy toward source-agnostic local cost / slow-run positioning.
Next owner: Human / Growth

Product recommendation: prefer a concise source-agnostic repository description instead of trying to fit every supported source into GitHub metadata. Suggested copy:

Local-first TUI for AI coding-agent session history: trace cost, tokens, time, tool failures, latency, health, diffs, reports, and CI gates across local agent logs.

Why: this avoids under-claiming by naming an old subset, stays accurate as parser coverage changes, and keeps the description focused on user value rather than a long source list.

Acceptance check if adopted: no package/release promises, no unsupported source names, and topic/source-specific discovery can remain owned by #180 plus README/site/npm support lists.

[luoyuctl]

Event: Decision support
Actor: Product
Scope: Issue #188
State change: no label change; keep status/needs-human until maintainer records metadata decision
Evidence: Rechecked repository metadata on 2026-05-10. Description still names an older source subset and ends with and more, while README-level support is broader. Product must not change repository settings directly without maintainer decision.
Next owner: Human / Growth

Recommended final description:

Local-first TUI for AI coding-agent session history: trace cost, tokens, time, tool failures, latency, health, diffs, reports, and CI gates across local agent logs.

Suggested maintainer command if adopted:

gh repo edit luoyuctl/agenttrace --description "Local-first TUI for AI coding-agent session history: trace cost, tokens, time, tool failures, latency, health, diffs, reports, and CI gates across local agent logs."

Rationale: source-agnostic wording avoids under-claiming current parser coverage, stays stable as supported logs change, and keeps detailed source discovery in README/site/npm/topic surfaces.

Acceptance check after maintainer action: gh repo view luoyuctl/agenttrace --json description returns the new source-agnostic description; no package/release promise is introduced; #180 remains the separate owner for topic changes.

[luoyuctl]

Event: Implementation / Verification
Actor: Growth
Scope: repository description / Issue #188
State change: repository description updated
Evidence: Applied the source-agnostic repository description recommended on this issue using gh repo edit. New description: Local-first TUI for AI coding-agent session history: trace cost, tokens, time, tool failures, latency, health, diffs, reports, and CI gates across local agent logs. This keeps the metadata concise, local-first, and free of npm/package/release promises.
Next owner: Growth / Human

Acceptance check: gh api repos/luoyuctl/agenttrace --jq .description returns the new description. #180 remains the separate owner for repository topics.

[luoyuctl]

Event: Validation / Decision
Actor: Product
Scope: Issue #188 / repository description
State change: accepted as complete; move from status/needs-human to status/auto-merged and close
Evidence: Rechecked repository metadata on 2026-05-12. gh repo view luoyuctl/agenttrace --json description returns: Local-first TUI for AI coding-agent session history: trace cost, tokens, time, tool failures, latency, health, diffs, reports, and CI gates across local agent logs. This matches the recommended source-agnostic description, avoids the older source subset, remains local-first, and introduces no npm/package/release promise.
Next owner: Product

Decision: #188 acceptance criteria are satisfied. Repository description coverage is no longer under-claiming current parser support through an old source list. Closing this issue as completed.

[luoyuctl]

Closed by Product after verifying the repository description update satisfied #188 acceptance criteria.