@chieflab/cli 0.2.0

package/README.md

@@ -0,0 +1,163 @@
+# @chieflab/cli
+
+Hosted MCP from your terminal. ChiefLab's repo-aware launch flow plus approval-gated execution.
+
+> Package status: this CLI is packaged in the repo but not published to npm yet. Use hosted MCP directly today at `https://api.chieflab.io/api/mcp`; the commands below describe the CLI contract once published.
+
+```bash
+curl -X POST https://api.chieflab.io/api/mcp \
+  -H "Content-Type: application/json" \
+  -d '{"jsonrpc":"2.0","id":1,"method":"tools/list"}'
+```
+
+## Why a CLI when the MCP is an HTTP endpoint?
+
+Because `curl` is great until you need the second call. Once you've got a `runId` to look up, an `actionId` to publish, a reviewUrl to open, an `accountId` to pass — you want a real shell tool, not a fistful of JSON-RPC envelopes.
+
+This CLI:
+- Saves your API key once (`~/.chieflab/config.json`, `chmod 600`)
+- Wraps every operator + the closed-loop launch flow with sane flags
+- Has zero npm dependencies (node 20+ built-ins only — install in <5s)
+- Is honest about JSON output (`--json` on any command)
+
+## Current install status
+
+The npm package is not public yet. Do not tell users to run `npx @chieflab/cli`
+until `npm view @chieflab/cli` resolves. Use the hosted MCP endpoint and hosted
+agent-hook installer today:
+
+```bash
+curl -X POST https://api.chieflab.io/api/mcp \
+  -H "Authorization: Bearer $CHIEFLAB_API_KEY" \
+  -H "Content-Type: application/json" \
+  -d '{"jsonrpc":"2.0","id":1,"method":"tools/list"}'
+
+curl -fsSL https://chieflab.io/install-agent-hook.mjs | node -
+```
+
+After npm publish:
+
+```bash
+npm install -g @chieflab/cli
+npx @chieflab/cli init
+npx @chieflab/cli launch-here https://yoursite.com
+```
+
+Both `chieflab` and `chiefmo` work as the bin name.
+
+## Auth
+
+```bash
+chieflab login                 # interactive prompt
+chieflab login --key clp_...   # non-interactive
+chieflab whoami                # confirm workspace
+chieflab logout                # forget the key
+```
+
+Or skip the file and pass via env (good for CI):
+
+```bash
+export CHIEFLAB_API_KEY=clp_live_...
+chieflab whoami
+```
+
+Get a key at <https://chieflab.io/get-key>.
+
+## The closed loop
+
+```bash
+# 0. Install repo instructions so agents call ChiefLab after build
+chieflab init
+
+# 1. Plan + draft from the current repo
+chieflab launch-here https://yoursite.com --channels linkedin,x,email
+#   → returns launchId + publishActions + reviewUrl
+
+# 2. Approve on the reviewUrl (open it in a browser)
+
+# 3. Fire the approved actions
+chieflab publish launch-action-run_xxx-linkedin \
+  --content "..." --platform linkedin --account zer_acc_xxx
+
+chieflab send-email launch-action-run_xxx-email \
+  --from "Brand <hi@yourdomain.com>" --to user@example.com \
+  --subject "Launch day" --html "<h1>...</h1>"
+
+# 4. Wait 24h, then read results + get the next-move recommendation
+chieflab review run_xxx
+```
+
+Full launch wedge in 4 commands.
+
+`init` writes `AGENTS.md`, a Cursor rule, Claude command, Codex note, and an MCP config stub. It tells agents to call `chieflab_get_users_after_build`, surface `agentGuide.userMessage`, wait for the `reviewUrl`, execute only approved actions, resume with `chiefmo_continue_launch_loop`, and measure after 24h.
+
+Compatibility: `chieflab install-agent-hook` still works after npm publish. Public docs should prefer the hosted installer until `npm view @chieflab/cli` resolves.
+
+```bash
+chieflab init --dry-run
+chieflab init --runtime cursor
+chieflab init --runtime all --force
+```
+
+## Launch Commands
+
+```bash
+chieflab launch-here https://yoursite.com  # preferred: gathers repo context
+chieflab launch https://yoursite.com       # URL-only fallback
+chieflab marketing "Diagnose our current funnel"
+```
+
+Each accepts `--url <product-url>` (auto-extract brand context), `--tenant-id <id>` (use stored tenant), `--idempotency-key <key>` (cached re-runs).
+
+## Trigger phrases
+
+When an agent calls the CLI on a user's behalf, these phrases map to `launch-here`:
+
+- "launch this"
+- "get users"
+- "market this"
+- "announce this"
+- "post this"
+
+For an existing program ("why is X not working"), use `chieflab marketing "<goal>"` (calls `chiefmo_diagnose_marketing`).
+
+## Connections
+
+```bash
+chieflab connections           # show what's connected
+chieflab connect ga4           # OAuth start (also: search_console, hubspot)
+chieflab set-key zernio sk_... # for set-key flows (also: resend)
+```
+
+## Inbox
+
+```bash
+chieflab runs                  # list workspace runs
+chieflab runs --limit 50
+chieflab open run_xxx          # print the signed reviewUrl
+```
+
+## Tools introspection
+
+```bash
+chieflab tools                 # list the live MCP tools available on this key
+chieflab tools --json          # for piping into jq
+```
+
+## Flags
+
+| Flag | What |
+|------|------|
+| `--json` | Emit raw JSON (suppresses pretty terminal output) |
+| `--key <key>` | Override saved key for this call only |
+| `--endpoint <url>` | Override endpoint (default `https://api.chieflab.io/api/mcp`) |
+
+| Env | What |
+|-----|------|
+| `CHIEFLAB_API_KEY` | Wins over saved config (CI-friendly) |
+| `CHIEFLAB_ENDPOINT` | Wins over saved endpoint |
+| `NO_COLOR` | Disable ANSI colors |
+
+## License
+
+Apache 2.0. Source at <https://github.com/bdentech/chieflab>.

package/package.json

@@ -0,0 +1,44 @@
+{
+  "name": "@chieflab/cli",
+  "version": "0.2.0",
+  "mcpName": "io.github.bdentech/chieflab",
+  "description": "ChiefLab CLI — after-build GTM for agents. Run `chieflab launch-here` from a repo to collect context, create a launch room, approval-gate publish/send actions, and measure the next move.",
+  "type": "module",
+  "bin": {
+    "chieflab": "src/index.js",
+    "chiefmo": "src/index.js"
+  },
+  "files": [
+    "src/",
+    "README.md"
+  ],
+  "engines": {
+    "node": ">=20"
+  },
+  "keywords": [
+    "chieflab",
+    "chiefmo",
+    "mcp",
+    "ai-agent",
+    "agent-built",
+    "get-users",
+    "product-launch",
+    "marketing-ops",
+    "launch",
+    "gtm",
+    "startup",
+    "cursor",
+    "claude",
+    "codex"
+  ],
+  "homepage": "https://chieflab.io",
+  "repository": {
+    "type": "git",
+    "url": "git+https://github.com/bdentech/chieflab.git",
+    "directory": "apps/cli"
+  },
+  "license": "Apache-2.0",
+  "publishConfig": {
+    "access": "public"
+  }
+}