Problem

OpenClaw's gateway accepts arbitrary params in agent/model config (agents.defaults.params), but createStreamFnWithExtraParams has a hardcoded allowlist of fields that get passed to the API request:

• temperature
• maxTokens
• transport
• openaiWsWarmup
• cachedContent/cached_content
• cacheRetention

All other fields — including the user parameter — are silently dropped. This means setting "user": "mission-control" in openclaw.json does nothing.

Why it matters

Both OpenRouter and OpenAI accept a user field in their chat completion requests for:

• Per-request attribution — OpenRouter's broadcast feature uses this for cost-per-project tracking
• Abuse detection — Both providers use it for rate limiting and abuse patterns
• Request correlation — Enables users to correlate their application's request IDs with provider logs

Without user passthrough, OpenClaw users cannot use these provider features at all.

Proposed solution

Use streamWithPayloadPatch (the same pattern already used for parallelToolCalls) to inject the user field into the API request body when it's defined in effectiveExtraParams.

Config usage:

{
  "agents": {
    "defaults": {
      "params": {
        "user": "mission-control"
      }
    }
  }
}

The user field would then appear in every API request, enabling OpenRouter broadcast attribution and similar provider features.

Scope

• src/agents/pi-embedded-runner/extra-params.ts — single file change
• No API changes, no breaking changes, no config schema changes
• Follows existing pattern (createParallelToolCallsWrapper uses streamWithPayloadPatch)
• Only applies when user is set in config — zero overhead otherwise

Related

PR: #64748 (incoming)

Notes

This handles the static user case. Dynamic fields (e.g., injecting graph/task IDs per-request) would need a separate mechanism — potentially a gateway hook that evaluates a template at request time.