Web UI

Settings

Each Settings screen that sets up Kraft itself, with the file it edits and whether a change saves at once, waits for a draft to be published or needs a restart.

Settings holds the screens that set up Kraft itself: the repos it works on, the agent CLIs it drives, its limits and how you reach it. Each page with something to save says in its header whether a change sticks.

ScreenThe file it editsA change
Reposrepos.yamlDraft: Review & publish
Forge accounts Added in 2.5forges.yamlEach action saves as you take it
Harnessesharnesses.yamlDraft
Policypolicy.yamlDraft
Auto-intakeintake.yamlDraft
Notificationsnotify.yaml; This browser is kept in the browserSaved on change
Accessaccess.yamlSaved on change; Restart to apply only while an edit waits for a restart
Appearancetheme.yamlSaved on change
Board & codetheme.yamlSaved on change
Workersworkers.yamlEach action saves as you take it
StorageNone: it reads the run folder; the limit and quota are in policy.yamlNo settings
AboutNoneSwitches and hours save on change

A draft screen shows a draft chip instead of a saved word. Esc leaves Review & publish, then the YAML view.

Repos

Repos lists the connected repos with each one's chain, whether it can run work, its test command and state. Select a repo to change its fields. See repos.yaml.

You seeIt means
No setupNo setup command is declared, so the first work item stops there
No tests setTests are unset, so the first work item stops there
ReadyBoth are set. Kraft keeps no verify result per repo

Connect repo on a repo already connected offers Update, which saves only what the entry left undecided, as kraft repo connect does. A repo with no commit yet can't connect: Check again reads it once you have committed.

A repo's fields

A selected repo's Config tab groups its fields under Running, Tests, Agents, Limits and Forge. Fields still at their default fold into N defaults · show; one you set, changed or that has a problem stays in view. Edited in YAML lists the keys with no field here (env, sandbox, ci_checks, library_auto_update, automated_review, post_merge_publish_jobs) and links to the repo's YAML tab.

SwitchWhat it says
No setup needed, beside setup commandA fresh checkout needs nothing installed (setup_command: "")
No tests, beside test commandThe repo has no tests (test_command: ""): its items pass verify without running any. Turning it off leaves the command unset, which stops each item at verify

The phone's Repos has the same two switches.

Forge accounts

Added in 2.5

Forge accounts lists each account in forges.yaml: Name, State, Forge with its web address, Token, Checked and Used by (the repos that name it). For a cli account Token shows gh's or glab's own sign-in. For an API account State says who the token signs in as, when it expires, whether single sign-on is needed and which repos it can't see. With no accounts, Kraft uses gh and glab as they are signed in. See forges.yaml.

ControlWhat it does
Add accountcli keeps the sign-in of gh or glab. api adds a CA file and Token from: git credential, variable, file or paste. A pasted token is kept in a file under secrets/ and never shown again
EditChanges everything but the name, forge and web address (remove the account and add it again for those). A variable is read at server start, so a new value needs a restart
Replace tokenOnly on an account that is already api
TestChecks the token; reads Testing… while it runs
Remove accountRefused while a repo names the account. Otherwise it goes after a five-second undo

An account whose token comes from a command shows no command text, since it can hold a token. Its Client is locked and the server refuses a browser change to its token or client (403): use kraft admin forge edit on the server's machine. A phone can Test, Paste a new token and Remove; add an account on a wider screen.

Harnesses

Harnesses lists the agent CLIs Kraft can drive, whether each is installed and who may use it, and the agent profiles tasks pick a model by. A lane per harness groups its tasks under their chain, and the pane header gives its health and access. See Switch a task to another harness.

+ Profile adds a profile. One labelled From Kraft's package can't be edited, renamed, copied or removed here: define it in harnesses.yaml to change it.

Policy

Policy has three tabs; a dot on a tab marks a change or a problem in it. See Caps and budgets.

TabWhat it sets
LimitsTime, token and dollar caps by scope (the work item, nodes, steps, tasks) and the daily dollar cap. A scope that sets no cap is one line, N unset caps · show
LoopsFix-loop defaults, findings and stuck-item handling. Where attempts or wall clock are set in more than one place, the most specific wins: the item's policy, then the loop's keys, then its node, then its loops: entry
HousekeepingConcurrency, relaunches, archive, the forge timeout, and the worktree storage limit and quota (a size such as 10G; blank is off). Automatic clean-up takes an age (2d). Merge request footer turns off the "Opened by Kraft" line

