You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
bug: agent-browser hangs on simple commands in PowerShell 7.6 #25938
When using OpenCode in PowerShell 7.6, agent-browser commands (e.g. agent-browser open https://example.com) frequently hang indefinitely on simple operations that should complete in seconds.
What works:
Windows Terminal (WSL) + OpenCode + agent-browser → no issues
PowerShell 7.6 + Claude Code + agent-browser → no issues
The issue is specific to the PowerShell + OpenCode combination. Same commands work fine when switching to WSL or using a different AI agent in the same PowerShell session.
Steps to reproduce
Open PowerShell 7.6 on Windows
Launch OpenCode
Ask OpenCode to use agent-browser to visit any website (e.g. agent-browser open https://example.com)
The screenshot link appears to be a placeholder (https://github.com/user-attachments/assets/example) rather than a real attached image. Please attach an actual screenshot or remove the screenshot section if one isn't available.
Please edit this issue to address the above within 2 hours, or it will be automatically closed.
This issue might be a duplicate of existing issues. Please check:
Thanks for updating the issue! It now meets our contributing guidelines — the bug report includes a clear description, steps to reproduce, and environment details. We appreciate you taking the time to fix it up.
Based on my observations, when agent-browser is executed for the first time (for example, agent-browser open http://example.com), it spawns a background daemon process and the main CLI process exits successfully.
However, OpenCode still keeps waiting for the command to finish. My guess is that the background daemon process may still be holding inherited stdio/pipe handles from the parent process.
If the daemon is already running, agent-browser commands work normally in OpenCode.
PR #29831 fixes this by completing spawn on 'exit' event instead of only 'close'. This solves the hang when agent-browser spawns a daemon that keeps stdio pipes open. Multiple users have confirmed it works on Windows with PowerShell.
Activity
github-actions commentedon May 5, 2026
This issue doesn't fully meet our contributing guidelines.
What needs to be fixed:
https://github.com/user-attachments/assets/example) rather than a real attached image. Please attach an actual screenshot or remove the screenshot section if one isn't available.Please edit this issue to address the above within 2 hours, or it will be automatically closed.
This issue might be a duplicate of existing issues. Please check:
If you believe this was flagged incorrectly, please let a maintainer know.
github-actions commentedon May 5, 2026
Thanks for updating the issue! It now meets our contributing guidelines — the bug report includes a clear description, steps to reproduce, and environment details. We appreciate you taking the time to fix it up.
h-kls commentedon May 11, 2026
Based on my observations, when agent-browser is executed for the first time (for example, agent-browser open http://example.com), it spawns a background daemon process and the main CLI process exits successfully.
However, OpenCode still keeps waiting for the command to finish. My guess is that the background daemon process may still be holding inherited stdio/pipe handles from the parent process.
If the daemon is already running, agent-browser commands work normally in OpenCode.
JustSidus commentedon Jun 12, 2026
PR #29831 fixes this by completing spawn on 'exit' event instead of only 'close'. This solves the hang when agent-browser spawns a daemon that keeps stdio pipes open. Multiple users have confirmed it works on Windows with PowerShell.
github-actions commentedon Aug 12, 2026
To stay organized issues are automatically closed after 60 days of no activity. If the issue is still relevant please open a new one.