logfire-gateway
Configure an Application with Pydantic AI Gateway
For observing or routing Claude Code/Codex itself, use coding-agent setup instead. Keep this application workflow separate from coding-session recording and provider setup.
Preserve the user's confirmed project, region, provider, and existing credential mechanism. An existing application Gateway key needs no CLI login or SDK write token. To create a key through the CLI, follow the CLI Gateway credential procedure. Use the UI's Gateway Connect flow when CLI access is unavailable.
Use this skill for model traffic, provider routing, and Gateway credentials. It
is separate from logfire-instrumentation: a Logfire write token sends
telemetry, while a Gateway key authorizes model requests. Do not substitute one
for the other. Do not configure coding-agent providers, telemetry, or MCP integrations.
A prepared setup handoff may already identify the exact project and credentials. Reuse it rather than repeating authentication or selecting another project.