webui(config): add Reload Telegram once a restart RPC exists #1491

Closed
opened 2026-10-27 13:40:37 +00:00 by sam · 1 comment
Owner

Split out of archie-core-tf20. The other two operator panels moved to
Configuration; this one could not.

"Reload Telegram" was never an API call. handleRestartTelegram in the old
chat panel sent the /restart chat command as a message and let the gateway
act on it. Putting a button on Configuration that posts a chat message to
restart an adapter is a worse coupling than leaving the command where commands
live, so it stays as /restart in the palette for now.

archie-core-ry4k adds the cross-process restart RPC. Once that lands, this
becomes an ordinary button on Configuration beside the other operator
controls.


Imported from beads archie-core-oif3 · GitHub #988 · type task · priority P3 · created 2026-09-20

Split out of archie-core-tf20. The other two operator panels moved to Configuration; this one could not. "Reload Telegram" was never an API call. `handleRestartTelegram` in the old chat panel sent the `/restart` chat command as a message and let the gateway act on it. Putting a button on Configuration that posts a chat message to restart an adapter is a worse coupling than leaving the command where commands live, so it stays as `/restart` in the palette for now. archie-core-ry4k adds the cross-process restart RPC. Once that lands, this becomes an ordinary button on Configuration beside the other operator controls. --- _Imported from beads `archie-core-oif3` · GitHub #988 · type task · priority P3 · created 2026-09-20_
sam added the lowtask labels 2026-10-27 13:40:37 +00:00
sam self-assigned this 2026-10-27 13:40:37 +00:00
sam added a new dependency 2026-10-27 13:42:24 +00:00
sam added a new dependency 2026-10-27 13:42:25 +00:00
Author
Owner

Closed: goes against the product plan in epic #1977. Core knows no vendor: forge- and channel-specific behaviour belongs in connector extensions (#1979), not in the core dashboard or chat.

Closed: goes against the product plan in epic #1977. Core knows no vendor: forge- and channel-specific behaviour belongs in connector extensions (#1979), not in the core dashboard or chat.
sam closed this issue 2026-11-14 14:45:13 +00:00
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Reference: sam/archie#1491