Harness setup terminal is never wired: the page always says unavailable #1257
Notifications
Due Date
No due date set.
Depends on
Reference: sam/archie#1257
Reference in new issue
Block a user
webui.Server.HarnessTerminal has no assignment in any composition root, so /api/harness reports terminal:false on every process and the Harness page always shows 'Setup terminal unavailable' with prose that blames the process. The archie-ui service cannot open containers itself; the terminal has to reach a container-capable service through its contract. Done when the Harness page opens a Kit profile's PTY in a normal deployment, or the terminal and its UI are deleted.
Notes
Duplicate of archie-core-h3s0 (2026-10-01), which already specifies this backend and predates this bead (2026-10-04). Two corrections to the framing here.
"Wire it" is not a wiring fix. No type in the tree implements webui.HarnessTerminal, there is no PTY (container.ExecIn attaches stdout/stderr only, no Tty), and no terminal contract exists in proto/. h3s0's acceptance already requires a decision doc before code.
"Or delete the terminal and its UI" is wrong. egress/oauth.go is the only writer of a harness secret (PutHarnessSecret has no other caller), and both kitrun.Launcher.oauthFacts and the proxy token path already tell the operator to "run the setup terminal first". Deleting the terminal leaves the store unwritable and those messages pointing at nothing. It is only coherent as part of deleting OAuth credential support entirely (harnesssecret, the OAuth half of egress, credential_file.go, kitrun oauthFacts, the bindings page).
Also noted while verifying: h3s0 cites cmd/archie-ui/architecture_test.go as enforcing the UI-binary import ban; that file was deleted in
ff424b70, so the boundary is intent, not a gate.Imported from beads
archie-core-c3zh· GitHub #1283 · type bug · priority P1 · created 2026-10-04 · closed 2026-10-08