[ENHANCEMENT] Run hook command on events requiring prompts

[Zocker1999NET]

Problem (one or two sentences)

It may happen that Roo Code issues an event or notification requiring some input by the user. But it might be that users may overhear the soundeffect audio or TTS.

Context (who is affected and when)

When Roo Code is working on its own & not all actions are auto-approved for whatever reason. I think may happen to most users when Roo Code takes a long time but the users are cautious about what Roo Code is allowed to do.

Desired behavior (conceptual, not technical)

Add an option allowing users to configure a hook command, which gets automatically executed. This may allow users to supply a script which forwards to notification over a service of their choice to another device (e.g. their smart home or smartphone).

Constraints / preferences (optional)

Supply the script with some well-defined arguments which are properly escaped. Only execute the command directly (not via shell indirection) for security reasons.

Request checklist

• I've searched existing Issues and Discussions for duplicates
• This describes a specific problem with clear context and impact

Roo Code Task Links (optional)

No response

Acceptance criteria (optional)

No response

Proposed approach (optional)

No response

Trade-offs / risks (optional)

No response

[roomote-v0]

I've analyzed this issue and here's my proposed implementation plan:

Overview

Add a new "Notification Hook Command" setting that lets users specify an external command to run whenever Roo Code requires user interaction (approval, followup question, etc.). The command will be executed directly (not via a shell) with well-defined, escaped arguments describing the event.

Trigger Points

The hook would fire on the same events that currently trigger sounds/notifications in the extension. Specifically, it hooks into the Task.ask() flow in src/core/task/Task.ts, at the point where approval.decision === "ask" (i.e., the task is blocked waiting for user input and auto-approval did not handle it). This covers all interactive asks (followup, command, tool, use_mcp_server), idle asks (completion_result, api_req_failed, mistake_limit_reached, auto_approval_max_req_reached, resume_completed_task), and resumable asks (resume_task).

Implementation Plan

1. Add new setting to the global settings schema

• File: packages/types/src/global-settings.ts
• Add notificationHookCommand: z.string().optional() to the settings schema
• Add default value of undefined (disabled by default)

2. Add the setting to ExtensionState

• File: packages/types/src/vscode-extension-host.ts
• Add notificationHookCommand to the ExtensionState pick type so the webview can read/write it

3. Create the hook execution utility

• File: src/utils/notificationHook.ts (new file)
• Use Node.js child_process.execFile (not exec / not shell) for security, as the issue requests
• Arguments passed to the command: --event <ask-type> and --message <summary-text>
• Arguments will be passed as an array to execFile, avoiding shell injection
• Include a timeout (e.g., 10 seconds) to prevent hanging
• Fire-and-forget: errors are logged but do not block the task flow
• Include a debounce/cooldown to prevent spamming the hook on rapid successive asks

4. Call the hook from Task.ask()

• File: src/core/task/Task.ts
• In the ask() method, after the approval.decision === "ask" branch (where isStatusMutable is true), call the notification hook utility if the setting is configured
• Pass the ask type and a summary of the ask text

5. Add UI for the setting

• File: webview-ui/src/components/settings/NotificationSettings.tsx
• Add a text input field for "Notification Hook Command" below the existing sound/TTS settings
• Include a description explaining the feature and the arguments the command will receive

6. Wire up state management

• File: src/core/webview/ClineProvider.ts
• Ensure notificationHookCommand is read from and written to global state
• File: webview-ui/src/context/ExtensionStateContext.tsx
• Add the new field to the context

7. Add i18n strings

• Add translation keys for the new setting label and description

8. Tests

• Unit tests for the new notificationHook.ts utility (mocking execFile)
• Test that the hook is invoked from Task.ask() when configured
• Test that shell metacharacters in the message are safely handled (since we use execFile with array args, not shell)

Command Interface

The user's configured command would be called like:

/path/to/script --event "followup" --message "What framework would you like to use?"

Arguments:

• --event: The ask type (e.g., followup, command, tool, completion_result, api_req_failed, etc.)
• --message: A summary of what Roo Code is asking about (truncated to a reasonable length)

Security Considerations

• Uses execFile (not exec), so the command is invoked directly without shell interpretation
• Arguments are passed as an array, preventing injection
• Timeout prevents the hook from blocking indefinitely
• Errors in the hook do not affect task execution

This approach is minimal, secure, and gives users maximum flexibility to forward notifications to any service they want (push notifications, smart home, webhooks, etc.).

Please mention @roomote in a comment saying that you approve this plan, and I'll proceed with the implementation.