@getfrontline/cli 1.0.0 → 1.0.1

package/README.md

@@ -1,28 +1,25 @@
-# @frontline/cli
+# @getfrontline/cli
 
 Unified Frontline command-line toolbox. Ships two binaries:
 
 - **`frontline`** — public REST API: agents, workflows, billing, tables, objects, raw GET, Claude Code skills setup.
-- **`max`** — Max chat & admin REST (Firebase ID token auth, interactive chat).
-
-> **Note (dev):** the default base URL is `http://localhost:7010/public/v1`.
-> When deploying to production, update it manually (per-profile, flag, or env var).
+- **`max`** — Max chat & admin REST (per-user API key as Bearer, interactive chat).
 
 ## Installation
 
 ```bash
-npm install -g @frontline/cli
+npm install -g @getfrontline/cli
 ```
 
 Or run without installing:
 
 ```bash
-npx @frontline/cli --help
+npx @getfrontline/cli --help
 ```
 
 ## Output format
 
-All `frontline` commands print **JSON to stdout by default** so you can pipe them into `jq`, scripts, or CI. Opt into human-readable output with:
+All `frontline` commands print **JSON to stdout by default** (scripting-friendly). Opt into human-readable output with:
 
 - `--pretty` — key/value blocks, spinners, icons (to stderr-safe channels)
 - `--table` — tabular rendering for list endpoints
@@ -33,22 +30,13 @@ Errors always go to `stderr` in human form and to `stdout` as structured JSON wh
 
 # `frontline` binary
 
-## Authentication
-
-API keys are sent via `Authorization: Bearer`.
-
 ### Login
 
 ```bash
-# Default profile, default base URL (localhost in dev)
 frontline auth login <api-key>
-
-# Multiple environments via named profiles
-frontline auth login <key> --profile production --base-url https://api.getfrontline.ai/public/v1
-frontline auth login <key> --profile staging    --base-url https://staging-api.example.com/public/v1
 ```
 
-The key is stored locally in your OS config dir (via `conf`). No `/me`/`/billing` verification is performed at login time — the key is saved as-is and validated on first real call.
+The API key is shared between `frontline` and `max` automatically.
 
 ### Switch / inspect profiles
 
@@ -60,10 +48,6 @@ frontline auth logout             # remove active profile
 frontline auth logout --profile staging
 ```
 
-### Resolution priority
-
-`--api-key` / `--base-url` flags → `FRONTLINE_API_KEY` / `FRONTLINE_BASE_URL` env → active profile → default (`http://localhost:7010/public/v1`).
-
 ## Commands
 
 ### Agents
@@ -146,15 +130,14 @@ Run `frontline <resource> <subcommand> --help` for details and examples.
 Every `frontline` command accepts:
 
 - `--api-key <key>` — override stored API key for a single call
-- `--base-url <url>` — override stored base URL for a single call
 - `--profile <name>` — use a specific saved profile
-- `--debug` — verbose request/response logs (token is redacted)
+- `--debug` — verbose request/response logs
 - `--pretty` — human-readable output
 - `--table` — tabular output for list endpoints
 
 ## Claude Code Skills
 
-Install Frontline skills into Claude Code (auto-detected on `npm install`):
+Optional: install Frontline skills into Claude Code (auto-detected on `npm install`):
 
 ```bash
 frontline setup --claude-skills          # install new skills
@@ -175,31 +158,59 @@ frontline agents list --debug
 
 ## Troubleshooting
 
-- **"No API key found"** — run `frontline auth login <key>` or set `FRONTLINE_API_KEY`.
+- **"No API key found"** — run `frontline auth login <key>`.
+- **"No Max API key found"** (Max CLI) — run `max auth login <key>` or `frontline auth login <key>` on the same profile.
 - **"Missing or invalid API key"** — key expired / revoked. Generate a new one.
-- **"Request timed out"** — check network; if using a custom base URL, verify with `frontline auth profiles list`.
+- **"Request timed out"** — check network.
 - **Rate limit** — public API allows 100 req/min.
 
 ---
 
 # `max` binary
 
-Browser-based sign-in (Firebase ID token flow). Same npm package exposes the `max` command after install.
+Authentication uses the **same API key** as `frontline`. Logging in with either CLI keeps them in sync.
 
 ```bash
 max --help
-max auth login
-max auth login --google
-max auth login --microsoft
-max auth login --email
-max auth login --otp
+max auth login <api-key>
 max auth whoami
-max auth logout
+max auth logout                    # clears Max + matching Frontline profile
+max auth logout --keep-frontline   # only clears the Max store
+```
+
+### Response shape and stdout
+
+Max Public API responses are typically `{ "ok": true|false, "data": ... }`. HTTP errors still use 4xx/5xx; logical failures may return `200` with `ok: false` (the CLI treats those as errors).
+
+- **`max "…"`** (root) and **`max chat send`**: default stdout is **one-line JSON** (`JSON.stringify` of the last response: POST, or last GET after polling). Use **`--pretty`** for assistant **plain text** from `data`. Use **`--json`** to print only the POST body and **skip polling**.
+- **`max conversations …`**: same idea — default one-line JSON; **`--pretty`** for plain text when the CLI can infer it.
+- **`max chat` / REPL**: stdout is assistant **plain text** from `data` when possible (interactive UX); otherwise one-line JSON. No progress spinners on stdout.
+
+### Public API — Max conversations
+
+| Method  | Path (after base)                                 |
+| ------- | ------------------------------------------------- |
+| `POST`  | `/max/conversations/message`                      |
+| `GET`   | `/max/conversations/:conversationId`              |
+| `PATCH` | `/max/conversations/:conversationId`              |
+| `POST`  | `/max/conversations/:conversationId/abortMessage` |
+| `GET`   | `/max/conversations/`                             |
+
+CLI:
+
+```bash
+max conversations list
+max conversations get 123
+max conversations update 123 --data '{"title":"Renamed"}'
+max conversations abort 123
+# alias: max conv list
 ```
 
+Global flags: `--profile`, `--api-key`, `--pretty`, `--debug` (same resolution as `max chat send`).
+
 ## Chat with Max
 
-After signing in, you can send messages:
+After `max auth login`, you can send messages:
 
 ```bash
 # Send message (uses last conversation by default)
@@ -211,6 +222,12 @@ max --new "Hola"
 # Explicit conversation id
 max --conversation 123 "Hola"
 
+# Default: one-line JSON from the API; human reply with --pretty
+max "Hola" --pretty
+
+# Override API key for one run
+max "Hola" --api-key flk_...
+
 # Alternative explicit command form
 max chat send "Hola"
 ```
@@ -227,93 +244,3 @@ Inside the interactive prompt, use:
 - `:new` to start a new conversation
 - `:conv <id>` to switch conversations
 - `:exit` to quit
-
-## Configuration
-
-The Max API base defaults to `https://prod-api.getfrontline.ai/api/v2`.
-Override with `--api-base-url` or set `MAX_API_BASE_URL`:
-
-```bash
-export MAX_API_BASE_URL="https://localhost:7010/api/v2"
-max --new "Hola" --debug
-```
-
-### Terminal logo (optional)
-
-The package ships a bundled logo at `packages/cli/assets/logo3.png` (included in the published npm package via `package.json` → `files`). The CLI looks for it automatically.
-
-Override the path:
-
-```bash
-export MAX_CLI_LOGO_PATH="/absolute/path/to/logo3.png"
-```
-
-If the logo can't be rendered (many Windows terminals), the CLI still shows the text welcome banner.
-
-### Configure the hosted login page
-
-The CLI opens a **URL you host** (web app). Set:
-
-- `MAX_CLI_AUTH_URL` (preferred), or `FRONTLINE_MAX_CLI_AUTH_URL`, or `FRONTLINE_CLI_AUTH_URL`
-
-Example:
-
-```bash
-export MAX_CLI_AUTH_URL="https://app.getfrontline.ai/max-cli/login"
-max auth login
-```
-Optional override per run:
-
-```bash
-max auth login --google --auth-url "https://localhost:3000/max-cli/login"
-```
-
-### Contract for the web app (backend + frontend)
-
-The CLI appends query parameters to `MAX_CLI_AUTH_URL`:
-
-| Parameter       | Meaning                                                                   |
-| --------------- | ------------------------------------------------------------------------- |
-| `provider`      | `google`, `microsoft`, or `otp`                                           |
-| `redirect_uri`  | `http://127.0.0.1:<port>/callback` (local HTTP server started by the CLI) |
-| `state`         | Random anti-CSRF value; **must** be returned unchanged                    |
-| `response_mode` | `query` (callback uses query string)                                      |
-
-After the user signs in with Firebase (Google / Microsoft / email OTP), redirect the browser to:
-
-**Success:** `redirect_uri` + `?token=<Firebase_ID_token>&state=<same_state>`
-Optional: `&refresh_token=<refresh_if_you_have_it>` (only if your app can expose it safely).
-
-**Error:** `redirect_uri` + `?error=access_denied&state=<same_state>&error_description=<url-encoded message>`
-
-The token should be the same **Firebase ID token** your API already accepts in `Authorization: Bearer` with `verifyIdToken` (see `src/api/middlewares/authMiddleware.ts`).
-
-### Config file location
-
-```bash
-max config-path
-```
-
----
-
-## Development
-
-This package lives inside the monorepo at `packages/cli`.
-
-```bash
-cd packages/cli
-npm install
-npm run dev:frontline -- agents list   # run frontline without building
-npm run dev:max -- "Hola"              # run max without building
-npm run build                          # compile TypeScript to dist/
-node dist/index.js --help              # run compiled frontline
-node dist/max.js --help                # run compiled max
-```
-
-Config is persisted via `conf`:
-
-- `frontline` binary → project name `frontline-cli`
-- `max` binary → project name `max-cli`
-
-They do **not** share credentials.
-

package/package.json

@@ -1,6 +1,6 @@
 {
     "name": "@getfrontline/cli",
-    "version": "1.0.0",
+    "version": "1.0.1",
     "description": "Frontline CLI — Public API (agents, workflows, billing, tables, objects) + Max chat/admin REST from your terminal",
     "private": false,
     "type": "commonjs",
@@ -25,7 +25,11 @@
         "frontline",
         "cli",
         "api",
-        "max"
+        "max",
+		"agents",
+		"getfrontline",
+		"workflows",
+		"crm"
     ],
     "license": "MIT",
     "dependencies": {