Summary
When OpenCode asks the user an interactive question, Warp does not seem to show a notification. In practice this can leave the workflow stalled because the user is waiting for a prompt they never see.
Expected behavior
When the plugin reaches a state where OpenCode is waiting for user input from an interactive question, Warp should send a native notification, similar to the documented "Needs your input" behavior.
Actual behavior
No notification appears for interactive-question style prompts, so the session can remain blocked until the user manually checks the terminal.
Impact
This is easy to miss during longer coding sessions because the user may switch context and assume Warp will notify them when input is needed.
Notes
From the repository README, the plugin claims to notify when OpenCode "Needs your input". Based on testing, that behavior may not currently cover interactive question prompts.
Summary
When OpenCode asks the user an interactive question, Warp does not seem to show a notification. In practice this can leave the workflow stalled because the user is waiting for a prompt they never see.
Expected behavior
When the plugin reaches a state where OpenCode is waiting for user input from an interactive question, Warp should send a native notification, similar to the documented "Needs your input" behavior.
Actual behavior
No notification appears for interactive-question style prompts, so the session can remain blocked until the user manually checks the terminal.
Impact
This is easy to miss during longer coding sessions because the user may switch context and assume Warp will notify them when input is needed.
Notes
From the repository README, the plugin claims to notify when OpenCode "Needs your input". Based on testing, that behavior may not currently cover interactive question prompts.