@critiquedotsh/harness 0.1.7 → 0.1.10

package/README.md

@@ -7,7 +7,7 @@
 | **CritiqueCode** (this package) | [`@critiquedotsh/harness`](https://www.npmjs.com/package/@critiquedotsh/harness) | `critique-code` | Author: write the change, then survive review |
 | **Critique CLI** | [`@critiquedotsh/cli`](https://www.npmjs.com/package/@critiquedotsh/cli) | `critique` | Sidecar reviewer for agents you already run |
 
-Same npm org. Different products. Do not install CritiqueCode by swapping `@critiquedotsh/cli`. Do not call `critique finish` as a substitute for this harness.
+Same npm org. Different products. Do not install CritiqueCode by swapping `@critiquedotsh/cli`. Native evidence stays on `/review`. `/critique` and `critique_cli` spawn the installed `critique` sidecar when you want that binary.
 
 Docs: [CritiqueCode](https://critique.sh/docs/platform/critique-code) · [Inference API](https://critique.sh/docs/platform/inference-api) · [Critique CLI](https://critique.sh/docs/platform/cli)
 
@@ -77,6 +77,22 @@ Or skip the TTY and open a local browser UI (still the same author kernel in thi
 critique-code web
 ```
 
+Pair a phone to that same laptop process (Wi-Fi PIN, Slack/Telegram DM, or `--anywhere` with your own tunnel). The kernel never moves to Critique Cloud:
+
+```bash
+critique-code remote
+critique-code remote --slack --anywhere
+critique-code slack
+```
+
+Drive it from the website instead. Open [critique.sh/code](https://critique.sh/code), click **Connect this PC**, then paste the printed code on this machine:
+
+```bash
+critique-code connect K7M2-9QWX
+```
+
+The site is a remote, not a runner: prompts, approvals, and event output relay through critique.sh, but the kernel and every file write stay on this laptop. It needs `critique-code login` (a `crt_` key) so the laptop can claim the code outbound.
+
 Describe the change. Slash lines (`/review`, `/ship`, …) are never sent to the model.
 
 ## What a session does
@@ -87,7 +103,7 @@ Describe the change. Slash lines (`/review`, `/ship`, …) are never sent to the
 4. **`/repair`** runs verified repair on promoted findings. It is not auto-applied chatter.
 5. `none_promoted` means nothing was promoted. It is **not** a correctness proof.
 
-The author can fan out **`critique_task`** workers (`explore` is read-only; `general` / `implement` can write through the same CAS path). Independent review is still `/review`, not a worker. `critique_run` still needs your approval. Workers cannot nest `critique_task`.
+The author can fan out **`critique_task`** workers (`explore` is read-only; `general` / `implement` can write through the same CAS path). Independent native review is still `/review`, not a worker. `critique_cli` spawns the installed Critique CLI sidecar when you ask for that binary. `critique_run` still needs your approval. Workers cannot nest `critique_task` or `critique_cli`.
 
 The TTY shows a wordmark, a compact live status (`thinking` / `write path` / `task explore …`), then a one-line `▸` summary before the reply. It does not stream thinking paragraphs.
 
@@ -99,10 +115,15 @@ Interactive TTY sessions keep **stdout quiet**. Pass `--json` for the session en
 critique-code
 critique-code chat [--intent <text>] [--models provider/model,...] [--cwd <dir>] [--store <dir>] [--voice] [--json]
 critique-code web [--port <n>] [--cwd <dir>] [--store <dir>] [--models ...]
+critique-code remote [--anywhere] [--site] [--slack] [--telegram] [--port <n>] [--cwd <dir>]
+critique-code connect [CODE] [--cwd <dir>]
+critique-code slack [--port <n>] [--cwd <dir>]
+critique-code telegram [--port <n>] [--cwd <dir>]
 critique-code login
 critique-code settings | keys | models
 critique-code review [--depth quick|standard|paranoid] [--focus general,security] [--models ...] [--base <ref>] [--intent <text>] [--cwd <dir>] [--store <dir>]
 critique-code repair <review-run-id> [--store <dir>] [--cwd <dir>] [--models ...]
+critique-code critique [sidecar argv...] [--cwd <dir>]
 critique-code capabilities [--cwd <dir>]
 critique-code skills [--cwd <dir>]
 critique-code import-skills [--cwd <dir>]
@@ -113,10 +134,14 @@ critique-code help
 | --- | --- |
 | `critique-code` / `chat` | Interactive author session |
 | `web` | Local browser UI on `127.0.0.1` (same author kernel; no TTY required) |
+| `remote` | Phone pairing to this laptop: LAN PIN, optional `--anywhere` tunnel. Not Critique Cloud. |
+| `connect [CODE]` | Register this PC on critique.sh/code. The website is a remote; the kernel stays here. |
+| `slack` / `telegram` | Outbound bots. DM the agent from those apps; the kernel stays in this process. |
 | `login` | Browser device approval; connect Critique Inference |
 | `settings` / `keys` / `models` | TUI for route, stored keys, and model ids |
 | `review` | Evidence harness (JSON on stdout) |
 | `repair <id>` | Verified repair for a stored review run |
+| `critique [argv…]` | Spawn the installed Critique CLI sidecar (`critique review --json` by default) |
 | `capabilities` | Discovered local check tools |
 | `skills` | Built-in plus imported Claude Code / Codex / Cursor `SKILL.md` folders |
 | `import-skills` | Copy discovered skills into `~/.critique/code/skills` |
@@ -135,6 +160,8 @@ critique-code help
 | `--voice` | Start the author session in voice mode |
 | `--json` | Print the session envelope on stdout even on a TTY |
 | `--port <n>` | Loopback port for `critique-code web` (`0` = ephemeral) |
+| `--anywhere` | For `remote`: publish an outbound `cloudflared` or `ngrok` URL. Still this laptop. |
+| `--slack` / `--telegram` | Attach those portals to `web` / `remote` |
 | `-h` / `help` | Help |
 
 `critique-code review` is read-only. Use `critique-code repair <review-run-id>` for explicit repair. `--repair apply` on `review` is rejected.
@@ -147,11 +174,16 @@ Type `/` or `/help` for a selectable picker. **Lines that start with `/` never g
 | --- | --- |
 | `/` `/help` | Picker / help |
 | `/login` | Connect Critique Inference in the browser |
+| `/remote` | Pair a phone; this laptop stays the agent |
+| `/slack` | Attach Slack Socket Mode |
+| `/telegram` | Attach a Telegram bot |
 | `/voice` | Record one spoken prompt (Qwen3 ASR) |
 | `/voice on` | Keep listening after each reply |
 | `/voice off` | Return to the keyboard |
 | `/review` | Evidence harness since the last review checkpoint |
 | `/review all` | Evidence harness on the current tree even if unchanged |
+| `/critique` | Spawn the Critique CLI sidecar (`critique review --json`) |
+| `/critique finish` | Sidecar `finish --repair pack`; apply stays an explicit slash |
 | `/repair` | Verified repair of promoted findings |
 | `/ship` | Review, then end if the controller allows |
 | `/settings` | Keys, route, models |
@@ -225,6 +257,24 @@ Also:
 - `CRITIQUE_INFERENCE_BASE_URL` — override `https://critique.sh/api/v1`
 - `CRITIQUE_SITE_URL` — site origin for device login (default derived from the inference URL)
 - `CRITIQUE_CODE_PI_DRIVER=off` — disable the live author kernel (sessions stay `kernel_required`)
+- `SLACK_BOT_TOKEN` + `SLACK_APP_TOKEN` — Slack Socket Mode (outbound). Optional `CRITIQUE_CODE_PORTAL_USERS`
+- `TELEGRAM_BOT_TOKEN` — Telegram long poll (outbound). Optional `CRITIQUE_CODE_PORTAL_CHATS`
+- `CRITIQUE_CODE_PORTAL_SECRET` — shared secret for `POST /api/portal/inbound` from other portals
+- `CRITIQUE_CODE_TUNNEL` — prefer `cloudflared` or `ngrok` for `--anywhere`
+
+## Remote phone and portals
+
+The agent is this process on this laptop. Phone, Slack, Telegram, and the website are remotes. They are not Critique Cloud.
+
+1. Leave the machine awake with the session running.
+2. Same Wi-Fi: `critique-code remote`, open the LAN URL on the phone, enter the PIN from the terminal.
+3. Anywhere: DM the Slack or Telegram bot (`critique-code slack` / `critique-code telegram` / `--slack`). Those open outbound sockets. No inbound port.
+4. Website: `critique-code connect CODE` after `critique-code login` claims the PC from [critique.sh/code](https://critique.sh/code). The site relays prompts and approvals; the kernel stays here.
+5. Optional `--anywhere` uses **your** `cloudflared` or `ngrok`. The tunnel is a pipe. Writes still happen in this working tree.
+
+Slack Socket Mode needs `SLACK_BOT_TOKEN` (`xoxb-`) and `SLACK_APP_TOKEN` (`xapp-`) with message events. Telegram needs `TELEGRAM_BOT_TOKEN`. Optional allowlists: `CRITIQUE_CODE_PORTAL_USERS`, `CRITIQUE_CODE_PORTAL_CHATS`.
+
+From an already-open TTY: `/remote`, `/slack`, `/telegram`.
 
 ## Files on disk
 
@@ -234,6 +284,7 @@ Nothing secret is written into the repository.
 | --- | --- |
 | `~/.critique/code/auth.json` | Stored API keys (mode `0600`) |
 | `~/.critique/code/settings.json` | Route and model selection |
+| `~/.critique/code/portals.json` | Slack / Telegram / webhook portal tokens (mode `0600`) |
 | Review/repair store | Outcomes and repair artifacts (`--store` or the default store root) |
 
 Project `REVIEW_GUIDELINES.md` is loaded as a review constraint. `AGENTS.md`, `CRITIQUE.md`, and `CLAUDE.md` can seed author instructions.