Skip to content

Align site llms.txt parser coverage with README support list #190

@luoyuctl

Description

@luoyuctl

Background

site/llms.txt is a public discovery surface for crawlers, AI assistants, and users who read the project metadata directly. Its supported-source wording now trails the README support list.

Evidence

  • README.md Supported logs lists 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.
  • site/llms.txt line 14 currently lists Claude Code, Codex CLI, Gemini CLI, Qwen Code, Aider, Cursor exports, Hermes Agent, OpenCode, OpenClaw, Kimi CLI, Pi, Oh My Pi, and Copilot-style traces.
  • The current site/llms.txt wording omits Cline and generic JSON/JSONL traces, and uses Copilot-style traces while README uses Copilot-style logs.
  • PR Add growth assets and npm launch docs #156 updates site/index.html and adds links to site/llms.txt, but it does not currently align the site/llms.txt source list itself.

User value

Users and AI assistants that use site/llms.txt should get the same parser-coverage signal as the README before deciding whether agenttrace supports their local session history.

Adoption rationale

llms.txt is a compact discovery entry point. Keeping it aligned with README-level support improves onboarding clarity without expanding product claims.

Suggested scope

  • Update site/llms.txt source coverage wording to match README-level parser coverage concisely.
  • Keep the copy local-first and focused on session history, cost/tokens/time, slow-run diagnosis, reports, and CI gates.
  • Coordinate with PR Add growth assets and npm launch docs #156 if it remains the active Growth branch, because that PR already touches site/llms.txt for navigation links.

Non-goals

Acceptance criteria

  • site/llms.txt no longer omits major currently supported sources that README lists.
  • Terminology is consistent with README for Copilot-style logs and generic JSON/JSONL traces.
  • No package/release promises are introduced.
  • scripts/ci/check-pages-artifact.sh site and release-surface/docs checks pass if touched.

Suggested lane

lane/growth

Risk

Low. Main risk is overloading a compact metadata file; keep the source list concise.

Source

Product discovery-surface audit on 2026-05-10 against origin/master README and site/llms.txt.

Metadata

Metadata

Assignees

No one assigned

    Labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions