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

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Files changed (3) hide show
  1. package/README.md +142 -2
  2. package/bin/logfire +0 -0
  3. package/package.json +4 -4
package/README.md CHANGED
@@ -1,3 +1,143 @@
1
- # Placeholder
1
+ # Logfire CLI
2
2
 
3
- Bootstrap version that only reserves this package name for trusted publishing. Do not install.
3
+ Set up [Pydantic Logfire](https://pydantic.dev/logfire), query your telemetry,
4
+ and manage projects and tokens without leaving the terminal.
5
+
6
+ [Getting started](docs/getting-started.md) · [Install](docs/installation.md) ·
7
+ [User guide](docs/README.md) · [Develop the CLI](dev-docs/README.md)
8
+
9
+ ## Get started
10
+
11
+ Install the native CLI with `uv`:
12
+
13
+ ```bash
14
+ uv tool install logfire-cli
15
+ logfire --version
16
+ ```
17
+
18
+ Want to try it first? Run either command without installing anything:
19
+
20
+ ```bash
21
+ uvx logfire-cli --help
22
+ npx logfire-cli --help
23
+ ```
24
+
25
+ You can also install it with npm:
26
+
27
+ ```bash
28
+ npm install --global logfire-cli
29
+ logfire --version
30
+ ```
31
+
32
+ ### New to Logfire?
33
+
34
+ From your application's directory, choose the organization and first project
35
+ names you want:
36
+
37
+ ```bash
38
+ logfire --region us signup --org acme --project my-app
39
+ ```
40
+
41
+ The CLI opens a short-lived signup page in your browser. After you approve the
42
+ signup, it creates the organization and project and connects the current
43
+ directory to that project. Use `--region eu` if your Logfire account belongs in
44
+ the EU region.
45
+
46
+ ### Already have a Logfire account?
47
+
48
+ Sign in, then create or choose a project interactively:
49
+
50
+ ```bash
51
+ logfire --region us auth --org acme
52
+ logfire --org acme init
53
+ ```
54
+
55
+ Browser credentials stay in your operating system's credential store. `init`
56
+ writes the project's SDK credential to `.logfire/logfire_credentials.json` and
57
+ keeps it out of version control.
58
+
59
+ ### Check it and do something useful
60
+
61
+ ```bash
62
+ logfire --org acme project current
63
+ logfire --org acme wizard
64
+ logfire --org acme mcp query run 'SELECT message FROM records LIMIT 20' --project my-app
65
+ ```
66
+
67
+ - `project current` verifies which Logfire project this directory uses.
68
+ - `project open` opens that validated project, while `--no-open` prints its URL.
69
+ - `wizard` prepares the account and project, then asks an installed Codex,
70
+ Claude Code, GitHub Copilot, Cursor, or Google Antigravity agent to instrument
71
+ and verify your application.
72
+ - `mcp query run` queries your Logfire data through the hosted MCP server.
73
+
74
+ For the complete walkthrough, including existing-project and automation flows,
75
+ see [Getting started](docs/getting-started.md).
76
+
77
+ ## Common jobs
78
+
79
+ | I want to… | Command | Guide |
80
+ | --- | --- | --- |
81
+ | Create my Logfire account and first project | `logfire signup` | [Signup](docs/commands/signup.md) |
82
+ | Sign in to an existing account | `logfire auth` | [Authentication](docs/authentication.md) |
83
+ | Connect this directory to a project | `logfire init` | [Project setup](docs/commands/init.md) |
84
+ | Add application instrumentation | `logfire wizard` | [Agent-assisted setup](docs/commands/wizard.md) |
85
+ | Try the beta AI Gateway integration | `logfire --beta agent gateway` or `logfire --beta agent proxy launch` | [Gateway setup](docs/commands/proxy.md) |
86
+ | Run Python with automatic instrumentation | `logfire run` | [Run Python](docs/commands/run.md) |
87
+ | Query traces and logs | `logfire mcp query` | [MCP](docs/commands/mcp.md) |
88
+ | Open or inspect the current project | `logfire project` | [Project](docs/commands/project.md) |
89
+ | Create a project read or write token | `logfire token` | [Tokens](docs/commands/token.md) |
90
+ | Diagnose credentials or local setup | `logfire doctor` | [Doctor](docs/commands/doctor.md) |
91
+
92
+ The CLI also includes beta typed Platform API commands, safe generic MCP calls,
93
+ agent skills, and beta Codex telemetry setup. The [user guide](docs/README.md) lists
94
+ every command by task.
95
+
96
+ ## Help that starts small
97
+
98
+ ```bash
99
+ logfire --help
100
+ logfire help signup
101
+ logfire help init
102
+ logfire help mcp query
103
+ ```
104
+
105
+ Short help keeps common choices visible. `logfire help <command>` adds examples,
106
+ effects, and advanced options.
107
+
108
+ For scripts and coding agents, add `--no-input` and request `--output json` or
109
+ `--output jsonl` instead of parsing human-readable output. See
110
+ [Output contracts](docs/output-contracts.md).
111
+
112
+ ## Credentials stay in the right place
113
+
114
+ - Browser OAuth credentials are scoped to one Logfire origin and organization
115
+ and stored in the operating system credential store.
116
+ - Project write credentials stay with the local project under `.logfire/`.
117
+ - Coding agents launched by setup or bundled skills do not inherit Logfire
118
+ account credentials from the CLI's environment.
119
+ - Newly created secrets are printed once only when a token-creation command is
120
+ explicitly used.
121
+ - `--org` always means the real organization name shown in Logfire.
122
+
123
+ See [Authentication](docs/authentication.md) for multiple organizations,
124
+ headless API keys, logout, and credential precedence.
125
+
126
+ ## Installation and updates
127
+
128
+ PyPI provides native binaries for all 17 supported targets. npm covers the five
129
+ common macOS, GNU/Linux, and Windows combinations. Repository readers can also
130
+ download every prebuilt archive, plus checksums and verification evidence, from
131
+ [GitHub Releases](https://github.com/pydantic/logfire-cli/releases/latest). Until
132
+ this repository is public, that GitHub route requires Pydantic repository access.
133
+
134
+ See [Installation](docs/installation.md) for supported platforms, one-off use,
135
+ updates, and shell completions.
136
+
137
+ ## Contributing and security
138
+
139
+ Developing the CLI itself? Start with the [developer guide](dev-docs/README.md)
140
+ and [contribution guide](CONTRIBUTING.md). Report vulnerabilities through the
141
+ private process in [SECURITY.md](SECURITY.md), never through a public issue.
142
+
143
+ Logfire CLI is released under the [MIT License](LICENSE).
package/bin/logfire CHANGED
Binary file
package/package.json CHANGED
@@ -4,6 +4,9 @@
4
4
  ],
5
5
  "description": "Native binary for @pydantic/logfire-cli-linux-x64-musl.",
6
6
  "homepage": "https://pydantic.dev/logfire",
7
+ "libc": [
8
+ "musl"
9
+ ],
7
10
  "license": "MIT",
8
11
  "name": "@pydantic/logfire-cli-linux-x64-musl",
9
12
  "os": [
@@ -11,8 +14,5 @@
11
14
  ],
12
15
  "preferUnplugged": true,
13
16
  "repository": "https://github.com/pydantic/logfire-cli",
14
- "version": "0.0.0",
15
- "libc": [
16
- "musl"
17
- ]
17
+ "version": "0.1.6"
18
18
  }