Reference
Look-up pages for the web UI, the CLI, configuration files, chain nodes, permissions, harnesses, triggers, the HTTP API, MCP tools, environment variables, and events.
Look up a command, field, endpoint, tool, status or event.
In this section
Use Kraft
- Web UI: when you want a screen explained: the sidebar, search and keyboard shortcuts, the board, an item's page, the review page, Templates and Settings, and Analytics.
- CLI: when you want the verb for a task, or a verb's flags and output.
- Work item statuses: when you want to know what a status means and what moves an item to the next.
Configure Kraft
- Configuration: when you edit a YAML file and want its fields, defaults and limits.
- Environment variables: when you want a
KRAFT_*variable, or a variable Kraft passes to workers. It sits last inside Configuration in the sidebar. - Chain file keys: when you write a chain and want the node kinds, the subprocess task and fix loop contracts, and the result file.
- Agent harnesses: when you want the agent CLIs Kraft runs and what each supports.
- Permission gate: when you want to know how Kraft answers a worker's asks, and the grants.
Drive Kraft from a program
- Inbound triggers: when you start a chain from a cron schedule or an HTTP call.
- HTTP API: when you call Kraft over HTTP and want the stable routes, the board's routes and the draft ops, the schema, and who may call.
- MCP tools: when you wire an agent to Kraft and want every tool and its
kraftcommand. - Events: when you read a work item's timeline, stream events over the WebSocket, or send events to a webhook.
Sandbox and Kit stops
Find the reason a sandboxed work item stopped, whether a sandbox with no network policy, the sandbox's memory limit, a Kit Kraft will not run, a workspace member Kraft cannot check out, or a nested git repository Kraft did not create, and the fix for each.
Overview
Every screen of Kraft's web UI, from the board and an item's page to the review page, Templates and Settings.