@pydantic/logfire-cli-linux-x64-musl 0.0.0 → 0.1.5

package/README.md

@@ -1,3 +1,140 @@
-# Placeholder
+# Logfire CLI
 
-Bootstrap version that only reserves this package name for trusted publishing. Do not install.
+Set up [Pydantic Logfire](https://pydantic.dev/logfire), query your telemetry,
+and manage projects and tokens without leaving the terminal.
+
+[Getting started](docs/getting-started.md) · [Install](docs/installation.md) ·
+[User guide](docs/README.md) · [Develop the CLI](dev-docs/README.md)
+
+## Get started
+
+Install the native CLI with `uv`:
+
+```bash
+uv tool install logfire-cli
+logfire --version
+```
+
+Want to try it first? Run either command without installing anything:
+
+```bash
+uvx logfire-cli --help
+npx logfire-cli --help
+```
+
+You can also install it with npm:
+
+```bash
+npm install --global logfire-cli
+logfire --version
+```
+
+### New to Logfire?
+
+From your application's directory, choose the organization and first project
+names you want:
+
+```bash
+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:
+
+```bash
+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
+
+```bash
+logfire --org acme project current
+logfire --org acme setup
+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.
+- `setup` prepares the account and project, then asks an installed Codex or
+  Claude Code 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](docs/getting-started.md).
+
+## Common jobs
+
+| I want to… | Command | Guide |
+| --- | --- | --- |
+| Create my Logfire account and first project | `logfire signup` | [Signup](docs/commands/signup.md) |
+| Sign in to an existing account | `logfire auth` | [Authentication](docs/authentication.md) |
+| Connect this directory to a project | `logfire init` | [Project setup](docs/commands/init.md) |
+| Add application instrumentation | `logfire setup` | [Agent-assisted setup](docs/commands/setup.md) |
+| Try the beta AI Gateway integration | `logfire --beta agent gateway` or `logfire --beta agent proxy launch` | [Gateway setup](docs/commands/proxy.md) |
+| Run Python with automatic instrumentation | `logfire run` | [Run Python](docs/commands/run.md) |
+| Query traces and logs | `logfire mcp query` | [MCP](docs/commands/mcp.md) |
+| Open or inspect the current project | `logfire project` | [Project](docs/commands/project.md) |
+| Create a project read or write token | `logfire token` | [Tokens](docs/commands/token.md) |
+| Diagnose credentials or local setup | `logfire doctor` | [Doctor](docs/commands/doctor.md) |
+
+The CLI also includes beta typed Platform API commands, safe generic MCP calls,
+agent skills, and beta Codex telemetry setup. The [user guide](docs/README.md) lists
+every command by task.
+
+## Help that starts small
+
+```bash
+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](docs/output-contracts.md).
+
+## 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/`.
+- 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](docs/authentication.md) 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](https://github.com/pydantic/logfire-cli/releases/latest). Until
+this repository is public, that GitHub route requires Pydantic repository access.
+
+See [Installation](docs/installation.md) for supported platforms, one-off use,
+updates, and shell completions.
+
+## Contributing and security
+
+Developing the CLI itself? Start with the [developer guide](dev-docs/README.md)
+and [contribution guide](CONTRIBUTING.md). Report vulnerabilities through the
+private process in [SECURITY.md](SECURITY.md), never through a public issue.
+
+Logfire CLI is released under the [MIT License](LICENSE).

package/package.json

@@ -4,6 +4,9 @@
   ],
   "description": "Native binary for @pydantic/logfire-cli-linux-x64-musl.",
   "homepage": "https://pydantic.dev/logfire",
+  "libc": [
+    "musl"
+  ],
   "license": "MIT",
   "name": "@pydantic/logfire-cli-linux-x64-musl",
   "os": [
@@ -11,8 +14,5 @@
   ],
   "preferUnplugged": true,
   "repository": "https://github.com/pydantic/logfire-cli",
-  "version": "0.0.0",
-  "libc": [
-    "musl"
-  ]
+  "version": "0.1.5"
 }