Community
Where the Appstrate community lives, how to ask for help, and how to follow the project.
Appstrate is open-source (Apache 2.0) and the community is public. Everyone who contributes, reports bugs, or builds on top of the runtime is welcome.
Chat
Discord is the primary real-time channel:
Channels cover setup help, self-hosting, AFPS and skill authoring, model and provider support, and general discussion. The maintainers and a growing group of contributors hang out there.
GitHub
Code, issues, discussions, and releases all live on GitHub.
| What | Where |
|---|---|
| Main monorepo | github.com/appstrate/appstrate |
| Issue tracker | github.com/appstrate/appstrate/issues |
| Releases and changelog | github.com/appstrate/appstrate/releases |
| AFPS spec repository | github.com/appstrate/afps-spec |
| All Appstrate projects | github.com/appstrate |
Star the repo if you find it useful. It's the most lightweight way to signal support.
When to use what
- Bug report, crash, regression: open a GitHub issue with steps to reproduce, expected vs. actual behavior, and your environment (Tier, OS, Docker version).
- Feature request: open a GitHub issue labeled
enhancement. Explain the use case before the proposed solution. - Security issue: do not open a public issue. Email
[email protected]. See SECURITY.md in the repo. - Setup help, general question: Discord. Real-time answers, lower friction than an issue.
- AFPS spec proposal: open a discussion or issue in the AFPS spec repo. The spec is governed separately from the runtime.
Contributing
Contributions are welcome: bug fixes, docs, providers, skills, tools, agents, feature work. Start with Contributing for the PR workflow and conventions.
Code of conduct
The project follows the Contributor Covenant. Be kind, be technical, assume good faith. Maintainers enforce this across all channels.