The terminal UI
Run lk with no arguments in an interactive terminal and it opens a full-screen
dashboard: the same inbox, runs, workflows, and policies the desktop app shows,
without leaving your terminal. It's a first-class way to drive loopkeep, equal to
the CLI and the desktop app — the daemon runs
underneath all three. Piped or redirected, lk prints its usage instead, so
scripts and lk | … keep working.
lk # opens the dashboard in an interactive terminalViews
Five views run across the top, each scoped to the selected project:
| View | What's in it |
|---|---|
| Inbox | Attentions waiting on you, plus the history of past ones. |
| Runs | Every run and its state — open one for its event timeline. |
| Workflows | The project's workflows: run, edit, or toggle their auto-triggers. |
| Policies | The project and personal policy, editable rule by rule. |
| Settings | Concurrency caps, worktree retention, and the global pause switch. |
Inbox, Policies, and Settings each carry two sub-tabs — Pending / History, Project / Personal, and Global / Project.
Getting around
| Keys | Action |
|---|---|
h l, ← → | Previous / next view |
j k, ↑ ↓ | Move within the list |
Shift+H Shift+L | Switch sub-tab (also [ and ]) |
Enter | Open or edit the selected item |
g | Toggle scope — this project only, or every one |
? | Show the full key list |
q | Quit |
What a selection does depends on the view. In Inbox and Runs: a
approve, s steer, d deny, t take over. In Workflows: r run now, n
new, space enable or disable its auto-triggers, e open in $EDITOR. In
Policies: x delete the selected rule.
The keys are configurable — set tui.keybindings in config.yaml (see
Daemon & configuration). The mouse works too; m toggles
mouse capture when you'd rather select text.
Editing workflows and policies
Open a workflow with Enter and you get a structured form for its
frontmatter execution settings — model, budgets, concurrency, and
execution mode — with dropdowns for the
choice fields, so there's no allowed value to remember. Open a policy rule and
you get the same field-by-field editor, one rule at a time.
To edit the raw file instead, e opens the workflow's Markdown and frontmatter,
or the policy's YAML, in your $EDITOR. Save and close, and the TUI re-reads and
re-validates it.
Next steps
- Write a workflow, then pick its triggers.
- Tune your policies — and check why something reached you.
- Take over a run to drive its session yourself.