Two problems with chat channel settings in the dashboard.
An extension channel's settings cannot be entered anywhere. The email channel (archipelago channel/email) reads imap_addr, smtp_addr, username, password_ref, authserv_id and allowed_senders from the extension-settings resource, but the dashboard's Extensions page only toggles an extension on or off, and the package declares no settings schema to build a form from. Enabled without them, the channel fails five times at every Messaging start and parks with an ERROR, which also counts against the canary.
Channel connection settings live on an org page (/org/channels) beside the org's agent binding, with the instance-only fields (Telegram bot token) hidden by permission. There is one Messaging service, bot token and mailbox per instance, so connection settings belong under the instance Settings area; the org page keeps only what an org chooses (which agent answers, session defaults it may override).
Done when: a channel package can declare its settings (secret fields as secret references) and the instance Settings area renders and saves them for every installed channel, Telegram included; /org/channels shows only org choices; and an enabled channel missing a required setting shows that on its row instead of crash-looping at start.
Two problems with chat channel settings in the dashboard.
1. An extension channel's settings cannot be entered anywhere. The email channel (archipelago channel/email) reads imap_addr, smtp_addr, username, password_ref, authserv_id and allowed_senders from the extension-settings resource, but the dashboard's Extensions page only toggles an extension on or off, and the package declares no settings schema to build a form from. Enabled without them, the channel fails five times at every Messaging start and parks with an ERROR, which also counts against the canary.
2. Channel connection settings live on an org page (/org/channels) beside the org's agent binding, with the instance-only fields (Telegram bot token) hidden by permission. There is one Messaging service, bot token and mailbox per instance, so connection settings belong under the instance Settings area; the org page keeps only what an org chooses (which agent answers, session defaults it may override).
Done when: a channel package can declare its settings (secret fields as secret references) and the instance Settings area renders and saves them for every installed channel, Telegram included; /org/channels shows only org choices; and an enabled channel missing a required setting shows that on its row instead of crash-looping at start.
sam
added the high label 2026-11-07 19:37:04 +00:00
Packages declare settings (key, label, description, secret, required). A secret's key ends in _ref and is saved only as an engine:key reference (PUT /api/extensions/{name}/settings rejects undeclared keys and raw secrets; table-tested).
Instance Settings > Channels renders a form per installed channel package from its declared settings, plus Telegram's connection and the chat session defaults moved off the org page. /org/channels keeps the org's agent, allowed users and tool-call display; the system org is sent to the instance page.
An enabled channel missing a required setting is not started: it reports stopped with 'Missing ', shown on its section.
email 1.2.0 and telegram 1.1.0 declare their settings; the running email install needs updating to 1.2.0 for the check to apply.
task check passes; deployed. Not checked in a browser. Telegram still reads its connection from channel-settings: follow-up filed.
8f37cc79 (archie-core) and f55d784 (archipelago):
- Packages declare settings (key, label, description, secret, required). A secret's key ends in _ref and is saved only as an engine:key reference (PUT /api/extensions/{name}/settings rejects undeclared keys and raw secrets; table-tested).
- Instance Settings > Channels renders a form per installed channel package from its declared settings, plus Telegram's connection and the chat session defaults moved off the org page. /org/channels keeps the org's agent, allowed users and tool-call display; the system org is sent to the instance page.
- An enabled channel missing a required setting is not started: it reports stopped with 'Missing <labels>', shown on its section.
- email 1.2.0 and telegram 1.1.0 declare their settings; the running email install needs updating to 1.2.0 for the check to apply.
task check passes; deployed. Not checked in a browser. Telegram still reads its connection from channel-settings: follow-up filed.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Two problems with chat channel settings in the dashboard.
An extension channel's settings cannot be entered anywhere. The email channel (archipelago channel/email) reads imap_addr, smtp_addr, username, password_ref, authserv_id and allowed_senders from the extension-settings resource, but the dashboard's Extensions page only toggles an extension on or off, and the package declares no settings schema to build a form from. Enabled without them, the channel fails five times at every Messaging start and parks with an ERROR, which also counts against the canary.
Channel connection settings live on an org page (/org/channels) beside the org's agent binding, with the instance-only fields (Telegram bot token) hidden by permission. There is one Messaging service, bot token and mailbox per instance, so connection settings belong under the instance Settings area; the org page keeps only what an org chooses (which agent answers, session defaults it may override).
Done when: a channel package can declare its settings (secret fields as secret references) and the instance Settings area renders and saves them for every installed channel, Telegram included; /org/channels shows only org choices; and an enabled channel missing a required setting shows that on its row instead of crash-looping at start.
8f37cc79(archie-core) and f55d784 (archipelago):task check passes; deployed. Not checked in a browser. Telegram still reads its connection from channel-settings: follow-up filed.