fix(web): use prompt_async endpoint to avoid timeout over VPN/tunnel#12749
Merged
adamdotdevin merged 1 commit intoanomalyco:devfrom Feb 13, 2026
Merged
fix(web): use prompt_async endpoint to avoid timeout over VPN/tunnel#12749adamdotdevin merged 1 commit intoanomalyco:devfrom
adamdotdevin merged 1 commit intoanomalyco:devfrom
Conversation
The web UI sent prompts via POST /session/{id}/message which holds the
connection open until the agent finishes. Over Tailscale/VPN the idle
connection gets killed, showing 'Failed to send prompt' even though the
server processed it fine.
Switch to the existing POST /session/{id}/prompt_async endpoint that
returns 204 immediately. Response data already arrives through SSE.
Closes anomalyco#12453
Contributor
|
The following comment was made by an LLM, it may be inaccurate: No duplicate PRs found |
TechnicallyAnna
pushed a commit
to TechnicallyAnna/opencode
that referenced
this pull request
Feb 13, 2026
3 tasks
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What does this PR do?
The web UI sends prompts via
POST /session/{id}/message, which holds the HTTP connection open until the agent finishes. Over Tailscale/VPN, aggressive network stacks kill the idle connection before completion, showing "Failed to send prompt" even though the server received and processed it.The fix switches to the existing
POST /session/{id}/prompt_asyncendpoint which returns 204 immediately. Response data already arrives through the SSE event stream. One-word change insubmit.ts:.prompt()→.promptAsync(). Parameters are identical and the return value was unused.Includes an e2e regression test that blocks the sync endpoint and verifies the prompt still succeeds.
Closes #12453
Closes #12748
How did you verify your code works?
prompt.spec.ts— still passes, no regression