Contribute

Help shape what comes next.

Design, feedback and focused code changes all help. The architecture lives in the docs. For code contributions, read the repository’s current AGENTS.md before starting; the rules below are a quick reference.

Character designer · Volunteer · Unpaid

Help give Cubby a face.

I’m looking for a graphic or character designer to help define the little creature that lives on Cinderpaw’s typing bar and reacts to the agent’s work. The current art is a placeholder.

This is unpaid. I’m funding the project myself and don’t have a design budget right now. If you need paid work, this isn’t that.

First step: agree on one character design that reads clearly at 96 × 96 pixels. Expressions and animation can follow if we both want to continue. We’ll agree on scope, credit and usage before any work starts. No free sample or full animation pack required to apply.

Share your portfolio on Discord →

Existing work is enough. Tell me what kind of character work you enjoy.

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.

Find something to work on →Poke around the code

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. The repository requires a scope check before changes spanning more than three files.

  2. 2

    Build again after you touch CinderpawAgent/

    A restart is not enough. Run `bun run build` in CinderpawAgent/ and copy the file to src-tauri/binaries/. If not you test the old code.

  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.