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
So I tried simple prompting using GPT models sometimes it able to respond within seconds but sometimes it takes several minutes even though it is a very simple command. for example I tried GPT 5.4 with a variant of xhigh and I just tried to update the graphify but it takes too long of the AI to respond or finish the execution.
Plugins
graphify
OpenCode version
1.15.10
Steps to reproduce
choose any GPT models and maybe like high or xhigh variant
Btw, I checked the status page and its operational
Right now I'm using v1.15.6. But I'm again having issues, like one off replies are now faster but agentic mode is getting stuckk. This is killing me. I don't know if it's an issue with opencode, ohmyopencode or in general GPT models.
And when I interrupt it snd then send "." It works
This is almost certainly a provider serving issue in SEA/Oceania. I'm currently in Philippines and having my European VPN on magically fixes the stuck and hanged states on OpenAI Provider and my flows work normally. But OpenCode not having valid paths to get these states retried after an adequate time doesn't help for sure.
Note: I run my own fork and I have just now updated it from being a month old relative to upstream to actual, this is most certainly not a regression on the part of OpenCode since the issue is present only for the last 2 days and doesn't seem to depend on the OpenCode version.
Reacted by Sayuri Nekomiya, OverHash, MS_Y, Chris Bates, Rujikorn Charakorn, John Chew, yamato, Fadhila Ikhsani, AnhVanGiang and timbo
Yeah, seems like it is an issue with provider. But certainly we can have better retry mechanism as codex can kind of brute force through this. And opencode just kinda hangs in there.
This is almost certainly a provider serving issue in SEA/Oceania. I'm currently in Philippines and having my European VPN on magically fixes the stuck and hanged states on OpenAI Provider and my flows work normally. But OpenCode not having valid paths to get these states retried after an adequate time doesn't help for sure.
Note: I run my own fork and I have just now updated it from being a month old relative to upstream to actual, this is most certainly not a regression on the part of OpenCode since the issue is present only for the last 2 days and doesn't seem to depend on the OpenCode version.
If anyone is still facing this issue that isnt using websockets openai requested the following info to help them trace down issue (I have no way of replicating this bug unfortunately):
could you capture one current reproduction on the path that is still hanging, with the 10s retry relaxed just for that controlled test? What would help us is:
model and transport
request start timestamp
whether/when response headers arrive cf-ray if headers arrive
whether/when the first stream event arrives
No prompt or output needed. This should let us distinguish a headers/connect issue from a first-event stall.
Easiest way to do this is run mitm proxy and set the HTTPS_PROXY vars. For example I have this zsh function I wrote so i can do proxy opencode:
proxy () {
if [[ -z "$1" ]]
then
echo "Usage: proxy <command>"
return 1
fi
mitmweb --listen-host 127.0.0.1 --listen-port 58888 --web-open-browser &> /dev/null &
local pid=$!
echo -n "Waiting for mitmweb..."
while ! nc -z 127.0.0.1 58888 2> /dev/null
do
sleep 0.2
done
echo " ready"
export NODE_EXTRA_CA_CERTS="/Users/$USER/.mitmproxy/mitmproxy-ca-cert.pem"
export HTTPS_PROXY="http://127.0.0.1:58888"
export HTTP_PROXY="http://127.0.0.1:58888"
export NO_PROXY="localhost,127.0.0.1"
"$@"
kill "$pid" 2> /dev/null
wait "$pid" 2> /dev/null
unset NODE_EXTRA_CA_CERTS HTTPS_PROXY HTTP_PROXY NO_PROXY
}
I wrapped OpenCode in mitmproxy to investigate as to what I can see is happening.
Unfortunately, it looks like requests are made to https://chatgpt.com/backend-api/codex, but no response is ever received from OpenAI. After ten minutes, OpenCode disconnects and retries the HTTP 1.1 call and it usually continues (usually gets routed to a new TCP/TLS connection server as well):
For what it is worth: have been running 1.15.12 for about 24 hours (in server/attach mode, with websockets), no issues, performs well. Can't yet say if it is as fast as codex again, but it is definitely responsive.
I think the mcp servers are eating the entire context window or ur supplying too many tools, they dont really give a good error in this case, we will add a tool search or code mode soon to resolve, Im assuming if u disable all the mcps it will work again, or maybe just 1 of them is causing the issue, hard to say
It was the MCP servers. 1.15.13 is working great. Many thanks 🙏🏻
What are the tool limits and should they be tracked by OpenCode on a model by model basis so you can give clear warning and not rely on model responses? I know Grok Build will error if you specify more the 200 tools.
Hi @rekram1-nodeI just wanted to ask for an update: WebSocket support is currently available only in the beta version, right? It is not available in the stable version yet, correct?
Activity
github-actions commentedon May 24, 2026
This issue might be a duplicate of existing issues. Please check:
If your issue is different or not covered by the above, please add more details to help distinguish it.
MarcoLouisNarca commentedon May 24, 2026
I checked on the https://status.openai.com/ it is operational
mrjared16 commentedon May 24, 2026
+1, same here. There seems to be an issue with GPT-5.4. GPT-5.5 is somewhat better
spidynots commentedon May 24, 2026
Same, looks like OpenAI is cooking something for 3rd party harness tools. AI doom is coming
MarcoLouisNarca commentedon May 24, 2026
for me a simple prompting like change files names it takes longer for both GPT 5.4 or GPT 5.5
AmanGusain2003 commentedon May 24, 2026
Same. I think it's due to new update. I rolled back two versions and it works fine.
LuisUrrutia commentedon May 24, 2026
Same over here @AmanGusain2003 which version are u using?
Btw, I checked the status page and its operational
AmanGusain2003 commentedon May 24, 2026
Right now I'm using v1.15.6. But I'm again having issues, like one off replies are now faster but agentic mode is getting stuckk. This is killing me. I don't know if it's an issue with opencode, ohmyopencode or in general GPT models.
And when I interrupt it snd then send "." It works
MarcoLouisNarca commentedon May 24, 2026
this needs to be resolved ASAP
MarcoLouisNarca commentedon May 24, 2026
@jlongster
ikarsokolov commentedon May 24, 2026
Issue is present in v1.14.50 too,
LPFchan commentedon May 24, 2026
this still happens with opencode 1.15.10 :(
glyphloom commentedon May 24, 2026
This is almost certainly a provider serving issue in SEA/Oceania. I'm currently in Philippines and having my European VPN on magically fixes the stuck and hanged states on OpenAI Provider and my flows work normally. But OpenCode not having valid paths to get these states retried after an adequate time doesn't help for sure.
Note: I run my own fork and I have just now updated it from being a month old relative to upstream to actual, this is most certainly not a regression on the part of OpenCode since the issue is present only for the last 2 days and doesn't seem to depend on the OpenCode version.
AmanGusain2003 commentedon May 24, 2026
Yeah, seems like it is an issue with provider. But certainly we can have better retry mechanism as codex can kind of brute force through this. And opencode just kinda hangs in there.
96 remaining items
rekram1-node commentedon May 29, 2026
If anyone is still facing this issue that isnt using websockets openai requested the following info to help them trace down issue (I have no way of replicating this bug unfortunately):
Easiest way to do this is run mitm proxy and set the HTTPS_PROXY vars. For example I have this zsh function I wrote so i can do
proxy opencode:kunal-004 commentedon May 29, 2026
@rekram1-node it was done by @OverHash
berenddeboer commentedon May 30, 2026
For what it is worth: have been running 1.15.12 for about 24 hours (in server/attach mode, with websockets), no issues, performs well. Can't yet say if it is as fast as codex again, but it is definitely responsive.
rekram1-node commentedon May 30, 2026
Ill have another websocket update soon that should have parity w/ codex (taking advantage of the previous_response_id logic to reduce latency)
thaoula commentedon May 30, 2026
Is it just me or is GPT 5.5 just not working at all in Opencode.
An error occurred while processing your request. You can retry your request, or ... (click to expand) [retrying in 2s attempt #2]I have tried adding env var above. I have tried removing it. I have tried VPN . I have tried upgrade to dev build.
Codex works fine but it aint OpenCode
rekram1-node commentedon May 30, 2026
@thaoula are u using a ton of mcp servers by chance? or any plugins?
thaoula commentedon May 30, 2026
This is all I am using.
rekram1-node commentedon May 30, 2026
I think the mcp servers are eating the entire context window or ur supplying too many tools, they dont really give a good error in this case, we will add a tool search or code mode soon to resolve, Im assuming if u disable all the mcps it will work again, or maybe just 1 of them is causing the issue, hard to say
thaoula commentedon Jun 1, 2026
It was the MCP servers. 1.15.13 is working great. Many thanks 🙏🏻
What are the tool limits and should they be tracked by OpenCode on a model by model basis so you can give clear warning and not rely on model responses? I know Grok Build will error if you specify more the 200 tools.
rekram1-node commentedon Jun 1, 2026
Im doing an mcp pass this week I hope to have better state of things by eow
ThisCCL commentedon Jun 2, 2026
I am still occasionally seeing an interruption issue with the dev build while using the experimental WebSocket path.
Environment:
@dev(0.0.0-dev-202606011039).batfile with proxy environment variablesOPENCODE_EXPERIMENTAL_WEBSOCKETS=trueBatch file:
Observed behavior:
interrupted.smashah commentedon Jun 17, 2026
do i have to reconnect codex?
MarcoLouisNarca commentedon Jun 30, 2026
Hi @rekram1-nodeI just wanted to ask for an update: WebSocket support is currently available only in the beta version, right? It is not available in the stable version yet, correct?
github-actions commentedon Aug 29, 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.