Open source

Build the control room with us.

o8 is MIT licensed, and the contribution path is public. Start with a focused issue, make one change easy to review, and include the proof that it works.

Where to start

Pick an open help-wanted issue or file a new issue before beginning non-trivial work. That short conversation prevents two people from solving the same problem and keeps the proposed change aligned with the product’s local-first and approval-first contracts.

Contributions that fit well

  • Small bug fixes with a clear reproduction and regression test.
  • Performance and reliability improvements with before-and-after evidence.
  • New agent runtime adapters that follow the shared adapter contract.
  • Focused tests for review, merge, memory, and local-control behavior.
  • Documentation and site fixes that match behavior available in a current release.

Make the pull request easy to trust

Keep each pull request to one concern. Explain the user-visible behavior, call out risk or migration work, and include the relevant checks. The repository’s full contribution guide covers setup, TypeScript, tests, linting, and Rust verification.

  • TypeScript changes: run the typecheck, tests, and targeted lint checks.
  • Rust changes: run the relevant Cargo checks and tests.
  • Interface changes: include a real screenshot or recording and verify reduced-motion behavior.
  • Product claims: point to the current code path and a release where users can reach it.

Add an agent runtime

Runtime adapters let o8 govern more coding tools without changing the review and approval model. Start with the adapter contract and open an issue with the runtime’s launch, streaming, cancellation, and authentication behavior before writing the integration.

Join the project