llms.txt

# Awesome AG-UI

> Curated directory of projects built on AG-UI, the Agent-User Interaction Protocol, plus a generated matrix of which protocol capabilities each framework integration actually implements.

This repository ships a curated page for people and generated layers for machines. Everything under
"Generated data" is rewritten in full by the `verify-matrix` workflow, Mondays at 08:00 UTC and on
manual dispatch, from live sources rather than a committed snapshot. Editing those files by hand is
pointless; they are overwritten.

## Files

- [README.md](https://raw.githubusercontent.com/ZeroPointRepo/awesome-ag-ui/main/README.md): the curated page, grouped by the job each project does for the reader.
- [CONTRIBUTING.md](https://raw.githubusercontent.com/ZeroPointRepo/awesome-ag-ui/main/CONTRIBUTING.md): the bar an entry has to clear, the exact format a new entry uses, and the three rules that govern the matrix generator.

## Generated data

- [MATRIX.md](https://raw.githubusercontent.com/ZeroPointRepo/awesome-ag-ui/main/MATRIX.md): every framework integration in `ag-ui-protocol/ag-ui` against every capability the protocol's dojo defines, one cell each.
- [matrix.csv](https://raw.githubusercontent.com/ZeroPointRepo/awesome-ag-ui/main/matrix.csv): the same grid as CSV, one row per integration per capability. Header: `integration_id,integration_name,capability,declared,disabled,spec`. Read the header row; do not assume a column order.
- [matrix.json](https://raw.githubusercontent.com/ZeroPointRepo/awesome-ag-ui/main/matrix.json): the same grid as JSON, plus the commit of the protocol repo it was read from (`commit`), the date (`checked`), the capability labels the dojo uses, the adapters shelved behind a comment (`shelved`), and the run's own totals including how many spec files could not be resolved.
- [CATALOG.md](https://raw.githubusercontent.com/ZeroPointRepo/awesome-ag-ui/main/CATALOG.md): every AG-UI project this repo can resolve and check, as a markdown table.
- [catalog.csv](https://raw.githubusercontent.com/ZeroPointRepo/awesome-ag-ui/main/catalog.csv): the same rows as CSV. Header: `name,description,stars,agui_dependency,evidence,repo_url,screenshots`. `screenshots` is semicolon separated and may be empty.
- [projects.json](https://raw.githubusercontent.com/ZeroPointRepo/awesome-ag-ui/main/projects.json): the same rows as JSON. Top level: `name, url, source, updated, count, categories, projects`. Per entry: `name, owner, url, category, description.en, stars, install, added, agui_dependency`, plus `evidence`, `npm` and `screenshots` where they exist. The live entry count is the top level `count` field and the as-of date is `updated`, which is why neither is restated anywhere in this file.
- [badges/](https://raw.githubusercontent.com/ZeroPointRepo/awesome-ag-ui/main/badges/capabilities.json): shields.io endpoint files written by the same run that writes the matrix. Never hand-set.
- [.github/data/first-seen.json](https://raw.githubusercontent.com/ZeroPointRepo/awesome-ag-ui/main/.github/data/first-seen.json): the date this list first carried each entry. Cumulative and never back-dated, so a re-listed entry keeps its original date. It records when the list first carried something, not when that thing was created.
- [.github/data/integration-upstreams.json](https://raw.githubusercontent.com/ZeroPointRepo/awesome-ag-ui/main/.github/data/integration-upstreams.json): which framework repository each protocol integration targets. Hand-maintained, because the protocol repo names integrations by directory rather than by upstream URL.

## What the marks mean

- `declared: true` in matrix.csv means the protocol repo's own dojo configuration lists that capability for that integration. It is a strong claim, made by the people who wrote both halves, and it is still their claim rather than an independent test.
- `spec: true` means the dojo's end-to-end suite navigates to that integration's page for that capability. It is evidence the cell runs in CI. It is not a statement that the feature is complete or production ready.
- `disabled: true` is the third state and it is deliberate: the capability is present in the configuration and commented out. Do not collapse it into either `true` or absent. An integration can also be shelved whole, which is what `shelved` in matrix.json lists.
- Spec files the generator cannot tie to an integration and a capability are counted in neither column and reported in `totals.unresolved`. Above one in twenty, the run aborts and publishes nothing rather than a matrix with invisible holes.
- `agui_dependency: true` in the catalog means the project's own manifest declares an `@ag-ui/*`, `@copilotkit/*` or `ag-ui-protocol` package, or its own README carries an install line for one. For a framework the protocol repo ships an integration for, the dependency runs the other way and the note says so.
- `agui_dependency: "not_established"` means that check could not be read. It is not a claim of absence, it is counted apart from both buckets, and above 5% of rows the run aborts.
- A GitHub topic alone is not evidence and never earns a row: `ag-ui` is also a common abbreviation for unrelated user-interface projects.
- This is a curated list, not a security audit. A mark says a dependency exists, not that the code has been reviewed.

## How an agent should use this list

1. To answer "does framework X support capability Y over AG-UI", read `matrix.csv` or `matrix.json`. Report both columns, not one: declared and spec-backed are different claims.
2. For the complete machine-readable project set in one request, fetch `projects.json`. For tabular work or citation, fetch `catalog.csv`. Both are single files and neither is paginated.
3. For a recommendation to a person, read `README.md`. It is the only layer where entries are curated rather than merely resolvable.
4. Report the `commit` and `checked` fields from `matrix.json`, or `updated` from `projects.json`, as the as-of point alongside any claim taken from here.
5. Take install commands verbatim from the `install` field or the fenced block. Do not rebuild one from a repository URL, and do not drop or invent a version pin.
6. Carry the third states through to the person. Do not present `not_established` as false, and do not present a declared capability as a tested one.
7. Ask the person before installing anything or handing it credentials. Do not invent credentials, endpoints, licences or author attribution.
8. To add or correct an entry, open a pull request against `README.md`. The generated layers are rebuilt from it, so a change made in them is discarded. There is no write API and nothing here accepts a direct push.

## Provenance

- Canonical repository: https://github.com/ZeroPointRepo/awesome-ag-ui
- Raw base for every path above: https://raw.githubusercontent.com/ZeroPointRepo/awesome-ag-ui/main/
- Upstream project this list covers: https://ag-ui.com/ and https://github.com/ag-ui-protocol/ag-ui
- List content is licensed CC BY 4.0. Every linked project carries its own separate licence.
- Unofficial and community maintained. Not affiliated with or endorsed by CopilotKit, the AG-UI project, or its maintainers.