Repository navigation
tui3: the engine road never shows '· N standing orders here' — remote.Agent has no StandingHere #1643
Closed as not planned
Description
What happened
On the default engine road (plain codeaf), a new conversation in a project with a standing rule never shows the threshold line · N standing orders here — /standing. With codeaf --no-host the same project shows it. The manual promises the line on every road. Found while checking #1545's rows against dev b267d3900.
Replication
Deterministic (no model). Add a hold standing rule scoped to a project, then open a new conversation there twice: once with codeaf (engine road) and once with codeaf --no-host. Only the second draws the line.
Where
noteStandingHereininternal/tui3/threshold.gotype-asserts the agent for aStandingHere()method.internal/remote.Agent, the engine road's agent, has no such method, so the function returns early.- The standing margin (
internal/tui3/margin.go) and the standing place (internal/tui3/place_standing.go) read the same method and share the gap. - This may share a root with standing: place scoping mismatch for project orders, stale budget on consent card, and activity label #1555's side-column rows.
The fix
remote.Agent answers StandingHere over the engine wire, the same way the in-process agent does, so every surface that reads it draws the same thing on both roads.
Acceptance
- e2e: in the tmux suite, a project with one hold rule opened with plain
codeafshows· 1 standing order here — /standingon its first frame. - Unit: a test asserts
remote.Agentsatisfies the interfacethreshold.goasserts, so a missing method fails the build rather than hiding the line.
Activity
AbirAbbas commentedon Sep 29, 2026
Still on dev and staging
461a43fb6(2026-09-29 pre-release happy-path pass), with a second symptom of the same missingStandingHereon the engine road: the standing place files orders scoped to this conversation underin other projects. A reminder ("remind me in 2 minutes to stretch"), a one-time run, and/standing always answer in one sentence in this conversation— each card saidwhere · just this conversation— were all listed underin other projects, so their row menu offered pause and stop but nonot here.internal/tui3/place_standing.go(~767) fills the first three shelves only fromagent.StandingHere();remote.Agenthas none, so the here-list is empty and everything machine-wide reads as elsewhere. Repro: plaincodeafin a git repo (engine road), make any conversation-scoped standing item, open the standing place (alt+7).santoshkumarradha commentedon Oct 23, 2026
Audited against current
dev(39fdbea6f73c).The missing
StandingHere()threshold is a contract of the retired standing-order surface. #1831 (966e2a788b11) explicitly removedStanding.*wire methods,/standing, andinternal/standing; project rules now use saved memories. Current dev has noStandingHerethreshold implementation to make remote parity with. Closing this report as obsolete after #1831, not as a claim that the old threshold was implemented. Current scoped worker-rule coverage is tracked by merged #1906.