fix: debounce permission notifications to avoid false positives in auto mode

[sfdye]

Problem

In auto mode, Warp auto-approves permission requests, but the plugin still sent a "Wants to run X" notification for every permission ask — causing Warp to show false "agent blocked" notifications while the agent was working uninterrupted.

Root cause

After investigating the opencode source (packages/opencode/src/permission/index.ts across v1, PermissionNext, and current v2), both permission.updated (v1 SDK) and permission.asked (v2 SDK) fire under identical conditions — only when the ruleset evaluates to "ask". Neither event fires for auto-approved ("allow") or denied ("deny") permissions.

The false positives occur because Warp's auto mode auto-replies to permission requests at the client level: opencode publishes a genuine ask event → the plugin notifies "blocked" → Warp auto-approves → the agent continues. The user sees a notification even though no input was needed.

The event payload ({id, type, pattern, sessionID, messageID, callID, title, metadata, time}) has no outcome field, so the plugin cannot distinguish "Warp will auto-approve this" from "user must act" at fire time.

Fix

Debounce permission notifications by 500ms. If permission.replied arrives within that grace period, the notification is cancelled.

• Auto mode: Warp auto-replies within milliseconds → timer cancelled → no false "blocked" notification
• Non-auto mode: no instant reply → notification fires after 500ms → user sees it as before (a user who replies within 500ms made the notification moot anyway)
• Works whether Warp auto-approves all asks or only a subset — only auto-approved ones are suppressed

Both permission.updated (v1 SDK case) and permission.asked (v2 SDK default case) are handled with the same debounce logic, preserving compatibility across opencode versions. The permission.replied handler checks both requestID (v2) and permissionID (v1) field names, and both reply (v2) and response (v1) for the reject check.

Verification

• npm run build — clean
• npx tsx --test tests/index.test.ts tests/payload.test.ts — 23/23 assertions pass
• Manual verification in Warp pending

[sambokai]

I agree that this is annoying. Would be great if the maintainers handled it.

[sambokai]

Tested this locally on macOS at the exact PR commit b1475466e28cf7ae23459dcaa4904215c3016f23.

• bun run typecheck ✅
• bun run build ✅
• bun test ✅ (25 pass, 0 fail)
• Temporary local debounce harness ✅ (5/5)
• Manual test in Warp ✅

Most importantly, the behavior works as intended in the real Warp integration: auto-approved permission requests no longer produce the false “agent blocked” notification, while genuine permission prompts still notify correctly.

From my testing this looks good. @harryalbert would appreciate a look when possible.

Related upstream OpenCode issue: anomalyco/opencode#47545