Description
While checking #31629, I found a related Windows Desktop path: opening a file with a selected app can spawn subprocesses for app resolution or launch. Before the fix in #31933, this path did not consistently use hidden subprocess creation.
The issue is to make this path use hidden subprocess creation so it cannot create a console window when the resolved command is a console program or shim.
This is separate from the shell tool and MCP subprocess path described in #31629.
Plugins
No response
OpenCode version
Current dev while investigating #31629.
Steps to reproduce
- On Windows Desktop, open a file with a selected app.
- Trigger selected app resolution or launch through a console executable or shim, such as
where, .cmd, or .bat.
- This path should hide those subprocesses consistently.
Screenshot and/or share link
No response
Operating System
Windows 10/11
Terminal
No response
Description
While checking #31629, I found a related Windows Desktop path: opening a file with a selected app can spawn subprocesses for app resolution or launch. Before the fix in #31933, this path did not consistently use hidden subprocess creation.
The issue is to make this path use hidden subprocess creation so it cannot create a console window when the resolved command is a console program or shim.
This is separate from the shell tool and MCP subprocess path described in #31629.
Plugins
No response
OpenCode version
Current
devwhile investigating #31629.Steps to reproduce
where,.cmd, or.bat.Screenshot and/or share link
No response
Operating System
Windows 10/11
Terminal
No response