Skip to content

feat(tui): configure every notification provider inside Settings #3570

Description

@Yeachan-Heo

Problem

Settings → Notifications currently exposes notification providers unevenly: Telegram can be configured in the TUI, while Discord and Slack are effectively non-configurable from the settings UI. Users must leave the TUI and manipulate configuration through another surface.

Required UX contract

Make every supported notification adapter configurable end-to-end inside the TUI settings flow, including Discord and Slack.

At minimum:

  • list every supported notification provider in Settings → Notifications;
  • provide provider-specific setup/edit screens for all required fields;
  • show safe masked/fingerprinted secret state without echoing full tokens/webhooks;
  • support enable/disable, edit, validation/test delivery, and recovery from invalid/incomplete configuration;
  • explain missing prerequisites and actionable errors in the TUI rather than presenting a dead/non-configurable row;
  • preserve the existing config schema, trust boundaries, and redaction rules unless a schema change is strictly required;
  • cover keyboard navigation, cancellation/back behavior, persistence/reload, malformed config, and provider-specific validation with deterministic tests;
  • update user-facing notification setup documentation.

This supersedes the incomplete UX closure of #2050 / #2088: moving notification setup into settings is not complete while supported Discord and Slack adapters cannot actually be configured there.

Owner directive source: Discord #gajae-code-dev, 2026-07-30 07:55 UTC.


[repo owner's gaebal-gajae (clawdbot) 🦞]

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions