Contributing

You will have a tested change on a branch, ready to open as a pull request. The contributor guide lives in the repository so it stays next to the code it describes: CONTRIBUTING.md.

Before you start

• just.
• uv. Its first uv sync downloads a supported Python if you have none.
• git.
• Node 22 with npm.

Contribute a change

1. Install the dependencies:

   just setup
   

2. Run a dev instance. It keeps its state in .dev/ and fakes the agents, so it never spends tokens and never touches ~/.kraft:

   just dev
   

   
   Open the Local URL it prints: http://localhost:5173, unless that port is taken.
3. Test your change and lint it:

   just test
   just lint
   

4. Open a pull request. Give it exactly one release:: label, and write its user-facing line in the ## Changelog section of its description. Do not edit CHANGELOG.md.

just test runs only the backend tests your changes affect. Do not call pytest directly. When you change behavior, update the docs page that covers it: CONTRIBUTING.md has the table that says which. To find the module to change, see the Source map. Maintainers cut releases as described in RELEASING.md.

Next steps

• Source map: which module under src/kraft/ holds what, and where to change a given thing.
• Architecture: how the parts fit together before you change one.