Skip to content

HTTP Transport Error on Chat Completion Request via OpenRouter #1081

Description

@Raphaelworld

Checked for Existing Issues?

  • Yes, I have checked existing issues and cannot find one related to this.

Software

Pieces OS, Desktop Application

Operating System / Platform

macOS

Your Pieces OS Version

12.4.1

Early Access Program

  • Yes, this is related to an Early Access Program feature.

Kindly describe the bug and include as much detail as possible on what you were doing so we can reproduce the bug.

Summary
A completion request to the OpenRouter API failed due to an HTTP transport error. The model was unable to complete the request, resulting in a failed response from the provider endpoint.

Date/Time
2026-06-22 14:54 EDT
Error Message
HTTP transport error (POST https://openrouter.ai/api/v1/chat/completions):
error sending request for url (https://openrouter.ai/api/v1/chat/completions)
[model=anthropic/claude-sonnet-4.6, provider=openrouter]
Steps to Reproduce
Send a chat completion request via POST to https://openrouter.ai/api/v1/chat/completions.
Specify model anthropic/claude-sonnet-4.6 with provider openrouter.
Observe that the request fails with an HTTP transport error before a response is received.
Expected Behavior
The API should successfully process the POST request and return a valid chat completion response.
Actual Behavior
The request fails at the HTTP transport layer. No completion is returned. The error indicates the request could not be sent to the target URL.
Root Cause (Suspected)
Temporary provider overload or network-level instability on the OpenRouter side. The error occurs at the transport layer before a response is received, suggesting the connection was dropped or refused rather than a malformed request.
Impact
failed to receive no completion output.
Any in-progress agent task is interrupted and fails to "keep going"
Workaround offered by error message
Re-send the request or instruct the agent to "Keep going" to resume from the last known state. The issue is expected to resolve on retry as it is likely transient.

Metadata

Metadata

Labels

status:triagedThe ticket has been reviewed, prioritized, categorized, and assigned to the appropriate team member.

Type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions