Status and support

How mature Kraft is, what its version numbers promise, where it runs, and where to get help.

Maturity

Kraft is young, and it changes quickly. Expect rough edges, and read the release notes before you upgrade.

Kraft follows semantic versioning. These are its public interfaces:

the kraft command line: its verbs, flags and --json output;
the HTTP endpoints meant for other programs: POST /api/triggers and GET /api/health;
the YAML config schema under $KRAFT_HOME/templates;
the MCP tools.

Every other HTTP route exists for the board and can change in any release.

Release	May change
Major (`2.0.0`)	Anything, including a breaking change to the CLI, the API, the config schema or the state on disk. The release notes say what breaks and how to move.
Minor (`1.2.0`)	New capabilities that do not break an existing one.
Patch (`1.1.1`)	Fixes to something that already shipped.

Only the latest release gets fixes, security fixes included. Kraft has no long-term support branch. kraft admin update installs the latest release.

macOS and Linux. Windows is not supported, and WSL is untested.
Python 3.12, 3.13 and 3.14. CI runs the tests on each. uv installs one for you if the machine has none.
Docker or Podman, only if you use the optional sandbox.

Ask questions and report bugs in GitHub issues. Report a security problem privately instead; see SECURITY.md.

Data and privacy

What leaves your machine, where it goes, how to turn it off, and where Kraft keeps secrets and state.