Skip to content

fix(tui): scope attention notifications - #41601

Closed
opencode-agent[bot] wants to merge 1 commit into
devfrom
notification-scope
Closed

opencode-agent[bot] wants to merge 1 commit into
devfrom
notification-scope

Conversation

@opencode-agent

Copy link
Copy Markdown
Contributor

Summary

  • expose the directory/workspace metadata already supplied by the TUI event adapter in the plugin event-bus type
  • ignore question, permission, status, and error events that do not belong to the event session location
  • notify for permission and question requests only when they remain pending in TUI state, so auto-approved permissions do not play attention sounds

Why

The server event feed spans locations, while the built-in notification plugin previously consumed matching event names without checking their directory or workspace. Auto-approve mode also replies to permission.asked without adding the request to pending TUI state, but the notification plugin still played staplebops-06 for the transient event.

Testing

  • bun test test/cli/cmd/tui --timeout 30000 --only-failures (25 passed)
  • bun typecheck in packages/tui
  • bun typecheck in packages/plugin
  • Prettier check for changed files
  • git diff --check

Requested by: @kommander (Sebastian Herrlinger via Slack)

@github-actions

Copy link
Copy Markdown
Contributor

Automated PR Cleanup

Thank you for contributing to opencode.

Due to the high volume of PRs from users and AI agents, we periodically close older PRs using automated criteria so maintainers can focus review time on the most active and community-supported contributions.

This PR was closed because it matched the following cleanup criteria:

  • The PR was created more than 1 month ago
  • The PR had fewer than 2 positive reactions
  • Positive reactions are counted as thumbs-up, heart, celebration, or rocket reactions on the PR

PRs created within the last month are not affected by this cleanup.

If you believe this PR was closed incorrectly, or if you are still actively working on it, please leave a comment explaining why it should be reopened. A maintainer can review and reopen it if appropriate.

Thanks again for taking the time to contribute.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant