logfire-cli 0.1.5__py3-none-win32.whl

logfire_cli/__init__.py

@@ -0,0 +1,14 @@
+"""Run the native Logfire CLI installed in this wheel."""
+
+from __future__ import annotations
+
+import os
+import sys
+from pathlib import Path
+
+
+def main() -> None:
+    """Replace this process with the bundled, provenance-verified CLI."""
+    binary = Path(__file__).with_name("bin") / ("logfire.exe" if os.name == "nt" else "logfire")
+    os.environ["LOGFIRE_CLI_DISTRIBUTION"] = "pypi"
+    os.execv(binary, [str(binary), *sys.argv[1:]])

logfire_cli-0.1.5.dist-info/METADATA

@@ -0,0 +1,181 @@
+Metadata-Version: 2.4
+Name: logfire-cli
+Version: 0.1.5
+Summary: The command-line interface for Pydantic Logfire.
+Home-page: https://pydantic.dev/logfire
+Project-URL: Documentation, https://pydantic.dev/docs/logfire/
+Project-URL: Source, https://github.com/pydantic/logfire-cli
+License-Expression: MIT
+License-File: LICENSE
+Requires-Python: >=3.9
+Description-Content-Type: text/markdown; charset=UTF-8
+
+# Logfire CLI
+
+The Rust command-line interface for [Pydantic Logfire](https://pydantic.dev/logfire).
+Sign in, query your traces and logs, manage projects and tokens, and connect your
+coding agent to Logfire from the terminal.
+
+This package installs the native CLI, not the Python instrumentation SDK.
+Install an application SDK separately to send telemetry; see the
+[Logfire documentation](https://pydantic.dev/docs/logfire/).
+
+## Install
+
+Try it with [uv](https://docs.astral.sh/uv/):
+
+```bash
+uvx logfire-cli --help
+```
+
+Install it as an isolated command-line tool:
+
+```bash
+uv tool install logfire-cli
+logfire --help
+```
+
+Or use `pipx install logfire-cli`. In an activated virtual environment, you can
+also run `python -m pip install logfire-cli`.
+
+The package provides both `logfire` and `logfire-cli`. If another package already
+provides a `logfire` command, use `logfire-cli` or `uvx logfire-cli` to select this
+CLI explicitly.
+
+Python 3.9 or newer is required for the launcher. Wheels include the matching
+prebuilt binary for macOS (ARM64 and x86-64), Windows (ARM64, x86, and x86-64),
+GNU/Linux (ARM64, ARMv7, x86, x86-64, PowerPC 64 LE, RISC-V 64, and IBM Z), and
+musl Linux (ARM64, ARMv6, ARMv7, x86, and x86-64). You do not need Rust installed.
+GNU/Linux requires glibc 2.17 or newer, except RISC-V 64, which requires glibc
+2.31. The musl wheels support compatible Alpine Linux versions.
+
+## New to Logfire
+
+From your application's directory, create an account, organization, and first
+project in one guided flow:
+
+```bash
+logfire --region us signup --org acme --project my-app
+logfire --org acme project current
+```
+
+Replace `acme` and `my-app` with the real names you want. Use `--region eu` for
+the EU region. Browser OAuth credentials go to the operating system credential
+store; the project SDK credential stays under `.logfire/` in your application.
+
+Then add instrumentation with an installed coding agent:
+
+```bash
+logfire --org acme setup
+```
+
+## Use an existing account
+
+Use your real organization name in place of `acme`, and `eu` instead of `us` if
+your data is in the EU region:
+
+```bash
+logfire --region us --org acme auth
+logfire --org acme mcp projects
+```
+
+Complete sign-in and approve access in your browser. OAuth credentials are stored
+in the OS credential store, scoped to the Logfire origin and organization.
+
+Choose a project from the list, then query its data through the hosted Model
+Context Protocol (MCP) server:
+
+```bash
+logfire --org acme mcp query run 'SELECT message FROM records LIMIT 20' --project my-app
+```
+
+For scripts, make the target explicit and request non-interactive JSON output:
+
+```bash
+logfire --org acme --no-input --output json mcp projects
+```
+
+## Connect a local project
+
+From your application's directory, create or choose a project interactively:
+
+```bash
+logfire --org acme init
+```
+
+To connect an exact existing project without a picker:
+
+```bash
+logfire --org acme init use --name my-app --permission send
+logfire project current
+```
+
+OAuth remains in the OS credential store; the SDK token stays with the local
+project. Keep credential files out of version control.
+
+To create additional read or write tokens for that project:
+
+```bash
+logfire --org acme token read
+logfire --org acme token write
+```
+
+Each command creates a new token and prints the secret once to standard output.
+Store it securely; do not paste it into logs, issues, or chat. These commands do
+not replace the project's saved SDK write token.
+
+## Run Python with automatic instrumentation
+
+The CLI selects the active project interpreter and delegates instrumentation to
+the Logfire Python SDK installed in that environment:
+
+```bash
+logfire run app.py
+logfire run -m uvicorn main:app
+logfire run pytest tests/
+```
+
+Use `--python .venv/bin/python` when interpreter discovery is ambiguous. Run
+`logfire help run` for selection rules and passthrough behavior.
+
+## Set up instrumentation with a coding agent
+
+With Codex or Claude Code installed, run this from your application's directory:
+
+```bash
+logfire --region us --org acme setup
+```
+
+The CLI detects installed agents and hands off the Logfire setup instructions
+bundled with this release. The agent can change your project to add
+instrumentation, using its normal permission and approval controls.
+
+If you already know the exact project and setup task, pass them explicitly:
+
+```bash
+logfire --region us --org acme setup --project api --task instrumentation
+```
+
+Use bare `setup` when you want the CLI and agent to discover the task from the
+current directory.
+
+To inspect the instructions without launching an agent:
+
+```bash
+logfire --region us --org acme setup --print-prompt
+```
+
+## Help and updates
+
+```bash
+logfire help
+logfire help mcp
+logfire help setup
+uv tool upgrade logfire-cli
+```
+
+Use the upgrade command for a `uv tool install` installation; otherwise upgrade
+with the package manager you used to install it.
+
+See the [Logfire documentation](https://pydantic.dev/docs/logfire/) for application
+instrumentation and platform guides. Logfire CLI is licensed under the MIT license.

logfire_cli-0.1.5.dist-info/RECORD

@@ -0,0 +1,7 @@
+logfire_cli-0.1.5.dist-info/METADATA,sha256=xhJdwqJfBqYGLjcQZWxECT9ZKvpkTnT7TJdb85cKbFc,5483
+logfire_cli-0.1.5.dist-info/WHEEL,sha256=b89ep8IcILUGi6iRN3H45-RjbBI4gsTub8fyLkS4MN8,101
+logfire_cli-0.1.5.dist-info/entry_points.txt,sha256=3BUySf0XhtZmjkshAhg2Xby6yow-Q19XgB7vsYhhMPo,76
+logfire_cli-0.1.5.dist-info/licenses/LICENSE,sha256=A1UHuKHnh6FsfxOPCSVXowqO6cyc726E0RVG7juaRc0,1099
+logfire_cli/__init__.py,sha256=oDBQ41SBhqtNJzcF71x82-NJXk53lgg58Q4_dqzvdpA,437
+logfire_cli/bin/logfire.exe,sha256=CUNhBWg9n-gvpdMwqoFaX7gDKTUW6ly1mb0WDxTiSXg,5229056
+logfire_cli-0.1.5.dist-info/RECORD,,

logfire_cli-0.1.5.dist-info/WHEEL

@@ -0,0 +1,4 @@
+Wheel-Version: 1.0
+Generator: logfire-cli release tooling
+Root-Is-Purelib: false
+Tag: py3-none-win32

logfire_cli-0.1.5.dist-info/entry_points.txt

@@ -0,0 +1,3 @@
+[console_scripts]
+logfire = logfire_cli:main
+logfire-cli = logfire_cli:main

logfire_cli-0.1.5.dist-info/licenses/LICENSE

@@ -0,0 +1,21 @@
+The MIT License (MIT)
+
+Copyright (c) 2023 - present Pydantic Services inc.
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in all
+copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
+SOFTWARE.