TUI

The TUI is the primary operator surface. It does not run autonomy; it connects to one or more agents listed in ~/.config/steelframe/projects.toml.

steelframe
# first run (no projects.toml) opens the project wizard
steelframe config          # add another project later
steelframe config --list

Keys

Key	Action
Tab	Move between panels.
[ ]	Switch project (agent).
r	Refresh.
s	Sync issues (POST /api/tasks/sync).
o	Trigger the optimize workflow.
t	Terminate the selected run.
c or /	Open Chat (operator Q&A + retrieve).
q	Quit.

Panels

• Dashboard — environment health, capacity, active work, delivered tasks, and the workflow list. Drill into a run for its step log.
• Chat — ask about tasks, retrieve memory, or file an issue. Work still goes through issues.
• Board — the Kanban of issue-rooted work plus the local backlog.
• Config — settings, credentials, health checks, and skills.
• Audit — the append-only record of state mutations.

Operator identity

The TUI sends X-Auth-User on every request so GitHub issue footers and audit records say who acted, not unknown. Resolution order: project operator → registry operator → STEELFRAME_OPERATOR → GITHUB_USER → gh api user → $USER.

Auth

Remote agents are token-gated. The TUI presents the token as a bearer credential (Authorization: Bearer …). Prefer a per-agent token file:

ssh root@HOST cat /root/steelframe-tui.token > /tmp/steelframe-tui.token
steelframe config --name my-project --url https://my-project.example.com \
  --token-file /tmp/steelframe-tui.token --operator your-github-login

See Auth.