logfire-coding-agents
/logfire-coding-agents
Connect Claude Code or Codex itself to Logfire telemetry, or route a coding agent's model requests through Pydantic AI Gateway. Use for coding-session recording, capture policies, Gateway agent configuration, temporary proxy launches, status, or removal. Not for instrumenting an application or routing an application's model client.
- Author
- pydantic ↗
- Repository
- skills ↗
- Licence
- MIT
- Last repository change
- 16.10.2026
Assessment and security
- Files in this package
- 5
- Scripts
- 0
- HTML comments
- 0
- URLs in SKILL.md
- 0
No signals detected. Repository changed on 16.10.2026, without references to retired models or APIs.
MIT, open: use and modify while retaining author attribution.
What it does and when to use it
Connect Claude Code or Codex itself to Logfire telemetry, or route a coding agent's model requests through Pydantic AI Gateway. Use for coding-session recording, capture policies, Gateway agent configuration, temporary proxy launches, status, or removal. Not for instrumenting an application or routing an application's model client.
Original author description
Connect Claude Code or Codex itself to Logfire telemetry, or route a coding agent's model requests through Pydantic AI Gateway. Use for coding-session recording, capture policies, Gateway agent configuration, temporary proxy launches, status, or removal. Not for instrumenting an application or routing an application's model client.
How it works
- Confirm the destination
- Choose the requested workflow
SKILL.md preview
--- name: logfire-coding-agents description: Connect Claude Code or Codex itself to Logfire telemetry, or route a coding agent's model requests through Pydantic AI Gateway. Use for coding-session recording, capture policies, Gateway agent configuration, temporary proxy launches, status, or removal. Not for instrumenting an application or routing an application's model client. --- # Connect Coding Agents to Logfire Use the exact Rust CLI executable supplied by the handoff for every operation; examples call it `logfire-cli`. Preserve its region, organization, project, and data directory. Do not replace it with a package launcher or install a second exporter by hand. These commands require `--beta`. Without a prepared handoff, follow [native CLI connection](./references/connection.md). The same skill is distributed in the Logfire plugin; plugin installation alone does not supply a CLI session, project credential, or capture consent. Distinguish three independent capabilities: - **Telemetry:** record the coding agent's activity in the selected project. - **Gateway:** route the agent's model requests through the organization's paid Gateway access. This does not enable telemetry. - **MCP:** let the agent query Logfire. MCP OAuth is owned by the agent's MCP client; CLI login or telemetry setup does not authenticate that client. Honor the user's stated goal and agent. Ask only for missing choices; do not enable all three because the user asked to connect one. For application code, use [instrumentation](../logfire-instrumentation/SKILL.md) or the [application Gateway skill](../logfire-gateway/SKILL.md) instead. ## Confirm the destination A prepared handoff already selected the origin, organization, project, and local SDK credential: reuse those without repeating account commands or creating another write token. Otherwise follow the shared [connection reference](./references/connection.md). Do not guess another project when access fails. Keep account credentials out of prompts, logs, and child environments. Leave credential storage and settings writes to the CLI. If a saved helper will invoke this executable later, use a persistent installed path, not a temporary build or cache directory. ## Choose the requested workflow - To observe Claude Code or Codex, read [session telemetry](./references/telemetry.md). - To route coding-agent inference, read [Gateway routing](./references/gateway.md). - For both, configure telemetry first, then Gateway. Preserve each integration's destination and settings independently. Do not launch another setup agent or a nested interactive coding session just to configure this one. Explain any required restart. Finish with the configured agent, destination, capture or routing choice, observed verification result, and one next action. Configuration is not proof of ingestion or inference.
Files in this package (5)
- SKILL.md 3 KB
- references/application-gateway.md 2 KB
- references/connection.md 4 KB
- references/gateway.md 4 KB
- references/telemetry.md 5 KB
Versions
The database has no other skills named logfire-coding-agents.
Identical content appears in 1 other GitHub folders. We show one copy with the highest score.
Database snapshot: 13.11.2026 · package version b16db7714f6d (SHA-256 digest of the entire package)
Downloads in the last 30 days: 0 · ranking
Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.
Similar skills
- 95logfire-gateway
Configure an application's model calls to use the Pydantic AI Gateway. Use when the user asks to route application inference through Gateway, connect a Gateway key, or add a Gateway provider snippet. This does not configure or instrument coding agents. - 86logfire-codex-connection
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. - 100pydantic-ai
Pydantic AI Python agent framework. Covers typed tools, model providers, evals, MCP, UI adapters, and observability. Use when building Python AI agents with Pydantic AI, configuring model providers, implementing typed tools/dependencies, running evals, or integrating MCP… - 100instrumentation
Add Pydantic Logfire observability to applications. Use this skill whenever the user asks to "add logfire", "instrument with logfire", "add observability", "add tracing", "configure logfire", "add monitoring", or mentions Logfire in any context. Supports Python,… - 98model-gateway
Set up, update, or diagnose the local ChatGPT/Codex gateway for Claude Code's /model picker. Use for gateway setup, login, model visibility, routing, or failures. - 100procept-lite
Turn exported agent logs (LangSmith, LangChain, Pydantic Logfire, OpenTelemetry, GCP, AWS, Azure) into cig.html, a failure network over errors, cost, latency and score, plus scorecard.html, a one-page scorecard, in one action, with every stage checked against the real data by a…