A curated index of notable community forks of dotagent. Being listed here is a quality signal — the maintainer reviews and chooses what gets listed. This is not a directory of everything that exists; it is a list of forks worth pointing people to.
A community fork must meet the following minimum standard:
- Contains a valid
manifest.yamlwithstackandmaintained-bydeclared - Follows the trace-based command format — traces are real runs, not invented
- Declares
dotagent-compatible: truein the manifest - Atomic examples carry
stack: agnosticin frontmatter to signal reusability
To propose a listing, open an issue with a link to your fork and a one-line description of the stack it targets.
No entries yet. The ecosystem grows from real usage.
Community workspaces live in forks, not branches. A fork means you own it — your repo, your name, your issue tracker, your release cycle. You get full credit and full control. The main repo stays clean.
Community forks can pull updates from the base dotagent repo as the standard evolves. They diverge where their stack demands it.
dotagent is the reference implementation and standard. Community forks are applications of that standard.