openclaw - 💡(How to fix) Fix OpenRouter calls stamped as "pi" instead of "OpenClaw" — pi-coding-agent SDK overrides attribution module [2 comments, 2 participants]

Summary

OpenClaw ships a provider-attribution module that explicitly stamps X-OpenRouter-Title: OpenClaw on outbound OpenRouter requests and even flags those headers as protected from caller override. But on the wire, every OpenRouter request from openclaw-gateway is stamped as pi because the bundled @mariozechner/pi-coding-agent SDK injects its own attribution headers downstream of the policy layer.

Net effect: OpenClaw deployments show up as Mario Zechner's pi project on the OpenRouter app dashboard, not as OpenClaw.

Versions

• OpenClaw: 2026.4.23
• @mariozechner/pi-coding-agent: 0.70.0

Evidence

/app/dist/provider-attribution-DL72eDFq.js (OpenClaw build):

const OPENCLAW_ATTRIBUTION_PRODUCT = "OpenClaw";
function buildOpenRouterAttributionPolicy(env = process.env) {
  // ...
  return {
    headers: {
      "HTTP-Referer": "https://openclaw.ai",
      "X-OpenRouter-Title": identity.product,   // → "OpenClaw"
      "X-OpenRouter-Categories": "cli-agent",
    },
  };
}

/app/dist/provider-request-config-DhoLmkrG.js even marks these as protected so caller headers can't override them:

const protectedAttributionKeys = new Set(
  Object.keys(policy.attributionHeaders ?? {}).map(/* ... */)
);

But /app/node_modules/@mariozechner/pi-coding-agent/dist/core/sdk.js does this:

function getOpenRouterAttributionHeaders(model, settingsManager) {
  if (!isInstallTelemetryEnabled(settingsManager)) return undefined;
  if (model.provider !== "openrouter" &&
      !model.baseUrl.includes("openrouter.ai")) return undefined;
  return {
    "HTTP-Referer": "https://pi.dev",
    "X-OpenRouter-Title": "pi",
    "X-OpenRouter-Categories": "cli-agent",
  };
}

The pi-coding-agent SDK applies these outside OpenClaw's attribution-policy plumbing, so they win on the wire.

Reproduction

1. Configure openclaw.json with an openrouter provider + any model (e.g. openrouter/xiaomi/mimo-v2-flash).
2. Run any agent task.
3. Check the OpenRouter dashboard → Activity → App column. Result: pi, not OpenClaw.

Suggested fixes

1. Disable pi-coding-agent's attribution headers when running inside OpenClaw — set PI_TELEMETRY=0 in the gateway's env (the SDK already reads this env var to gate getOpenRouterAttributionHeaders). That returns undefined and lets OpenClaw's own attribution-policy layer apply its X-OpenRouter-Title: OpenClaw headers.
2. Or override getOpenRouterAttributionHeaders at the integration point so OpenClaw's policy headers take precedence on OpenRouter requests.

Option (1) is a one-line env change.