Goose
Point Goose at FluxRouter through its OpenAI provider by splitting the host and base path.
Goose talks to FluxRouter through its OpenAI provider, which hits the /v1/chat/completions endpoint. Your Flux key is the only credential it needs.
For abilities as well as models, such as reading pages and making images, add the Flux tools server with the same key if your version of the tool supports remote MCP servers.
Manual config
Goose splits the host from the base path, so the /v1 lives on the base path rather than the host. Set these environment variables:
export OPENAI_HOST=https://api.fluxrouter.ai
export OPENAI_BASE_PATH=v1/chat/completions
export OPENAI_API_KEY=sk-YOUR-FLUX-KEY
To persist the provider and model, write ~/.config/goose/config.yaml:
GOOSE_PROVIDER: openai
GOOSE_MODEL: flux-auto
Test it
Run goose session and send a prompt. A reply confirms the connection. Check your FluxRouter dashboard to confirm the request landed.
Notes
flux-auto is the default and routes each request for you. If you want to pin a single lane, set GOOSE_MODEL to flux-fast, flux-standard, or flux-reasoning.
The host plus base-path split is unusual. The host carries no /v1, and the base path carries it; keep them separate or Goose will build the wrong URL.