Built by people who
use it every day.
tok0 is open-source under MIT. The fastest path to an answer is the appropriate channel below — issue tracker for bugs, Discord for quick questions, email for anything sensitive.
Issues & discussions
Bug reports, feature requests, and open-ended design conversations. Read-only required for browse, GitHub account required to post.
Real-time chat
The fastest way to ask a small question. Maintainers and core contributors hang out here. English-primary, all timezones welcome.
Release announcements
Low-volume. New versions, breaking changes, and the occasional benchmark thread. Mute words exist for a reason.
Security & private
Vulnerability disclosures, partnership requests, anything that should not be public. PGP key on the SECURITY.md page.
Four ways to land
your first PR.
Every contribution path has a documented recipe. None of them require knowing the engine internals — that's deliberate.
Ship a TOML rule
The most-needed contribution. Pick a verbose CLI you use, capture a fixture, write 10 lines of TOML, open a PR. Most rules merge same-day.
Add an AI tool integration
Used a tool tok0 doesn't support? The bridge layer is ~50 LOC per integration and follows a strict template — you don't need to know the engine internals.
Build an extension
Bundle company- or community-specific rules into a git repo and let anyone install them with one command. Solves the long-tail without growing the binary.
Fix a bug or improve docs
Issues tagged good-first-issue are vetted to be approachable. Doc improvements are always in scope — every page has an edit-on-GitHub link.
Contributor
Covenant.
The project follows the Contributor Covenant v2.1. Reports go to conduct@prxm-labs.dev. Responses within 72 hours.
Be kind, be specific, assume good faith, and remember the person on the other side of the screen is volunteering their time. That's the whole policy.