mcpField
L
logfire-codex-connection

logfire-codex-connection

github.com/pydanticAgent workflows14590 installsUpdated 2w ago
Repository

About logfire-codex-connection

A Codex skill for connecting to, checking, or disconnecting Logfire. It treats MCP access and session recording as separate choices and distinguishes configuration from evidence that data arrived.

Key features

  1. 01Connect, check, or disconnect
  2. 02Choose querying or session recording
  3. 03Separate MCP access from capture
  4. 04Report delivery evidence

Use cases

  1. 01Set up Logfire for Codex
  2. 02Check connection status without repairs
  3. 03End Logfire access or recording

MCP support

Guides setup of Logfire MCP access while keeping it independent from Codex session recording. A status check does not authorize installation, authentication, or repairs.

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/pydantic/skills --skill logfire-codex-connection

After installing, type/logfire-codex-connectionin Claude Code to confirm it loaded.

Bundled files

References and scripts installed along with SKILL.md.

references/
connect.md
mcp.md
status.md

Details

From the project README

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.

Comments

Markdown supported