-
Notifications
You must be signed in to change notification settings - Fork 1.2k
[Bug]:OpenCode engine fails to start on Windows when using HTTP proxy #1276
Description
Summary
On Windows, the OpenWork desktop application is unable to successfully start or connect to the OpenCode engine. The system environment uses an HTTP proxy for internet access, which seems to interfere with the engine's initialization or the internal communication between OpenWork and OpenCode.
To Reproduce
Install OpenWork on a Windows machine.
Configure a system-wide or environment-level HTTP proxy (e.g., set HTTP_PROXY=http://...).
Launch the OpenWork application.
Observe the status: The "OpenCode engine" remains in a "Failed" state and never becomes ready.
Expected behavior
The OpenCode engine should be able to start and bypass the proxy for local communication (127.0.0.1), or respect the proxy settings for external model API calls without crashing the local process.
Actual behavior
The engine fails to initialize. No clear error message is provided in the UI, but the application cannot perform any AI tasks because the underlying OpenCode service is unreachable.
Screenshots (optional)
No response
OW version & Desktop info (optional)
No response
Additional context (optional)
No response