Community
Where to ask for help, report bugs, and follow Appstrate.
Appstrate is open source (Apache 2.0, apart from the source-available packages/module-ee) and its community is public. Anyone who reports a bug, asks a question, improves the docs, or builds on the platform is welcome.
Chat
Discord is the place for questions and real-time help: discord.gg/5Js2CKWNnh. Ask about setup and self-hosting, agents and skills, or what you are building.
GitHub
Code, issues, and releases are on GitHub.
| What | Where |
|---|---|
| Main repository | github.com/appstrate/appstrate |
| Issues (bugs and feature requests) | github.com/appstrate/appstrate/issues |
| Releases | github.com/appstrate/appstrate/releases |
| Changelog | CHANGELOG.md, see Changelog |
| AFPS specification | github.com/appstrate/afps-spec |
| All Appstrate projects | github.com/appstrate |
Starring the repository is the lightest way to show support.
When to use what
- Bug, crash, regression: open an issue with the bug report template. Include steps to reproduce, what you expected, what happened, and your environment (OS, Bun and Docker versions).
- Feature request: open an issue with the feature request template. Describe the problem before the solution.
- Large or breaking change: propose it first, following the RFC process in GOVERNANCE.md.
- Security vulnerability: do not open a public issue. Use GitHub private vulnerability reporting or email
security@appstrate.dev. See SECURITY.md. - Setup help or a general question: Discord.
- A change to the AFPS format: open an issue on the AFPS spec repository. The spec is governed separately from the runtime.
- Anything else:
hello@appstrate.dev.
Contributing
Bug fixes, documentation, translations, integrations, skills, agents, and features are all welcome. Contributing covers the workflow and conventions.
Code of conduct
The project follows the Contributor Covenant. Be kind and technical, and assume good faith.