request-logger: Pi + Openrouter

[crywolf]

Is it possible to add Openrouter provider?

I followed README.md and tried to use Custom base URL but was not able to make it work with Pi agent. Models.json is getting ignored, because I am logged to Openrouter.

Thank you.

[mattpocock]

Triage: this should mostly already be possible via the Custom base URL flow (request-logger's wizard) added for #12/#15 and threaded through to Pi in #22 — OpenRouter's API is OpenAI-compatible, so picking Pi → Custom base URL → OpenAI-compatible should generate a ~/.pi/agent/models.json override that points Pi's openai (or anthropic) provider entry at the proxy, with a discovered model ID baked in.

My best guess at what's going wrong: "logged in to OpenRouter" suggests you've authenticated Pi against OpenRouter directly (e.g. pi auth login), which likely makes Pi active on its own built-in openrouter provider key. The override this tool writes only replaces the openai/anthropic provider keys (see piModels() in request-logger/agents.ts) — it never touches openrouter — so if Pi is defaulting to its native OpenRouter provider, the override in models.json would indeed sit there unused, which matches "getting ignored."

To confirm and fix this properly, could you share:

1. The exact command you ran through the wizard (which agent/provider/wire-format choices you picked).
2. The contents of ~/.pi/agent/models.json after running it.
3. Whether "logged in to OpenRouter" means you ran a Pi auth/login command for OpenRouter specifically, or something else (env var, existing config).
4. The exact error or behavior you saw (does Pi start? does the request-logger log anything at all?).

Once we know which provider key Pi is actually resolving to at runtime, this is either a doc/UX fix (make Pi log out of any conflicting native provider before using Custom base URL) or a real gap (need to let the override target openrouter directly).

[crywolf]

1:

$ npm run request-logger -- --force

> request-logger
> tsx request-logger/proxy.ts --force

┌   request-logger
│
◇  Which coding agent do you use?
│  Pi
│
◇  Which model provider do you use with Pi?
│  Custom base URL
│
◇  What's the base URL of the model server you want to log?
│  https://openrouter.ai/api
│
◇  Which wire format does it speak?
│  Not sure — show me the raw JSON
[request-logger] Could not discover any models; enter a model ID manually.
│
◇  What's the model ID?
│  deepseek/deepseek-v4-pro

------------------------------------------------------------------------
  Agent      Pi (Custom base URL)
  Listening  http://localhost:8787
  Forwards   https://openrouter.ai
  Logs       ai-coding-crash-course/request-logger/logs
------------------------------------------------------------------------

  Put this in ~/.pi/agent/models.json:

      {
        "providers": {
          "openai": {
            "baseUrl": "http://localhost:8787/v1",
            "models": [{ "id": "deepseek/deepseek-v4-pro" }]
          }
        }
      }

  Then run your agent in another terminal with:

      pi

  Note: This models.json entry replaces Pi's built-in "openai" model
        catalogue with the one model you selected, since Pi's built-in
        model names almost never exist on a custom server.

  Note: You picked "not sure" for the wire format, so every capture falls
        back to a raw JSON dump instead of a fully rendered one. That is
        not broken — it is just less readable. Run with --force and pick a
        format once you know it, and the readable renderer takes over.

  Using a different agent now? Run: npm run request-logger -- --force
  Press Ctrl+C to stop logging.
------------------------------------------------------------------------

2:

{
  "providers": {
    "openai": {
      "baseUrl": "http://localhost:8787/v1",
      "models": [{ "id": "deepseek/deepseek-v4-pro" }]
    }
  }
}

3: Yes, I am logged to OpenRouter in Pi by running /login command

4: Pi starts normally, nothing is logged, models.json is ignored, "defaultProvider": "openrouter" from settings.json is used instead