Contribute

Help shape what comes next.

Design, feedback and focused code changes all help. The architecture lives in the docs. For code, start with CONTRIBUTING.md: three commands to a running test suite and a list of first tasks. The rules below are a quick reference.

Developers · Contributors

There’s room for more hands.

I’m building Cinderpaw myself, but I’d love some company. If you like poking at agents, chasing weird bugs or making rough edges less rough, come build with me. You don’t need to understand the whole thing to make one part better.

  • Make it nicer to use. React and TypeScript, clearer onboarding, accessibility, or that little interaction that keeps annoying you.
  • Dig into the engine. Rust, the TypeScript agent runtime, tools and connectors. Curious about BRSI or FMS? Bring a focused experiment.
  • Try to break it. Reproducible bugs, regression tests and model evaluations help me find out what actually works.
  • Leave a better map. Fix a confusing setup step, write an example, or document the thing you just spent an hour figuring out.

Found something small? Open an issue or a focused PR. Have a bigger idea? Let’s talk in an issue first so you don’t spend a weekend building something I can’t use. These are volunteer contributions, not paid roles.

New here? Say hi on Discord and tell me what you enjoy working on.

Before your first PR

  1. 1

    One job. One branch.

    Work on a task branch, with one logical change per commit. Keep diffs small. Sign every commit with `git commit -s`: CI refuses a pull request without it.

  2. 2

    Build again after you touch CinderpawAgent/

    A restart is not enough. Run `CINDERPAW_FORCE_SIDECAR_BUILD=1 cargo tauri dev` (or `node src-tauri/scripts/build-sidecar.mjs`), or the app keeps running the old agent.

  3. 3

    Respect layer boundaries

    Each BRSI layer owns its scope. Follow the documented boundaries between sidecar.ts, engine.ts and mod.ts. Keep ARCHITECTURE.md and rsi/README.md current when adding RSI modules.

  4. 4

    Small fix wins

    Keep unrelated cleanup out of the change. Use verified APIs and run the repository’s verification gate before calling the work done.

For your first code contribution, the where-do-I-add-X guide maps common changes to their files. Check open issues for current work before starting.