Greptile Summary

This PR adds service_tier support for Amazon Bedrock models, allowing users to select flex, priority, default, or reserved tiers via agents.defaults.params.serviceTier. The feature is implemented in two separate paths — the extension's wrapStreamFn and the pi-embedded-runner wrappers — but the two implementations are not fully aligned.

• P1 — Missing API guard in extension path: createServiceTierWrapStreamFn in the extension injects serviceTier into the onPayload callback for all model API types. The parallel createBedrockServiceTierWrapper in bedrock-stream-wrappers.ts correctly skips the patch when model.api !== \"bedrock-converse-stream\". Without that guard, a non-converse Bedrock API call will receive an unexpected field and Bedrock will return a validation error.
• P2 — New helpers not exposed through SDK barrel: createBedrockServiceTierWrapper and resolveBedrockServiceTier are exported from bedrock-stream-wrappers.ts but not re-exported through src/plugin-sdk/provider-stream-shared.ts, causing the extension to re-implement both the constant list and the resolver.

Confidence Score: 3/5

Not safe to merge as-is — the extension path can inject serviceTier into non-bedrock-converse API calls, causing Bedrock validation errors for affected model types.

A P1 behavioral divergence between the two implementation paths means the extension's service-tier wrapping can produce request failures when a Bedrock model uses a non-converse API. The pi-embedded-runner path is correct; the extension path is missing the same guard. This needs to be fixed before the feature is reliable across all Bedrock model configurations.

extensions/amazon-bedrock/register.sync.runtime.ts — the createServiceTierWrapStreamFn inner wrapper needs the model.api !== "bedrock-converse-stream" guard, and the local reimplementations of BEDROCK_SERVICE_TIER_VALUES/resolveBedrockServiceTier should ideally be replaced once the SDK barrel is updated.

This is a comment left during a code review.
Path: extensions/amazon-bedrock/register.sync.runtime.ts
Line: 50-56

Comment:
**Missing `model.api` guard before injecting `serviceTier`**

The extension's service-tier wrapper calls `streamWithPayloadPatch` for every model, but the parallel implementation in `bedrock-stream-wrappers.ts` explicitly skips the patch when `model.api !== "bedrock-converse-stream"`. Without that guard, `serviceTier` is injected into the `onPayload` callback regardless of API type. If a Bedrock model routes through a non-converse API (e.g. an Anthropic-family model using a different API style), the extra field is sent to an endpoint that doesn't expect it and Bedrock will reject the request with a validation error.

`createBedrockServiceTierWrapper` in `bedrock-stream-wrappers.ts` already has this guard:
```typescript
if (model.api !== "bedrock-converse-stream") {
  return underlying(model, context, options);
}
```
The same check should be added here:
```suggestion
    return (model, context, options) => {
      if (model.api !== "bedrock-converse-stream") {
        return inner(model, context, options);
      }
      return streamWithPayloadPatch(inner, model, context, options, (payload) => {
        if (payload.serviceTier === undefined) {
          payload.serviceTier = { type: serviceTier };
        }
      });
    };
```

How can I resolve this? If you propose a fix, please make it concise.

---

This is a comment left during a code review.
Path: extensions/amazon-bedrock/register.sync.runtime.ts
Line: 25-57

Comment:
**Duplicated logic not exposed through SDK barrel**

`BEDROCK_SERVICE_TIER_VALUES`, `resolveBedrockServiceTier`, and the service-tier patch logic are all re-implemented here but were just added (and exported) in `bedrock-stream-wrappers.ts`. The `provider-stream-shared.ts` SDK barrel already re-exports other helpers from that same file (`createBedrockNoCacheWrapper`, `isAnthropicBedrockModel`, `streamWithPayloadPatch`), but the new `createBedrockServiceTierWrapper` and `resolveBedrockServiceTier` exports were not added to the barrel.

Adding those two exports to `src/plugin-sdk/provider-stream-shared.ts` would let the extension replace its local reimplementations with:
```typescript
import {
  createBedrockServiceTierWrapper,
  resolveBedrockServiceTier,
} from "openclaw/plugin-sdk/provider-stream-shared";
```
…and collapse the `createServiceTierWrapStreamFn` factory down to a direct call at the `wrapStreamFn` call site.

How can I resolve this? If you propose a fix, please make it concise.

