Logfire CLI

Set up Pydantic Logfire, query your telemetry, and manage projects and tokens without leaving the terminal.

Getting started · Install · User guide · Develop the CLI

Get started

Install the native CLI with uv:

uv tool install logfire-cli
logfire --version

Want to try it first? Run either command without installing anything:

uvx logfire-cli --help
npx logfire-cli --help

You can also install it with npm:

npm install --global logfire-cli
logfire --version

New to Logfire?

From your application's directory, choose the organization and first project names you want:

logfire --region us signup --org acme --project my-app

The CLI opens a short-lived signup page in your browser. After you approve the signup, it creates the organization and project and connects the current directory to that project. Use --region eu if your Logfire account belongs in the EU region.

Already have a Logfire account?

Sign in, then create or choose a project interactively:

logfire --region us auth --org acme
logfire --org acme init

Browser credentials stay in your operating system's credential store. init writes the project's SDK credential to .logfire/logfire_credentials.json and keeps it out of version control.

Check it and do something useful

logfire --org acme project current
logfire --org acme wizard
logfire --org acme mcp query run 'SELECT message FROM records LIMIT 20' --project my-app

• project current verifies which Logfire project this directory uses.
• project open opens that validated project, while --no-open prints its URL.
• wizard prepares the account and project, then asks an installed Codex, Claude Code, GitHub Copilot, Cursor, or Google Antigravity agent to instrument and verify your application.
• mcp query run queries your Logfire data through the hosted MCP server.

For the complete walkthrough, including existing-project and automation flows, see Getting started.

Common jobs

| I want to… | Command | Guide | | --- | --- | --- | | Create my Logfire account and first project | logfire signup | Signup | | Sign in to an existing account | logfire auth | Authentication | | Connect this directory to a project | logfire init | Project setup | | Add application instrumentation | logfire wizard | Agent-assisted setup | | Try the beta AI Gateway integration | logfire --beta agent gateway or logfire --beta agent proxy launch | Gateway setup | | Run Python with automatic instrumentation | logfire run | Run Python | | Query traces and logs | logfire mcp query | MCP | | Open or inspect the current project | logfire project | Project | | Create a project read or write token | logfire token | Tokens | | Diagnose credentials or local setup | logfire doctor | Doctor |

The CLI also includes beta typed Platform API commands, safe generic MCP calls, agent skills, and beta Codex telemetry setup. The user guide lists every command by task.

Help that starts small

logfire --help
logfire help signup
logfire help init
logfire help mcp query

Short help keeps common choices visible. logfire help <command> adds examples, effects, and advanced options.

For scripts and coding agents, add --no-input and request --output json or --output jsonl instead of parsing human-readable output. See Output contracts.

Credentials stay in the right place

• Browser OAuth credentials are scoped to one Logfire origin and organization and stored in the operating system credential store.
• Project write credentials stay with the local project under .logfire/.
• Coding agents launched by setup or bundled skills do not inherit Logfire account credentials from the CLI's environment.
• Newly created secrets are printed once only when a token-creation command is explicitly used.
• --org always means the real organization name shown in Logfire.

See Authentication for multiple organizations, headless API keys, logout, and credential precedence.

Installation and updates

PyPI provides native binaries for all 17 supported targets. npm covers the five common macOS, GNU/Linux, and Windows combinations. Repository readers can also download every prebuilt archive, plus checksums and verification evidence, from GitHub Releases. Until this repository is public, that GitHub route requires Pydantic repository access.

See Installation for supported platforms, one-off use, updates, and shell completions.

Contributing and security

Developing the CLI itself? Start with the developer guide and contribution guide. Report vulnerabilities through the private process in SECURITY.md, never through a public issue.

Logfire CLI is released under the MIT License.