[FEATURE]: bell ansi for user acknowledgment #36472

Activity

1. github-actions

   assigned

   kommander

   on Jul 12, 2026
2. github-actions commented on Jul 12, 2026

   

   github-actionsBot

   on Jul 12, 2026 – with GitHub Actions

   Contributor

   More actions

   This issue might be a duplicate of existing issues. Please check:

   • [FEATURE]: Bell sound when response is finished! #35282: [FEATURE]: Bell sound when response is finished! — same request for an audible bell notification when the model finishes responding
   • [FEATURE]:make a sound when done clankering #23184: [FEATURE]: make a sound when done clankering — closed feature request for a completion sound notification

   Please review these issues before continuing, and consider adding your plugin examples as a comment there if relevant.
3. klonuo commented on Jul 12, 2026

   

   klonuo

   on Jul 12, 2026

   Author

   More actions

   wow, there is similar issue for any idea - nice
   kudos to guys reviewing
4. prestonbrown commented on Aug 10, 2026

   

   prestonbrown

   on Aug 10, 2026

   More actions

   +1'ing with a concrete pain point: tmux's monitor-bell window flag (! in the status line) is the main reason BEL matters. The built-in attention.sound plays an audio file through system audio — it never writes \x07 to the PTY, so tmux/screen never light up. The result: in a multiplexed session the attention signal is invisible unless you're actively listening, even with attention.enabled: true.

   For anyone hitting this today, here's a working TuiPlugin on 1.17.x. The snippet in the OP is slightly stale — TuiPlugin now returns Promise<void> (not Hooks), and disposal goes through api.lifecycle.onDispose:

   // ~/.config/opencode/plugins/terminal-bell.ts
   import type { TuiPlugin } from "@opencode-ai/plugin/tui";
   
   const RING_EVENTS = [
     "session.idle",
     "question.asked",
     "question.v2.asked",
     "permission.asked",
     "permission.v2.asked",
     "session.error",
   ] as const;
   
   let last = 0;
   const ring = () => {
     const now = Date.now();
     if (now - last < 1000) return; // coalesce the v1/v2 event pairs
     last = now;
     try { process.stdout.write("\x07"); } catch { /* never throw from a hook */ }
   };
   
   export const tui: TuiPlugin = async (api) => {
     const off = RING_EVENTS.map((t) => api.event.on(t, ring));
     api.lifecycle.onDispose(() => off.forEach((u) => u()));
   };

   Still think this belongs built-in. An attention.terminal_bell: true option that writes \x07 alongside the sound (mirroring TuiAttentionSoundName — done, question, permission, error, subagent_done) would cover every multiplexer user without forcing them to ship a plugin, and the TuiAttention API already centralizes the "when to ring" logic.

   👍React with 👍3Reacted by klo, Simon Bos and carschandler
5. github-actions commented on Oct 11, 2026

   

   github-actionsBot

   on Oct 11, 2026 – with GitHub Actions

   Contributor

   More actions

   To stay organized issues are automatically closed after 60 days of no activity. If the issue is still relevant please open a new one.
6. github-actions

   closed this as not plannedon Oct 11, 2026