_{Reviews (1): Last reviewed commit: "feat(amazon-bedrock): support service_ti..." | Re-trigger Greptile}

Addressing Greptile Review Comments

P1 — Missing model.api guard: Already present in the code — the createServiceTierWrapStreamFn factory included the model.api !== "bedrock-converse-stream" check before the crash, matching the guard in bedrock-stream-wrappers.ts.

P2 — Duplicated logic not exposed through SDK barrel: Fixed in commit 53ed819.

• Added createBedrockServiceTierWrapper and resolveBedrockServiceTier exports to src/plugin-sdk/provider-stream-shared.ts
• Removed local reimplementations (BEDROCK_SERVICE_TIER_VALUES, resolveBedrockServiceTier, createServiceTierWrapStreamFn) from the extension
• Replaced the factory pattern with a direct createBedrockServiceTierWrapper(wrapped, serviceTier) call at the wrapStreamFn site

Net result: -37 lines, +8 lines. The extension now imports shared helpers from the SDK barrel instead of duplicating them.

Codex review: needs changes before merge.

Summary
The PR adds Amazon Bedrock serviceTier/service_tier support through a Bedrock stream wrapper, SDK re-export, provider tests, docs, and changelog entry.

Reproducibility: not applicable. as a bug reproduction; this is a feature PR for a new Bedrock request parameter. Current main lacks the feature, while PR source inspection and the uploaded OpenClaw/AWS screenshots provide a high-confidence verification path once the branch is rebased.

Real behavior proof
Sufficient (screenshot): The PR body includes after-fix screenshots showing both an OpenClaw Bedrock model invocation and AWS CloudWatch metrics with ServiceTier: flex.

Next step before merge
Safe repair candidate: the remaining blockers are mechanical rebase/conflict resolution and generated SDK baseline follow-through, with no security or product-design blocker found.

Security
Cleared: The diff is limited to Bedrock request shaping, tests, docs, changelog, and SDK exports, with no new dependencies, workflows, secrets handling, install scripts, or artifact downloads.

Review findings

• [P2] Refresh the Plugin SDK API baseline — src/plugin-sdk/provider-stream-shared.ts:640-642
• [P2] Rebase the branch before merge — CHANGELOG.md:13

Unit tests for expected behavior added based on previous Codex comments.

Real behavior proof (required for external PRs)

• Behavior or issue addressed: pass service_tier parameter to amazon-bedrock models
• Real environment tested:
  • AWS Amazon Linux (both arm64 and x86_64) via EC2 host IAM policy; nodejs v22.22.2
  • Apple MacOS M3 via Bedrock bearer token; nodejs v25.9.0
  • Fedora 43 Linux desktop using ~/.aws/credentials; nodejs v22.22.0
  • Systemd quadlet container (Fedora 43 host, bookworm-slim container) via Bedrock bearer token.
• Exact steps or command run after this patch:
  • Restart gateway
  • Ensure agents.defaults.params.serviceTier="flex"
  • Ask agent to spawn a subagent running amazon-bedrock/moonshotai.kimi-k2.5
  • Tested with a model that does not support flex service tier.
    • Behavior is as documented.
    • Ran with model-specific override for serviceTier="default" to ensure individual models could be overridden.
  • Check AWS CloudWatch for amazon-bedrock/moonshotai.kimi-k2.5 model invokation with serviceTier=flex.
  • Also have been running this in production for a month now.
• Evidence after fix: see attached screenshots.
  • Agent starts subagent with model.
  • AWS CloudWatch shows model invocation with serviceTier=flex. April Bedrock bill was lower.
  • What was not tested: I did not test all Amazon Bedrock models. Only the limited subset that I use.

Model invocation via subagent on OpenClaw.

serviceTier=flex passed to Amazon Bedrock model invocation.

Landed via rebase onto main.

• Scoped tests: bunx pnpm test extensions/amazon-bedrock/index.test.ts; bunx pnpm exec oxfmt --check --threads=1 CHANGELOG.md docs/providers/bedrock.md extensions/amazon-bedrock/index.test.ts extensions/amazon-bedrock/register.sync.runtime.ts; OPENCLAW_LOCAL_CHECK=1 OPENCLAW_LOCAL_CHECK_MODE=throttled bunx pnpm check:changed
• Changelog: CHANGELOG.md updated
• Land commit: 84828a5
• Merge commit: 0ef1f36

Thanks @mobilinkd!