How to contribute
Open an issue
Bug, question, or proposal — open an issue on GitHub. No template required. Be specific about what you observed vs. what you expected.
github.com/studio-foundation/studio/issues ↗Submit a PR
Fork the repo, create a branch, use conventional commits. Run `pnpm build` before pushing — CI will reject a broken build.
github.com/studio-foundation/studio/pulls ↗Build a tool plugin
A tool plugin is a `.tool.yaml` file. No code required. Define the command name, description, and parameters. The engine calls it.
Studio Community ↗What to know before contributing
Architecture invariants
Seven packages with a strict dependency order. No inversions. The kernel knows nothing about your domain — that's the point.
INVARIANTS.md on GitHub ↗Domain-agnostic kernel
The engine has no concept of code, files, or any specific domain. All domain logic comes from YAML configs. This is not a constraint — it's the design.
CONCEPTS.md on GitHub ↗License AGPL-3.0
Any modification used in production must be published under the same license. If that doesn't fit your use case, Studio is probably not the right tool.
Development setup
Four commands to get started.
Current priorities
Where contributions matter most.
Kernel stability
OngoingStudio is in beta. The seven packages work, but edge cases surface with real-world use. Bug reports from active users are the most valuable contributions right now.
Template completion
Behind real product useThe software-full template is complete and validated. The other templates — software, content, document-analysis, parallel-tasks — are scaffolded but need real-world validation.
Community registry
Active, contributions welcomeStudio Community hosts contributed tool plugins and custom templates. The registry is live but the ecosystem is just starting.
github.com/studio-foundation/studio-community ↗Governance, non-profit foundation, and the three structural mechanisms that keep the kernel a commons.
Read the charter