@tailglow/cli 0.5.1 → 0.6.1

package/README.md

@@ -6,7 +6,7 @@ same API by construction.
 
 ```bash
 npm install -g @tailglow/cli
-tglow config set api_key tg_api_...
+tglow login
 tglow projects list
 ```
 
@@ -24,7 +24,7 @@ alias tg=tglow
 tglow <resource> <command> [flags]
 ```
 
-Run `tglow` for the resources, `tglow <resource>` for its commands, and
+Run `tglow help` for the resources, `tglow <resource>` for its commands, and
 `tglow <resource> <command> --help` for the flags, their types, allowed values and requiredness.
 
 ```bash
@@ -42,8 +42,31 @@ tglow views create-join --project prj_x --joins '[{"view_id":"view_b","on":"user
 
 ## Credentials
 
-Authentication is an API key, created in the dashboard under Team settings. Precedence is flag, then
-environment, then stored config:
+In a terminal, `tglow` offers sign-in when no credential is configured for the selected API.
+Choose an account, an API key, or Cancel. `tglow help` and `tglow --help` always show help.
+When a credential is configured, or without an interactive terminal, `tglow` shows help.
+
+`tglow login` signs in through the browser: it opens an approval page, you check the code matches
+and approve, and the CLI stores the credential in `~/.tailglow/config.json` (mode 0600). Choose your
+account (a CLI session that acts as you, in the team you choose) or an API key for one team.
+In a terminal it counts down to the code's expiry, ten minutes after creation. It makes a final
+poll to collect an approval given just before expiry, then ends cleanly if the code expired.
+Run `tglow login` to try again. If the server still reports pending, the CLI keeps the sign-in and
+shows `tglow login --wait` to resume. These normal interactive endings exit `0`; `--wait` retains
+exit `75` while pending. A request in progress can finish after expiry to avoid losing a credential.
+Without a terminal (an agent, a script) it prints the link and exits; approve it, then run
+`tglow login --wait`.
+
+```bash
+tglow login                    # asks which method in a terminal
+tglow login --method api-key   # skip the question
+tglow login --wait             # collect a sign-in started without a terminal
+tglow whoami                   # who the CLI is acting as, in which team
+tglow logout                   # end the credential and remove it
+```
+
+An API key works too. Precedence is `--api-key`, then `TAILGLOW_API_KEY`, then the `tglow login`
+credential, then a stored `api_key`:
 
 ```bash
 tglow projects list --api-key tg_api_...     # this call only
@@ -51,7 +74,8 @@ TAILGLOW_API_KEY=tg_api_... tglow projects list
 tglow config set api_key tg_api_...          # ~/.tailglow/config.json, mode 0600
 ```
 
-A stored key is never printed back, by `config get` or anything else.
+A login credential is only ever sent to the API that issued it, and no credential is printed
+back, by `config get` or anything else.
 
 `tglow config` also stores a default `project` and `team`, which is what lets
 `tglow metrics list` work without repeating the project on every call. Those two are the only
@@ -92,13 +116,27 @@ and `--limit` on its own when you want a single page.
 A delete asks for confirmation in a terminal. `--yes` skips the prompt, and a non-interactive run
 proceeds without one, so scripts and agents are not blocked on a question they cannot answer.
 
+## Docs
+
+Every guide and API reference page ships with the CLI, so reading them needs no network:
+
+```bash
+tglow docs                  # the index of every page
+tglow docs guides/sdk       # one page, as markdown
+tglow docs /api/drains.md   # any link from the index works as it is
+```
+
+Pages print as markdown even when piped; `--json` returns `{ path, url, content }` for a page, or
+`{ index, pages, online }` for the index.
+
 ## Development
 
 ```bash
 bun run tglow <resource> <command>   # run from source, without installing
 bun run test:cli                     # unit tests, no network
-bun run build:llms                   # regenerate src/commands.generated.js
+bun run build:llms                   # regenerate src/commands.generated.js and src/docs.generated.js
 ```
 
-`src/commands.generated.js` is written by `scripts/build/llms.build.js` and is never edited by hand.
-Adding a route to the API adds its command here with no change to this package.
+`src/commands.generated.js` and `src/docs.generated.js` are written by `scripts/build/llms.build.js`
+and are never edited by hand. Adding a route to the API adds its command here with no change to this
+package, and editing a guide changes the bundled page the same way.

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@tailglow/cli",
-  "version": "0.5.1",
+  "version": "0.6.1",
   "type": "module",
   "description": "The Tailglow command line. Every command is generated from the Tailglow API reference, so the CLI and the documentation can never describe different APIs.",
   "bin": {