omnish 1.2.4 → 1.3.0

package/CHANGELOG.md

@@ -7,6 +7,66 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
 
 ## [Unreleased]
 
+## [1.3.0] - 2026-05-18
+
+### Added
+
+- **Platform attached mode**: `omnish run` with `platform_url` + `platform_token`; inbound policy from `GET /v1/me` (allowlists, `gatewayMode`).
+- **`omnish platform` CLI**: `status`, `allow`, `login`, `probe`, `link-whatsapp`, `unlink-whatsapp`, `import-whatsapp`.
+- **`omnish config` CLI**: `add`, `show`, `edit`, `delete` for `config.json` including platform credentials (env still overrides).
+- **Platform relay**: WhatsApp/Telegram connectors, `PUT /v1/me/allowlists`, dashboard pairing UI, connector restore on boot, Telegram `/id` before allowlist.
+- **Platform device WebSocket fallback**: CLI tries `/platform/device` then `/control/device`; relay serves both on the control port.
+- **`omnish platform probe`**: diagnoses WebSocket routing for attached `omnish run`.
+
+### Fixed
+
+- **Platform WhatsApp QR pairing**: Baileys 515 `pairing_restart` reconnect loop; close-handler bug that blocked reconnect after `stop()`.
+- **Attached CLI allowlist**: `buildAllowSet` normalizes platform digits-only entries so `+E164` inbound checks match dashboard allowlists.
+- **WhatsApp LID routing** on platform to attached devices; live allowlist reload on platform inbound.
+- **Attached `omnish run` behind misconfigured proxies**: relay serves device WebSocket paths on control port and HTTP edge.
+- **CI / release**: GitHub Actions use Node 22 (pnpm 11); tunnel integration tests install local `contrib/tunnel-relay` deps before `pnpm test`.
+- **Chat LLM fallback**: ignore `EPIPE` when a piped subprocess exits before stdin is closed (fixes flaky CI `workDir` test).
+
+### Documentation
+
+- [Platform reference](docs/guides/platform-reference.md) hub; attached-mode guides; Easypanel redeploy notes for relay + `COMM_LAYER_DATA_DIR`.
+
+[1.3.0]: https://github.com/eligapris/omnish/compare/v1.2.4...v1.3.0
+
+## [1.2.5] - 2026-05-16
+
+### Added
+
+- **`omnish config` CLI**: `add`, `show`, `edit`, `delete` for `config.json` including `platform_url`, `platform_token`, and `platform_device_id` (env still overrides).
+- **`omnish platform probe`**: diagnoses WebSocket routing for attached `omnish run`.
+- **Platform device WebSocket fallback**: CLI tries `/platform/device` then `/control/device`; relay serves both on the control port.
+
+### Fixed
+
+- **Attached `omnish run` behind misconfigured proxies**: relay serves `/platform/device` and `/control/device` on both the control port (8788) and the HTTP edge (8787). Smoke test covers device paths via `SMOKE_BASE_URL`.
+
+### Documentation
+
+- EasyPanel routing for apex vs wildcard and control paths: [contrib/tunnel-relay/docs/dns.md](contrib/tunnel-relay/docs/dns.md).
+
+### Added
+
+- **`/bg --notify` / `-N`**: background jobs can now send a completion notification (exit code, duration, command) to your chat when the process finishes. Combine with names: `/bg -N -n deploy git pull && docker compose up -d`.
+- **Cowork conditional notifications (`notifyWhen`)**: `/cowork set <name> when always|failure|state-change` controls when a task sends its notification. `failure` only notifies on non-zero exit; `state-change` tracks the last-known result in SQLite and only notifies when it flips (e.g. ok→fail or fail→ok).
+- **Cowork heartbeat (dead-man's-switch)**: new schedule kind `heartbeat` that expects periodic check-ins instead of running a command. Create with `/cowork add backup heartbeat 1h 10m`, check in with `/cowork checkin backup`. If no check-in arrives within interval + grace, an alert is sent; a recovery notification follows when check-ins resume.
+- **Webhook receiver**: lightweight HTTP endpoint (`POST /webhook`) for CI/CD webhooks. Accepts JSON payloads with Bearer token auth, formats GitHub Actions and GitLab CI events into concise chat messages, and delivers via `sendToPeer`. Config keys: `webhookEnabled`, `webhookPort`, `webhookHost`, `webhookToken`. See [docs/features/webhook-receiver.md](docs/features/webhook-receiver.md).
+- **Multi-step recipe runbooks**: `/run add deploy --steps git pull; npm ci; npm run build; pm2 restart all` creates a recipe with sequential steps. Steps stop on first failure by default; prefix a step with `+` to continue on fail. Results are sent as a formatted per-step summary when all steps complete. See `/run show <name>` for step listing.
+
+### Documentation
+
+- New feature doc: [Webhook receiver](docs/features/webhook-receiver.md).
+- Updated [background-jobs.md](docs/features/background-jobs.md) for `--notify` / `-N`.
+- Updated [cowork.md](docs/features/cowork.md) for `notifyWhen` conditional notifications, heartbeat schedule, and `/cowork checkin`.
+- Updated [user-guide.md](docs/guides/user-guide.md) for all new features.
+- Updated [configuration.md](docs/guides/configuration.md) with webhook receiver config section.
+- Updated [README.md](README.md) command summaries.
+- Updated [research pain points](docs/research/unsolved-developer-pain-points.md) with implementation status.
+
 ## [1.2.4] - 2026-05-11
 
 ### Added

package/README.md

@@ -27,14 +27,22 @@
 
 **WARNING: Remote shell access.** This tool links **WhatsApp** and/or **Telegram** (and is built to add more surfaces later) to your machine and runs shell commands from **allowlisted senders only**. Anyone who can message from an allowed identity can run arbitrary commands as your user. Treat those identities as credentials. Do not use `*` wildcards on the allowlist.
 
+### Glossary: gateway, communication layer, modes
+
+- **Gateway / CLI** — `omnish run` on **your** machine: enforces allowlist and runs shell / PTY **locally** (security boundary for execution).
+- **Standalone mode** — messengers connect on the same host (`omnish link`, `omnish allow`, `omnish run`). No hosted layer required.
+- **Platform attached mode** — link WhatsApp/Telegram **once** on the hosted relay; each machine runs `omnish run` with `OMNISH_PLATFORM_URL` + `OMNISH_TOKEN` (or `omnish config add platform_url … platform_token …`). Chat is **routed** to the right device; shell still runs only on that box. Docs: [platform attached mode](docs/guides/platform-attached-mode.md) · [**platform reference** (full API/CLI/dashboard)](docs/guides/platform-reference.md) · [communication layer model](docs/architecture/communication-layer-model.md).
+- **`/service` “platform”** — **operating system** (Linux, macOS, Windows), not the communication layer.
+
 ## What it does
 
 - `omnish link` — QR login (WhatsApp → Linked devices), or **`omnish link --tg <bot_token>`** to save a Telegram bot token and set `gatewayMode` (`telegram`, or `both` if WhatsApp is already linked). See `omnish link --help`.
 - `omnish run` — Listen for DMs; execute commands; reply with output.
 - **`omnish i`** — Interactive terminal with the same commands as chat (local full trust; the inbox allowlist is **not** applied). Run from any directory; session cwd starts at the current directory. Use **`/sendto <destination> <selectors> [-- caption]`** (for example `wa`, `tg`, `*`, `+E164,+E164`) to push files through a running gateway (see `omnish i --help`). Background jobs from `/bg` in the REPL are **only** that process (not the gateway’s job list).
 - **Sync:** send `!ls` or `! ls` (prefix configurable; default `!`). Each chat has its **own working directory**; use `!cd /path` or `! cd /path` to change it (saved under the data dir, e.g. `~/.omnish/sessions.json`).
-- **Background:** **`/bg`** runs a long command in that chat’s cwd; optional **`-n myname`** / **`--name`** labels the job so you can use **`/log myname`**, **`/tail myname`**, **`/kill myname`** instead of the 8-char id. Then `/jobs`, `/log`, `/tail`, `/kill` as usual.
-- **Cowork:** `/cowork` / `/cw` — scheduled or on-demand saved shell tasks, logs under `~/Cowork/…` by default. See [docs/features/cowork.md](docs/features/cowork.md).
+- **Background:** **`/bg`** runs a long command in that chat’s cwd; optional **`-n myname`** / **`--name`** labels the job; **`--notify`** / **`-N`** sends a completion notification with exit code and duration. Then `/jobs`, `/log`, `/tail`, `/kill` as usual.
+- **Cowork:** `/cowork` / `/cw` — scheduled or on-demand saved shell tasks with conditional notifications (`always` / `failure` / `state-change`), heartbeat dead-man's-switch monitoring (`/cowork checkin`), and logs under `~/Cowork/…` by default. See [docs/features/cowork.md](docs/features/cowork.md).
+- **Webhook receiver:** built-in HTTP endpoint for CI/CD notifications (GitHub Actions, GitLab CI). Enable with `webhookEnabled: true`. See [docs/features/webhook-receiver.md](docs/features/webhook-receiver.md).
 - **Interactive PTY:** drive TUIs and REPLs (`cursor-agent`, `claude`, `bash`, etc.) from DMs. See [Interactive sessions](#interactive-sessions) below.
 - **User shortcuts:** save per-chat commands under a short name (`/shortcut add myproj !cd ~/code/myproj`), then run **`!myproj`** or **`/myproj`** (bare token only) to expand once—see [User shortcuts](#user-shortcuts).
 
@@ -235,12 +243,14 @@ Index and curated paths: **[docs/README.md](docs/README.md)**.
 | Topic | Doc |
 |-------|-----|
 | Vision — local first, product direction | [docs/vision.md](docs/vision.md) |
+| Docker gateway (reference compose) | [docs/guides/docker-gateway-golden-path.md](docs/guides/docker-gateway-golden-path.md) |
 | Interactive terminal (`omnish i`, `/sendto` multi-target) | [docs/guides/interactive-cli.md](docs/guides/interactive-cli.md) |
 | Configuration (`config.json`) | [docs/guides/configuration.md](docs/guides/configuration.md) |
 | Browser setup UI (`omnish ui`) | [docs/guides/ui.md](docs/guides/ui.md) |
 | Cluster roster + `/config` from chat | [docs/features/cluster-and-chat-config.md](docs/features/cluster-and-chat-config.md) |
 | Interactive sessions (`/apps`) | [docs/features/sessions.md](docs/features/sessions.md) |
 | Background jobs | [docs/features/background-jobs.md](docs/features/background-jobs.md) |
+| Webhook receiver (CI/CD notifications) | [docs/features/webhook-receiver.md](docs/features/webhook-receiver.md) |
 | Message routing | [docs/architecture/routing.md](docs/architecture/routing.md) |
 | Security | [docs/architecture/security.md](docs/architecture/security.md) |
 | User guide | [docs/guides/user-guide.md](docs/guides/user-guide.md) |

package/config.example.json

@@ -21,13 +21,13 @@
   "appsClearInput": true,
   "appsClearInputDelayMs": 20,
   "appsClearInputSequence": "^A,^K",
-  "fileSendMaxBytes": 0,
-  "fileReceiveMaxBytes": 0,
+  "fileSendMaxBytes": 52428800,
+  "fileReceiveMaxBytes": 52428800,
   "fileReceiveRootMode": "downloads",
   "fileReceiveRootPath": "",
   "fileInboxSubdir": "inbox",
   "recipesAllowDangerousBuiltins": false,
-  "recipesMaxTaskChars": 0,
+  "recipesMaxTaskChars": 100000,
   "recipesMacroDefaultCommand": "claude -p \"$OMNISH_TASK\"",
   "clusterEnabled": false,
   "clusterLabel": "",
@@ -44,5 +44,10 @@
   "chatLlmMaxInputChars": 16000,
   "chatLlmMaxOutputChars": 24000,
   "chatLlmNeedsTty": false,
-  "chatLlmWorkDir": ""
+  "chatLlmWorkDir": "",
+  "tunnelEnabled": false,
+  "tunnelRelayUrl": "https://tunnel.omnish.dev",
+  "platformToken": "",
+  "platformDeviceId": "",
+  "tunnelMaxActive": 5
 }