The adapter registry
Community adapters are shared as git repos: publish your tally-adapter-<name> directory anywhere clonable, and anyone installs it with tally adapter install <git-url>. The community registry is the index over those repos; it is searchable via tally adapter search and launches with the beta. Writing an adapter is covered in Building adapters; the manifest schema is in the adapter.toml reference.
The registry format
Section titled “The registry format”{ "v": 1, "adapters": [ { "name": "aider", "harness": "aider", "git": "https://example.org/alice/tally-adapter-aider", "author": "alice", "pac_conformance": "validate-pass" }, { "name": "goose-lite", "harness": "goose", "git": "https://example.org/bob/tally-adapter-goose-lite", "author": "bob", "pac_conformance": "" } ]}Fields
Section titled “Fields”| Field | Meaning |
|---|---|
v |
Registry schema version (currently 1). |
adapters[] |
The list of registry entries. |
adapters[].name |
The adapter’s name ([a-z0-9-]+, matching the manifest’s [adapter].name). This is the name you pass to the session verbs after installing. |
adapters[].harness |
The harness the adapter targets. |
adapters[].git |
The git clone URL of the adapter repo; pass it to tally adapter install. |
adapters[].author |
Who published it. |
adapters[].pac_conformance |
The PAC conformance state: "validate-pass" when the adapter passes the tally adapter validate round-trip smoke; empty when no conformance result is recorded. |
Searching and installing
Section titled “Searching and installing”tally adapter search <TERM> matches the term as a substring against name, harness, and author:
tally adapter search aiderInstall from the entry’s git URL (or a local path):
tally adapter install https://example.org/alice/tally-adapter-aiderThe manifest is parsed and validated before anything is written, and install refuses manifests containing shell-exec patterns unless you pass --allow-shell after reviewing the manifest (the pattern list is in the adapter.toml reference). Installed adapters land under <tally_home>/adapters/; tally adapter list shows built-ins (verified) alongside installed community manifests, and tally adapter remove <name> uninstalls a community adapter (built-ins refuse).
See also
Section titled “See also”- Building adapters: the create → validate → install → publish workflow
- adapter.toml reference: the manifest schema
- The PAC specification: the contract every adapter implements