webui(chat): rehome update-check, Dangerous actions and Reload Telegram to Configuration #1587

Closed
opened 2026-10-27 13:40:59 +00:00 by sam · 0 comments
Owner

ChatApp carries operator-admin surfaces that are not conversation and have no place in a
chat drawer: the update check/install panel, the Dangerous actions checkpoint-approval
panel, and the Reload Telegram button (chat/chat.jsx:496-600).

Decision (Sam, 2026-09-20): these move to the Configuration route, where operator controls
already live. The model/personality/provider selects stay with chat, behind a drawer
overflow menu.

Expected

  • Update check/install moves to Configuration.
  • Dangerous actions moves to Configuration.
  • Reload Telegram moves to Configuration.
  • None of these is deleted; each keeps its current behaviour at the new location.

Related: archie-core-sod1 (dangerous-command authority is still unwired).

Notes

Update actions and Dangerous actions moved to Configuration as ui/src/settings/operator-cards.jsx, wired in settings.jsx with 501 degrading to an absent card rather than an error. Verified on the dev stack: both endpoints return 501 there, so both cards correctly render nothing; the populated states are covered by nine tests in test/settings-operator.test.js.

Reload Telegram did NOT move, deliberately. It was never an API call: handleRestartTelegram sent the '/restart' chat command as a message. Rehoming it would mean Configuration posting a chat message to reach the adapter, which is a worse coupling than leaving it where the command lives. It remains available as /restart in the command palette. The real fix is archie-core-ry4k (cross-process restart RPC); once that exists it can land here as a proper button.

Close reason

Closed


Imported from beads archie-core-tf20 · GitHub #971 · type task · priority P1 · created 2026-09-20 · closed 2026-09-20

`ChatApp` carries operator-admin surfaces that are not conversation and have no place in a chat drawer: the update check/install panel, the Dangerous actions checkpoint-approval panel, and the Reload Telegram button (`chat/chat.jsx:496-600`). Decision (Sam, 2026-09-20): these move to the Configuration route, where operator controls already live. The model/personality/provider selects stay with chat, behind a drawer overflow menu. ### Expected - Update check/install moves to Configuration. - Dangerous actions moves to Configuration. - Reload Telegram moves to Configuration. - None of these is deleted; each keeps its current behaviour at the new location. Related: archie-core-sod1 (dangerous-command authority is still unwired). ### Notes Update actions and Dangerous actions moved to Configuration as ui/src/settings/operator-cards.jsx, wired in settings.jsx with 501 degrading to an absent card rather than an error. Verified on the dev stack: both endpoints return 501 there, so both cards correctly render nothing; the populated states are covered by nine tests in test/settings-operator.test.js. Reload Telegram did NOT move, deliberately. It was never an API call: handleRestartTelegram sent the '/restart' chat command as a message. Rehoming it would mean Configuration posting a chat message to reach the adapter, which is a worse coupling than leaving it where the command lives. It remains available as /restart in the command palette. The real fix is archie-core-ry4k (cross-process restart RPC); once that exists it can land here as a proper button. ### Close reason Closed --- _Imported from beads `archie-core-tf20` · GitHub #971 · type task · priority P1 · created 2026-09-20 · closed 2026-09-20_
sam added the hightask labels 2026-10-27 13:40:59 +00:00
sam self-assigned this 2026-10-27 13:40:59 +00:00
sam closed this issue 2026-10-27 13:40:59 +00:00
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Reference: sam/archie#1587