Skip to content

Fix OpenRouter strict parameter routing for runner sessions - #36

Merged
IMax153 merged 1 commit into
mainfrom
fix/openrouter-parameter-routing
Sep 14, 2026
Merged

IMax153 merged 1 commit into
mainfrom
fix/openrouter-parameter-routing

Conversation

@IMax153

@IMax153 IMax153 commented Sep 14, 2026

Copy link
Copy Markdown
Member

Slack sessions now reach the model provider but fail with OpenRouter's "No endpoints found that can handle the requested parameters" error. The pinned SDK's OpenRouter serializer emits store, prompt_cache_key, and max_completion_tokens, while the selected Groq endpoint advertises max_tokens and no storage or prompt-cache-key support.

Adapt the native OpenRouter request body to omit those OpenAI-specific fields and use max_tokens. Preserve native streaming and tool parsing, usage reporting, the 2,048-token ceiling, the selected model, Groq-only routing, and strict parameter matching.

The existing HTTP transport test now checks the serialized request on every turn and compaction call. It failed before this change and passes after it. Model deployment tests cover credential rotation, configuration immutability, and failure handling. Runner typecheck/build and vp check also pass.

Live OpenRouter acceptance remains pending deployment because the production credential is not available locally. No secret or environment-variable changes are needed.

Reference: OpenRouter provider selection, model endpoint metadata.

@IMax153
IMax153 merged commit 48f2845 into main Sep 14, 2026
1 check passed
@IMax153
IMax153 deleted the fix/openrouter-parameter-routing branch September 14, 2026 17:31
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant