Skip to content

Add OpenRouter provider routing params#84579

Merged
amknight merged 1 commit into
mainfrom
ak/openrouter-provider-routing
May 20, 2026
Merged

Add OpenRouter provider routing params#84579
amknight merged 1 commit into
mainfrom
ak/openrouter-provider-routing

Conversation

@amknight

@amknight amknight commented May 20, 2026 •
edited
Loading

Copy link
Copy Markdown
Member

Summary

  • Adds an OpenRouter-owned transport params bridge for provider-routing defaults from models.providers.openrouter.params.provider.
  • Merges provider-wide, per-model, and explicit request routing params by key, with explicit params winning.
  • Writes the resolved OpenRouter routing object to the outbound chat-completions provider payload and documents the supported config path.

Verification

  • node scripts/run-vitest.mjs extensions/openrouter/index.test.ts src/agents/pi-embedded-runner-extraparams-openrouter.test.ts
  • git diff --check -- CHANGELOG.md docs/gateway/config-agents.md docs/providers/openrouter.md extensions/openrouter/index.test.ts extensions/openrouter/index.ts extensions/openrouter/stream.ts
  • git diff --no-index --check /dev/null extensions/openrouter/provider-routing.ts
  • Scoped Codex review over this patch: autoreview clean: no accepted/actionable findings reported
  • Live local Gateway E2E with disposable OPENCLAW_STATE_DIR, OpenRouter key supplied via process stdin, debug capture enabled, and openclaw agent --json --agent main --session-id e2e-openrouter-routing-success --model openrouter/auto --thinking off --message "Reply with exactly: OR_ROUTING_OK" --timeout 180

Real behavior proof

Behavior addressed: OpenRouter provider-routing config now has a documented provider-wide path and is serialized into the OpenRouter request provider payload for chat-completions routes.

Real environment tested: Real local OpenClaw Gateway from this branch on macOS, using a disposable state dir, openrouter/auto, and a live OpenRouter API key supplied only through process stdin/environment.

Exact steps or command run after this patch: Initialized disposable local config with openclaw onboard --non-interactive --accept-risk --mode local --auth-choice skip --gateway-bind loopback --gateway-port 19179 --no-install-daemon --skip-channels --skip-search --skip-skills --skip-health, patched models.providers.openrouter.params.provider, started openclaw gateway run --force --auth none --bind loopback --port 19179 --allow-unconfigured --verbose with direct debug capture enabled, then ran openclaw agent --json --agent main --session-id e2e-openrouter-routing-success --model openrouter/auto --thinking off --message "Reply with exactly: OR_ROUTING_OK" --timeout 180.

Evidence after fix: Debug capture recorded outbound POST https://openrouter.ai/api/v1/chat/completions with Authorization present, model openrouter/auto, stream: true, and payload provider: { sort: "latency", data_collection: "deny" }; the corresponding OpenRouter response was HTTP 200 text/event-stream. A prior capture with per-model require_parameters: true recorded provider: { sort: "latency", data_collection: "deny", require_parameters: true } and OpenRouter returned its provider-routing 404, confirming the merged model-level knob was transmitted.

Observed result after fix: The local Gateway completed the live agent turn successfully and returned exactly OR_ROUTING_OK.

What was not tested: A broad OpenRouter provider matrix and non-OpenRouter custom proxy routes were not exercised.

@openclaw-barnacle openclaw-barnacle Bot added docs Improvements or additions to documentation gateway Gateway runtime extensions: openrouter size: S maintainer Maintainer-authored PR labels May 20, 2026
@clawsweeper

clawsweeper Bot commented May 20, 2026 •
edited
Loading

Copy link
Copy Markdown
Contributor

Codex review: needs maintainer review before merge.

Workflow note: Future ClawSweeper reviews update this same comment in place.

How this review workflow works
  • ClawSweeper keeps one durable marker-backed review comment per issue or PR.
  • Re-runs edit this comment so the latest verdict, findings, and automation markers stay together instead of adding duplicate bot comments.
  • A fresh review can be triggered by eligible @clawsweeper re-review comments, exact-item GitHub events, scheduled/background review runs, or manual workflow dispatch.
  • PR/issue authors and users with repository write access can comment @clawsweeper re-review or @clawsweeper re-run on an open PR or issue to request a fresh review only.
  • Maintainers can also comment @clawsweeper review to request a fresh review only.
  • Fresh-review commands do not start repair, autofix, rebase, CI repair, or automerge.
  • Maintainer-only repair and merge flows require explicit commands such as @clawsweeper autofix, @clawsweeper automerge, @clawsweeper fix ci, or @clawsweeper address review.
  • Maintainers can comment @clawsweeper explain to ask for more context, or @clawsweeper stop to stop active automation.

Summary
The PR adds an OpenRouter plugin hook that merges provider-wide, model, and explicit routing params into the outbound OpenRouter provider request payload, with docs, tests, and a changelog entry.

Reproducibility: not applicable. this is a feature PR rather than a broken-behavior report. Source inspection shows current main already has per-model routing, while the PR adds the new provider-wide default path and payload serialization tests.

PR rating
Overall: 🐚 platinum hermit
Proof: 🌊 off-meta tidepool
Patch quality: 🐚 platinum hermit
Summary: The patch is focused and well-covered by targeted tests, with merge confidence mainly limited by upgrade-visible provider-routing behavior rather than an identified correctness bug.

Rank-up moves:

  • Confirm maintainer acceptance that existing models.providers.openrouter.params.provider values should begin affecting all OpenRouter text requests.
What the crustacean ranks mean
  • 🦀 challenger crab: rare, exceptional readiness with strong proof, clean implementation, and convincing validation.
  • 🦞 diamond lobster: very strong readiness with only minor maintainer review expected.
  • 🐚 platinum hermit: good normal PR, likely mergeable with ordinary maintainer review.
  • 🦐 gold shrimp: useful signal, but proof or patch confidence is still limited.
  • 🦪 silver shellfish: thin signal; proof, validation, or implementation needs work.
  • 🧂 unranked krab: not merge-ready because proof is missing/unusable or there are serious correctness or safety concerns.
  • 🌊 off-meta tidepool: rating does not apply to this item.

Shiny media proof means a screenshot, video, or linked artifact directly shows the changed behavior. Runtime, network, CSP, and security claims still need visible diagnostics.

Real behavior proof
Not applicable: The external-contributor real behavior proof gate does not apply to this MEMBER/maintainer-labeled PR; the body provides targeted test output but no live OpenRouter call.

Risk before merge

  • Merging makes models.providers.openrouter.params.provider a live provider-wide routing default; any existing latent or invalid object at that path would start influencing all OpenRouter text requests or fail upstream after upgrade.
  • The PR body verifies mocked outbound payload/tests only and explicitly says no live OpenRouter API request was sent, so maintainers still need to decide whether targeted tests are enough for this provider-routing change.

Maintainer options:

  1. Accept provider-wide routing (recommended)
    Treat the new provider-wide params.provider path as intentional documented behavior and merge after normal maintainer review confirms latent configs should now take effect.
  2. Narrow the rollout
    If latent config compatibility is not acceptable, restrict the behavior to already-documented per-model params or add an explicit opt-in path before merging.

Next step before merge
The PR is a protected maintainer draft with no narrow automated repair finding; maintainers need to review the provider-routing upgrade behavior and decide proof expectations.

Security
Cleared: No concrete security or supply-chain regression was found; the diff adds no dependency or workflow changes and sanitizes prototype-polluting record keys before forwarding config-derived routing data.

Review details

Best possible solution:

Land the provider-owned hook if maintainers accept provider-wide OpenRouter routing defaults as intentional upgrade behavior, with focused tests covering default, per-model, and explicit override precedence.

Do we have a high-confidence way to reproduce the issue?

Not applicable; this is a feature PR rather than a broken-behavior report. Source inspection shows current main already has per-model routing, while the PR adds the new provider-wide default path and payload serialization tests.

Is this the best way to solve the issue?

Yes, the provider-owned extraParamsForTransport hook is the right boundary for OpenRouter-specific request metadata. The main remaining question is upgrade acceptance for making provider-wide routing config live.

Label changes:

  • add P2: This is a normal user-facing provider-routing improvement with limited surface but real model/provider selection impact.
  • add merge-risk: 🚨 compatibility: The PR turns a provider-wide config path into live request behavior, so existing ignored config can affect requests after upgrade.
  • add merge-risk: 🚨 auth-provider: The changed payload directly controls OpenRouter provider routing, fallback, privacy, and model-provider selection behavior.
  • add rating: 🐚 platinum hermit: Current PR rating is 🐚 platinum hermit because proof is 🌊 off-meta tidepool, patch quality is 🐚 platinum hermit, and The patch is focused and well-covered by targeted tests, with merge confidence mainly limited by upgrade-visible provider-routing behavior rather than an identified correctness bug.
  • add status: 👀 ready for maintainer look: ClawSweeper has no concrete contributor-facing blocker left for this PR. Not applicable: The external-contributor real behavior proof gate does not apply to this MEMBER/maintainer-labeled PR; the body provides targeted test output but no live OpenRouter call.

Label justifications:

  • P2: This is a normal user-facing provider-routing improvement with limited surface but real model/provider selection impact.
  • merge-risk: 🚨 compatibility: The PR turns a provider-wide config path into live request behavior, so existing ignored config can affect requests after upgrade.
  • merge-risk: 🚨 auth-provider: The changed payload directly controls OpenRouter provider routing, fallback, privacy, and model-provider selection behavior.
  • rating: 🐚 platinum hermit: Current PR rating is 🐚 platinum hermit because proof is 🌊 off-meta tidepool, patch quality is 🐚 platinum hermit, and The patch is focused and well-covered by targeted tests, with merge confidence mainly limited by upgrade-visible provider-routing behavior rather than an identified correctness bug.
  • status: 👀 ready for maintainer look: ClawSweeper has no concrete contributor-facing blocker left for this PR. Not applicable: The external-contributor real behavior proof gate does not apply to this MEMBER/maintainer-labeled PR; the body provides targeted test output but no live OpenRouter call.

What I checked:

  • Protected maintainer PR: The item is a draft pull request authored by a MEMBER and labeled maintainer, which repository cleanup policy treats as requiring explicit maintainer handling rather than auto-close.
  • Current per-model routing support already exists: Current main already reads ctx.extraParams.provider in the OpenRouter plugin and injects it into compat.openRouterRouting; the PR's unique useful part is the provider-wide/default merge and explicit payload bridge. (extensions/openrouter/stream.ts:203, 9c00268914b9)
  • Current extra-param resolution does not read provider-wide params directly: Current main resolves extra params from agents.defaults.params, agents.defaults.models[...], and per-agent params, then calls the provider extraParamsForTransport hook; the PR uses that seam for OpenRouter-owned provider-wide defaults. (src/agents/pi-embedded-runner/extra-params.ts:81, 9c00268914b9)
  • PR implementation uses the provider-owned hook: The patch adds resolveOpenRouterExtraParamsForTransport, sanitizes JSON-like provider routing objects, merges provider/model/explicit routing by key, and registers it as OpenRouter's extraParamsForTransport hook. (extensions/openrouter/provider-routing.ts:63, 4775708ded20)
  • Dependency contract supports a request provider object: OpenRouter's official provider-routing docs say Chat Completions requests can customize routing with a provider object and list fields such as order, allow_fallbacks, require_parameters, data_collection, only, ignore, quantizations, sort, latency/throughput preferences, and max_price. (openrouter.ai)
  • Related implemented path: Merged PR feat: pass through OpenRouter provider routing params #17148 previously implemented per-model params.provider pass-through for [Feature]: Support OpenRouter provider pinning (provider.only / provider.order) in OpenClaw model config #10869; this PR builds on that path rather than replacing it. (57187f8e9b4b)

Likely related people:

  • carrotRakko: Authored the merged per-model OpenRouter provider-routing pass-through that current main already relies on for params.provider. (role: introduced related behavior; confidence: high; commits: 57187f8e9b4b, 415686244a8b; files: extensions/openrouter/stream.ts, extensions/openrouter/index.test.ts)
  • vincentkoc: Merged the earlier OpenRouter routing PR and has recent OpenRouter/provider stream work in the same area. (role: merger and recent area contributor; confidence: medium; commits: 415686244a8b, 63ebe372e8fb, a7436c8b4a93; files: extensions/openrouter/stream.ts, extensions/openrouter/index.ts, src/agents/pi-embedded-runner/extra-params.ts)
  • steipete: Recent commits touched OpenRouter stream behavior, OpenRouter provider registration, and shared extra-param handling used by this patch. (role: recent adjacent contributor; confidence: medium; commits: c5a4d7af415d, f45390416565, d5eec80e3403; files: extensions/openrouter/stream.ts, extensions/openrouter/index.ts, src/agents/pi-embedded-runner/extra-params.ts)

Codex review notes: model gpt-5.5, reasoning high; reviewed against 9c00268914b9.

@clawsweeper clawsweeper Bot added rating: 🐚 platinum hermit Good normal PR readiness with ordinary maintainer review expected. status: 👀 ready for maintainer look ClawSweeper has no concrete contributor-facing blocker left for this PR. P2 Normal backlog priority with limited blast radius. merge-risk: 🚨 compatibility 🚨 May break existing users, config, migrations, defaults, or upgrade paths. merge-risk: 🚨 auth-provider 🚨 May break OAuth, tokens, provider routing, model choice, or credentials. labels May 20, 2026
@clawsweeper

clawsweeper Bot commented May 20, 2026

Copy link
Copy Markdown
Contributor

ClawSweeper PR egg

✨ Hatched: 🥚 common Velvet Lint Imp

Hatch command

Comment @clawsweeper hatch when this PR is hatchable.

Hatchability rules:

  • Merged PRs are hatchable.
  • Open PRs are hatchable when they are status: 👀 ready for maintainer look, status: 🚀 automerge armed, or labeled clawsweeper:automerge.
  • Closed unmerged PRs are hatchable only when one of those hatchable labels is still present in the durable record.

Rarity: 🥚 common.
Trait: stacks clean commits.
Image traits: location proof lagoon; accessory little merge flag; palette cobalt, lime, and pearl; mood patient; pose guarding a tiny green check; shell frosted glass shell; lighting clean product lighting; background small green status lights.
Share on X: post this hatch
Copy: My PR egg hatched a 🥚 common Velvet Lint Imp in ClawSweeper.

What is this egg doing here?
  • Eggs appear after the PR passes real-behavior proof. It is here for vibes, not verdicts: it does not change labels, ratings, merge decisions, or automation.
  • The shell reacts to review momentum: open follow-up work warms it up, re-review makes it wobble, and a clean final review lets it hatch.
  • Hatchability usually comes from sufficient real-behavior proof, no blocking P0/P1/P2 findings, no security attention needed, and clean correctness. A merged PR is already final, so merge makes the egg hatchable independently.
  • The hatch is seeded from this repository and PR number, so the same PR keeps the same creature; the reviewed head SHA can only change safe visual details.
  • Rarity is just collectible sparkle: 🥚 common, 🌱 uncommon, 💎 rare, ✨ glimmer, and 🌈 legendary.

@amknight amknight marked this pull request as ready for review May 20, 2026 13:26
@amknight amknight merged commit ac69776 into main May 20, 2026
195 of 216 checks passed
@amknight amknight deleted the ak/openrouter-provider-routing branch May 20, 2026 13:27
@clawsweeper clawsweeper Bot mentioned this pull request May 20, 2026
Open
@github-actions github-actions Bot mentioned this pull request May 20, 2026
Open
RomneyDa added a commit that referenced this pull request May 20, 2026
@RomneyDa
fix(openrouter): drop empty spread fallbacks for new oxlint rule
1c00457 
The 94ac563 dep bump moved oxlint to 1.65.0 (with unicorn
no-useless-fallback-in-spread enforced), and the OpenRouter provider
routing helper added in #84579 (merged into main after this branch
opened) uses '...(value ?? {})' on records that may be undefined.
Spreading undefined already yields {}, so the empty fallbacks are
redundant. Drop them so check-lint and check-additional-extension-bundled
go green.
@amittell amittell mentioned this pull request May 20, 2026
Closed
3 tasks
amittell added a commit to amittell/openclaw that referenced this pull request May 20, 2026
@amittell @claude
fix(openrouter): drop empty-object fallbacks from provider-routing sp…
fa36345 
…reads

`...(x ?? {})` and `...(cond ? {x} : {})` patterns trip oxlint's
`unicorn/no-useless-fallback-in-spread` rule because spreading `undefined`/
`false`/`null` into an object literal is already a no-op — the empty-object
fallback adds nothing. Removing the fallbacks restores `check-additional-
extension-bundled` to green; the lint regression was introduced by openclaw#84579 and
has been failing on every PR rebased onto current main since.

Behavior unchanged: `{ ...undefined }` evaluates to `{}` exactly like
`{ ...({} ?? {}) }`, and the conditional `provider: providerRouting` is now
set imperatively when truthy, matching the prior contract that only attaches
the key when a routing record is present.

Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
(cherry picked from commit 251c419)
amittell added a commit to amittell/openclaw that referenced this pull request May 20, 2026
@amittell @claude
fix(openrouter): drop empty-object fallbacks from provider-routing sp…
fe1b47a 
…reads

`...(x ?? {})` and `...(cond ? {x} : {})` patterns trip oxlint's
`unicorn/no-useless-fallback-in-spread` rule because spreading `undefined`/
`false`/`null` into an object literal is already a no-op — the empty-object
fallback adds nothing. Removing the fallbacks restores `check-additional-
extension-bundled` to green; the lint regression was introduced by openclaw#84579 and
has been failing on every PR rebased onto current main since.

Behavior unchanged: `{ ...undefined }` evaluates to `{}` exactly like
`{ ...({} ?? {}) }`, and the conditional `provider: providerRouting` is now
set imperatively when truthy, matching the prior contract that only attaches
the key when a routing record is present.

Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
(cherry picked from commit 251c419)
frankhli843 added a commit to gemmaclaw/gemmaclaw that referenced this pull request May 21, 2026
@frankhli843 @RomneyDa
@altaywtf @clawsweeper @Takhoffman @giodl73-repo @yaoyi1222 @sjf @moeedahmed @jalehman @amknight @galiniliev
maintenance: selective upstream sync 2026-05-21 (8 commits ported)
251f6f6 
* fix(errors): dedupe identical messages when traversing error .cause chain (openclaw#84556)

Merged via squash.

Prepared head SHA: 46aa27f
Co-authored-by: RomneyDa <6581799+RomneyDa@users.noreply.github.com>
Co-authored-by: altaywtf <9790196+altaywtf@users.noreply.github.com>
Reviewed-by: @altaywtf

* fix(cli): gate exported subcli descriptors (openclaw#84519)

Summary:
- This PR filters exported sub-CLI descriptors through the private-QA gate, centralizes that filter, adds regr ... ge, and carries small validation repairs in workspace glob and tunnel-timeout tests plus a changelog entry.
- Reproducibility: yes. Current-main source shows the raw SUB_CLI_DESCRIPTORS export can include qa while the helper surfaces filter it, and src/cli/argv.ts consumes that export for root command policy.

Automerge notes:
- PR branch already contained follow-up commit before automerge: fix(cli): gate exported subcli descriptors
- PR branch already contained follow-up commit before automerge: fix(clawsweeper): address review for automerge-openclaw-openclaw-8451…

Validation:
- ClawSweeper review passed for head ba197a6.
- Required merge gates passed before the squash merge.

Prepared head SHA: ba197a6
Review: openclaw#84519 (comment)

Co-authored-by: Zhaocun <zhaocunsun@gmail.com>
Co-authored-by: clawsweeper <274271284+clawsweeper[bot]@users.noreply.github.com>
Co-authored-by: clawsweeper[bot] <274271284+clawsweeper[bot]@users.noreply.github.com>
Approved-by: takhoffman
Co-authored-by: takhoffman <781889+takhoffman@users.noreply.github.com>

* fix(doctor): migrate invalid thinking formats (openclaw#84626)

* fix(cron-cli): bound loadCronJobForShow pagination (openclaw#83856) (openclaw#83989)

Summary:
- Adds a 50-page and advancing-`nextOffset` guard to `loadCronJobForShow`, exports that helper for regression tests, and adds an unreleased changelog entry.
- Reproducibility: yes. Current main is source-reproducible because `loadCronJobForShow` loops while `hasMore` ... ed numeric `nextOffset`; the PR discussion also includes terminal before/after proof for the same CLI path.

Automerge notes:
- No ClawSweeper repair was needed after automerge opt-in.

Validation:
- ClawSweeper review passed for head 7828b4b.
- Required merge gates passed before the squash merge.

Prepared head SHA: 7828b4b
Review: openclaw#83989 (comment)

Co-authored-by: clawsweeper <274271284+clawsweeper[bot]@users.noreply.github.com>
Co-authored-by: clawsweeper[bot] <274271284+clawsweeper[bot]@users.noreply.github.com>
Approved-by: takhoffman
Co-authored-by: takhoffman <781889+takhoffman@users.noreply.github.com>

* fix(config): accept execApprovals.enabled="auto" in zod schema

* fix: honour tool error suppression for mutating tools (openclaw#81561)

Merged via squash.

Prepared head SHA: 7462a86
Co-authored-by: moeedahmed <5780040+moeedahmed@users.noreply.github.com>
Co-authored-by: jalehman <550978+jalehman@users.noreply.github.com>
Reviewed-by: @jalehman

* Add OpenRouter provider routing params (openclaw#84579)

Co-authored-by: Alex Knight <15041791+amknight@users.noreply.github.com>

* Preserve AGENTS.md policy during bootstrap truncation (openclaw#82921)

Fixes openclaw#82920

* chore: regenerate base config schema

Updated after MODEL_THINKING_FORMATS changed from z.union literals to
z.enum, and session/session.agentToAgent gained detailed help text.

* Revert "Add OpenRouter provider routing params (openclaw#84579)"

This reverts commit 53254dc.

---------

Co-authored-by: Dallin Romney <dallinromney@gmail.com>
Co-authored-by: RomneyDa <6581799+RomneyDa@users.noreply.github.com>
Co-authored-by: altaywtf <9790196+altaywtf@users.noreply.github.com>
Co-authored-by: Zhaocun Sun <zhaocunsun@gmail.com>
Co-authored-by: clawsweeper <274271284+clawsweeper[bot]@users.noreply.github.com>
Co-authored-by: takhoffman <781889+takhoffman@users.noreply.github.com>
Co-authored-by: Gio Della-Libera <giodl73@gmail.com>
Co-authored-by: yaoyi1222 <yaoyi_1222@163.com>
Co-authored-by: Sarah Fortune <sarah.fortune@gmail.com>
Co-authored-by: Moeed Ahmed <drmoeedahmed@gmail.com>
Co-authored-by: moeedahmed <5780040+moeedahmed@users.noreply.github.com>
Co-authored-by: jalehman <550978+jalehman@users.noreply.github.com>
Co-authored-by: Alex Knight <aknight@atlassian.com>
Co-authored-by: Alex Knight <15041791+amknight@users.noreply.github.com>
Co-authored-by: Galin Iliev <iliev@galcho.com>
@clawsweeper clawsweeper Bot mentioned this pull request May 22, 2026
Open
5 tasks
SebTardif pushed a commit to SebTardif/openclaw that referenced this pull request May 24, 2026
@amknight @SebTardif
Add OpenRouter provider routing params (openclaw#84579)
54d003c 
Co-authored-by: Alex Knight <15041791+amknight@users.noreply.github.com>
SebTardif pushed a commit to SebTardif/openclaw that referenced this pull request May 24, 2026
@amknight @SebTardif
Add OpenRouter provider routing params (openclaw#84579)
a2c9b26 
Co-authored-by: Alex Knight <15041791+amknight@users.noreply.github.com>
SebTardif pushed a commit to SebTardif/openclaw that referenced this pull request May 24, 2026
@amknight @SebTardif
Add OpenRouter provider routing params (openclaw#84579)
99e8943 
Co-authored-by: Alex Knight <15041791+amknight@users.noreply.github.com>
github-actions Bot pushed a commit to Desicool/openclaw that referenced this pull request May 24, 2026
@amknight
Add OpenRouter provider routing params (openclaw#84579)
cd44e97 
Co-authored-by: Alex Knight <15041791+amknight@users.noreply.github.com>
galiniliev pushed a commit to galiniliev/openclaw that referenced this pull request May 25, 2026
@amknight
Add OpenRouter provider routing params (openclaw#84579)
628fa6d 
Co-authored-by: Alex Knight <15041791+amknight@users.noreply.github.com>
SebTardif pushed a commit to SebTardif/openclaw that referenced this pull request May 26, 2026
@amknight @SebTardif
Add OpenRouter provider routing params (openclaw#84579)
af25682 
Co-authored-by: Alex Knight <15041791+amknight@users.noreply.github.com>
SebTardif pushed a commit to SebTardif/openclaw that referenced this pull request May 26, 2026
@amknight @SebTardif
Add OpenRouter provider routing params (openclaw#84579)
e67bd29 
Co-authored-by: Alex Knight <15041791+amknight@users.noreply.github.com>
SebTardif pushed a commit to SebTardif/openclaw that referenced this pull request May 26, 2026
@amknight @SebTardif
Add OpenRouter provider routing params (openclaw#84579)
86ac7fd 
Co-authored-by: Alex Knight <15041791+amknight@users.noreply.github.com>
jameslcowan pushed a commit to jameslcowan/openclaw that referenced this pull request Jun 2, 2026
@amknight
Add OpenRouter provider routing params (openclaw#84579)
4bbc1f6 
Co-authored-by: Alex Knight <15041791+amknight@users.noreply.github.com>
SYU8384 pushed a commit to SYU8384/openclaw that referenced this pull request Jun 3, 2026
@amknight
Add OpenRouter provider routing params (openclaw#84579)
09e4d32 
Co-authored-by: Alex Knight <15041791+amknight@users.noreply.github.com>
sablehead pushed a commit to sablehead/openclaw that referenced this pull request Jun 10, 2026
@amknight
Add OpenRouter provider routing params (openclaw#84579)
331d9f7 
Co-authored-by: Alex Knight <15041791+amknight@users.noreply.github.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

No reviews

Assignees

No one assigned

Labels

docs Improvements or additions to documentation extensions: openrouter gateway Gateway runtime maintainer Maintainer-authored PR merge-risk: 🚨 auth-provider 🚨 May break OAuth, tokens, provider routing, model choice, or credentials. merge-risk: 🚨 compatibility 🚨 May break existing users, config, migrations, defaults, or upgrade paths. P2 Normal backlog priority with limited blast radius. rating: 🐚 platinum hermit Good normal PR readiness with ordinary maintainer review expected. size: S status: 👀 ready for maintainer look ClawSweeper has no concrete contributor-facing blocker left for this PR.

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

1 participant

@amknight