This is a community convention in Draft 00: the most valuable contribution right now is critical discussion, not code.
robots.txt and AGENTS.md solved adjacent problems, and departures from their choices should be justified, not accidental.The registry records one canonical vendor/product identifier per agent (spec §6.1).
If you represent the vendor: open a pull request adding or updating your row with status confirmed, from an account whose affiliation is verifiable (organization membership, or a link from the vendor’s official documentation to the PR). Confirming an identifier is a claim about the name — you are adopting it as the canonical token for your agent — not a claim about implementation status. When your tool does support the convention, link that documentation in the Reference column.
If you do not represent the vendor: open a pull request with status proposed, following the naming pattern of existing entries. Proposed entries are best-effort guesses that the vendor may later correct.
Identifier rules: lowercase, vendor/product, naming the agent product rather than the underlying model, stable across versions.
.editorconfig covers the rest (UTF-8, LF, final newline).By contributing, you agree that your contributions are licensed under CC BY 4.0, like the rest of this repository.