proxy --provider openrouter ignores ANTHROPIC_PROXY_BASE_URL (openrouterBaseUrl not passed)

Summary

agentic-flow proxy --provider openrouter constructs AnthropicToOpenRouterProxy without openrouterBaseUrl, so the standalone proxy can only ever talk to https://openrouter.ai/api/v1. Every other construction site in the package passes it, which makes this look like an omission rather than a decision.

Reproduce

npm i -g agentic-flow@2.1.2
OPENROUTER_API_KEY=placeholder \
ANTHROPIC_PROXY_BASE_URL=http://localhost:11434/v1 \
  agentic-flow proxy --provider openrouter --port 3801 --model llama3.2:3b

Actual banner:

   OpenRouter Base URL: https://openrouter.ai/api/v1

Expected: http://localhost:11434/v1, i.e. the value of ANTHROPIC_PROXY_BASE_URL, as the other two call sites already honour.

Root cause

Three construction sites, one inconsistent:

// dist/cli-proxy.js:583-586
const proxy = new AnthropicToOpenRouterProxy({
    openrouterApiKey: apiKey,
    defaultModel: finalModel
});

The constructor already defaults to https://openrouter.ai/api/v1 when the field is absent, so passing it through is non-breaking.

Impact

The proxy subcommand is the documented way to put an Anthropic-shaped endpoint in front of Claude Code / Cursor. As written it cannot target a self-hosted or local OpenAI-compatible backend (Ollama, vLLM, LM Studio, LiteLLM, an internal gateway) — which is the main reason to run a local proxy at all. The workaround is to bypass the CLI and run node dist/proxy/anthropic-to-openrouter.js directly, since only its own entrypoint reads the variable.

Suggested fix

  const proxy = new AnthropicToOpenRouterProxy({
      openrouterApiKey: apiKey,
+     openrouterBaseUrl: process.env.ANTHROPIC_PROXY_BASE_URL,
      defaultModel: finalModel
  });

Verified locally against 2.1.2: with that one line, the banner reports the local /v1 and requests reach it. Happy to open a PR.

Environment

agentic-flow@2.1.2 · node v22.23.0 · npm 10.9.8 · macOS (Darwin 25.6.0)

Related: #224 (ollama provider — same underlying capability, reached differently)

Start at dist/cli-proxy.js:584 and compare the proxy subcommand with the other construction sites listed in the issue. Run the provided ANTHROPIC_PROXY_BASE_URL reproduction after the change; done means the banner shows the configured URL and requests reach that endpoint.