How long does the integration take?

Change one base URL in an OpenAI-compatible client, or install the Python or TypeScript SDK; the quickstart routes a first request in a few minutes.

Will this lock us into another vendor?

No. The router is Apache-2.0 open source, your provider keys stay yours, and the API is OpenAI-compatible, so leaving is a change of base URL.

What happens when a provider fails?

The router falls back to the next model your policy allows and records the fallback in the trace, so an outage costs a retry, not an incident.

logfire-codex-connection - Skill

Name: logfire-codex-connection
Author: pydantic

Imported from pydantic/skills (plugins/logfire/skills/logfire-codex-connection/SKILL.md). Install upstream with npx skills add pydantic/skills --skill logfire-codex-connection. Copyright stays with the author.

Connect Codex to Logfire

Help the user connect, check status, or disconnect without making them run a setup checklist. Honor the requested operation; a status request never grants permission to install, authenticate, or repair anything.

For connection, ask only if missing: "Would you like to query Logfire, record your Codex sessions, or both?" MCP access and recording are independent. Do not require CLI login for working MCP, or MCP read access to record sessions.

Connect: follow connection setup.
Status: follow status and removal.
Disconnect: follow status and removal.

Resolve bundled scripts relative to this installed skill directory. The runtime helper is ../../scripts/agent_runtime.py --agent codex; the explicit agent selects Codex's separate runtime and project credential directory. Quote paths as single arguments. Do not assume CLAUDE_PLUGIN_ROOT exists in Codex.

Leave telemetry configuration and exporter installation to the native Logfire CLI. Do not add custom transcript hooks, copy credentials, open secret-bearing Codex/exporter configuration files, or start a nested coding session for setup. Keep existing application instrumentation, model providers, and Gateway routing unchanged. Plugin installation is not consent to session capture.

Finish with MCP access, capture mode/destination, and delivery evidence as separate facts. Give one next action. "Configured" does not mean data arrived.

Install logfire-codex-connection and it becomes one more candidate the router can pick - when it fits.

A listing is a routing target with a manifest: what it does, which domains it covers, what it costs and who publishes it. Once installed it sits beside your own models and tools, is scored like any other candidate for each request, and shows up in the trace when it wins. Ratings come from workspaces that installed it, one per account.

{ "ocm": "1", "id": "pydantic-skills-logfire-codex-connection", "kind": "skill", "name": "logfire-codex-connection", "description": "Connect Codex itself to Logfire, check connection status, or stop session recording. Use for this plugin's MCP access and optional native Codex telemetry, not application instrumentation or AI Gateway routing.", "publisher": "pydantic", "version": "1.0.0", "capabilities": { "domains": [ "customer_support", "data_analysis" ], "tags": [ "skill-md", "skills-sh" ], "languages": [ "en" ] }, "quality_prior": 0.6, "examples": [ "Connect Codex itself to Logfire, check connection status, or stop session recording. Use for this plugin's MCP access and optional native Codex telemetry, not application instrumentation or AI Gateway routing." ], "primary": false, "metadata": { "source": { "provider": "skills.sh", "repository": "https://github.com/pydantic/skills", "path": "plugins/logfire/skills/logfire-codex-connection/SKILL.md", "ref": "HEAD", "url": "https://github.com/pydantic/skills/blob/HEAD/plugins/logfire/skills/logfire-codex-connection/SKILL.md", "key": "pydantic/skills/plugins/logfire/skills/logfire-codex-connection/SKILL.md" } }, "instructions": "# Connect Codex to Logfire\n\nHelp the user connect, check status, or disconnect without making them run a\nsetup checklist. Honor the requested operation; a status request never grants\npermission to install, authenticate, or repair anything.\n\nFor connection, ask only if missing: \"Would you like to query Logfire, record\nyour Codex sessions, or both?\" MCP access and recording are independent. Do not\nrequire CLI login for working MCP, or MCP read access to record sessions.\n\n- **Connect:** follow [connection setup](references/connect.md).\n- **Status:** follow [status and removal](references/status.m", "cost": { "context_tokens": 384 } }

logfire-codex-connection

About

Connect Codex to Logfire

Use it

Install logfire-codex-connection and it becomes one more candidate the router can pick - when it fits.

What it costs to adopt - in engineering time.

One base URL

No vendor lock-in

Failover built in

Manifest

Reviews