Generated banner for Logfire Codex Connection
Generated logo for Logfire Codex Connection

Logfire Codex Connection

PydanticOfficialPublished by Pydantic

  • Skill
  • Tool integration
  • Automation and integrations
  • MIT
  • No issues found

From the author

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.
— the description by Pydantic

AutoGineer summary

Written by AutoGineer from the skill’s own files, not by the author

The logfire-codex-connection skill provides a structured interface for managing the integration between Codex and Logfire. It allows users to configure MCP access for querying Logfire and set up session recording for telemetry, all while adhering to security best practices regarding credential handling and configuration management. The skill acts as a bridge to the native Codex CLI and configuration APIs, ensuring that users can maintain their observability setup without manual file editing or complex CLI workflows.

What it does

  • Connects Codex to Logfire for MCP-based querying and session telemetry.
  • Checks the current status of Logfire connections and recording configurations.
  • Disables or removes existing Logfire connections and stops session recording.
  • Supports regional configurations including US, EU, and self-hosted endpoints.
  • Handles the enabling and disabling of the bundled Logfire MCP server.
  • Provides clear reporting on MCP access, capture modes, and delivery status.

When to use it

  • When you need to enable Logfire telemetry for your Codex sessions.
  • When you want to query Logfire data directly from within the Codex environment.
  • When you need to switch between US, EU, or self-hosted Logfire instances.
  • When you need to verify if your current session is being recorded or if MCP is active.
  • When you need to disconnect Logfire from Codex to stop data collection.

Advantages

  • Simplifies complex configuration tasks into guided, safe steps.
  • Protects sensitive credentials by avoiding manual file inspection or printing.
  • Maintains clear separation between MCP querying and session recording.
  • Provides consistent status reporting without requiring manual CLI intervention.
  • Respects existing application instrumentation and model provider settings.

Usage examples

“Connect my Codex to Logfire for session recording.”
The agent will guide you through selecting a capture mode (full, messages-only, or metadata-only) and verify the connection status.
“Check if my Codex session is currently being recorded by Logfire.”
The agent will inspect the current configuration and report the active capture mode and connection status.
“Switch my Logfire connection to the EU region.”
The agent will help you disable the current US connection and configure the EU endpoint via native Codex controls.
“Stop recording my Codex sessions.”
The agent will execute the necessary commands to disable session recording while keeping the MCP connection intact if desired.

Install

  1. Download the skill as a ZIP:

    https://mp-staging.autogineer.com/agent-skills/pydantic/logfire-codex-connection/download
  2. Unzip it into the cross-client skills folder of your project:

    mkdir -p .agents/skills && unzip logfire-codex-connection.zip -d .agents/skills

Documentation by Pydantic

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.

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.

Files

Requirements and compatibility

Works with: Claude Code, Claude apps, OpenAI Codex, GitHub Copilot, Cursor, Gemini CLI, Kiro, OpenCode, Goose, Amp, Roo Code, JetBrains Junie, Factory Droid, Devin (ex-Windsurf), Mistral Vibe, OpenHands, Letta

“Works with” means the tool reads the open Agent Skills format; a skill written for one tool may use features others lack.

Security

No issues found by our static scan· No issues found

A static scan is not a guarantee. Skills are third-party content: review a skill before you let an agent use it.

Attribution and licence

Published by
Pydantic
Publisher
Pydantic (Official)
Source
pydantic/skills · plugins/logfire/skills/logfire-codex-connection · commit 98f591c
Licence
MIT License (redistribution allowed)
  • LICENSE (added by AutoGineer from LICENSE)
  • ATTRIBUTION.md (written by AutoGineer)
Synced

AutoGineer is not affiliated with or endorsed by Pydantic.

Download ZIP

The ZIP holds the skill’s files, its licence files and an ATTRIBUTION.md. Download logfire-codex-connection.zip