Auto-intake

Auto-intake sets whether Kraft starts the open, unblocked issues in each repo's bd tracker (the issues of beads) by itself, and its schedules. The status card holds the on/off switch and the pickup rule; blank Repos is every enabled repo. A cron Kraft can't run is explained and not saved. See Schedule or webhook work.

Notifications

Notifications sets where Kraft tells you it has stopped and waits for you: a Webhook and This browser. Send a test checks each. Allow notifications, and accepting the browser's prompt, turns This browser on. See Get notified when an item needs you.

Access

Access sets who can reach the board: This machine only (127.0.0.1, no password) or Local network (0.0.0.0, password required), with the port, the allowed hosts and the password. See Remote access.

Appearance

Appearance sets how the web UI looks: theme, colour, surface, accent and Density. An accent from an older file that is no longer offered (green, amber) paints as None.

Board and code

Added in 2.1

Board & code sets how Kraft behaves where you read code and work the board. It was part of Appearance, and it is the same theme.yaml: your saved choices carried over.

SettingWhat it sets
Syntax highlightingThe colour scheme for code in review diffs, for light and dark separately
Review diffSide-by-side or Inline, the added and removed colours, whitespace changes, changed words, line wrapping and one file at a time
Board › Open items inPeek, the side panel, or Full page
Default editorAn editor found on this machine, or Not set, which uses KRAFT_EDITOR, else the system's default app. Set it on a computer; a phone doesn't show it

Workers

Added in 2.4

Workers lists the machines that may run work item steps, as kraft admin worker list does, and adds, edits and removes them. Both write workers.yaml. See workers.yaml. A step that runs on a machine shows its name under machine in the task pane, and unreachable since when the connection drops.

StateIt means
onlineThe machine takes steps
offline, with a reasonKraft can't reach it
disabledIt takes no new steps; running ones finish

A row also shows how Kraft connects (this machine, over ssh or dials in) and the steps running against its limit.

ControlWhat it does
Add machineOver ssh, Add and connect saves the machine and connects once; if that fails it stays saved and Kraft keeps trying. A machine that dials in gets the kraft admin worker serve command with its token, shown once
Takes new steps offLets running steps finish and starts nothing new
Rotate token, on a dial-in machineStops the current token at once and shows a new one once
Remove machine, in the Edit dialogGreyed out while a step runs on the machine, with the reason. Otherwise the row goes after a five-second Undo. local can't be removed

On a phone, More › Workers shows the list and changes nothing.

Storage

Added in 2.1

Storage shows what the worktrees use against the limit and quota set under Policy › Housekeeping, and archives finished items when you confirm. See Free disk space.

You seeIt means
Usage bar, amberOver the quota
Usage bar, redWhat archiving can free is over the limit, and the page says starts are held
can be cleaned up, with a boxA completed or abandoned item that isn't archived. Every other row has a greyed box
Worktrees columnsPer item, largest first: its size (what archiving frees), its documents (kept by archiving, removed by abandoning), its step outputs (freed by archiving) and when it last changed
ControlWhat it does
Clean up selected, Clean up allConfirm first, showing what is freed, where usage lands against the quota and limit, and per item the uncommitted files lost and whether its branch stays. Each item moves to Archived, restorable as a record without its worktree
RefreshMeasures again, which can take half a minute on a large instance

On a phone, More › Storage shows the same figures and one Clean up all.

About

About opens from the version line at the sidebar's foot. It shows the version, whether an update is available or waits on a restart, and how this instance runs. Copy diagnostics copies them for a bug report.

Update when Kraft is free

Added in 2.3

About holds the controls for updating when Kraft is free.

ControlWhat it does
Install when free, Don'tMarks the available release, or drops the mark. A new major has its own button
Update automatically, Restart when freeThe two switches of update.yaml, both off until you turn them on
Allowed hoursThe ranges Kraft may update and restart in

A line says what is waiting and why it hasn't happened (waiting for 1 running item, outside 01:00-06:00, attached to a terminal), and the last attempt applied or failed with the reason. The sidebar's version badge reads update marked while a mark waits. With KRAFT_NO_UPDATE_CHECK set, auto-update finds no release.

Copyright © 2026