@akshar5/cohall 0.6.1 → 0.7.0

package/CHANGELOG.md

@@ -1,5 +1,30 @@
 # Changelog
 
+## [0.7.0](https://github.com/AksharP5/cohall/compare/v0.6.2...v0.7.0) (2026-09-26)
+
+
+### Features
+
+* **delegation:** exchange bounded task files ([#86](https://github.com/AksharP5/cohall/issues/86)) ([8a2f808](https://github.com/AksharP5/cohall/commit/8a2f80841d52a189736a17b991277eaf0c267f23))
+* **tasks:** surface completed work in a client inbox ([#84](https://github.com/AksharP5/cohall/issues/84)) ([a7a367f](https://github.com/AksharP5/cohall/commit/a7a367ff1ffcf9aa77d971d8f83d419154bbb656))
+
+## [0.6.2](https://github.com/AksharP5/cohall/compare/v0.6.1...v0.6.2) (2026-09-24)
+
+
+### Bug Fixes
+
+* **bot:** retain cancellation limits after uncertain dispatch ([#81](https://github.com/AksharP5/cohall/issues/81)) ([e324530](https://github.com/AksharP5/cohall/commit/e324530ee578bae7fd5a244a70daffa4304d8eb7))
+* **cli:** reject invalid timeouts before sending work ([#70](https://github.com/AksharP5/cohall/issues/70)) ([bac67e9](https://github.com/AksharP5/cohall/commit/bac67e9a2dc8c9c460f2b5df7b882d098177c5ae))
+* **config:** reject files as workspace roots ([#75](https://github.com/AksharP5/cohall/issues/75)) ([7b86305](https://github.com/AksharP5/cohall/commit/7b86305f36f68d264441c0d09fabbcbc23f457ae))
+* **delegation:** keep child tasks out of blocked parent slots ([#80](https://github.com/AksharP5/cohall/issues/80)) ([5b1e891](https://github.com/AksharP5/cohall/commit/5b1e891244c913d752b98015a28f30d6dd9b237a))
+* **deps:** update packages with published advisories ([#77](https://github.com/AksharP5/cohall/issues/77)) ([10801c9](https://github.com/AksharP5/cohall/commit/10801c9bc620b61da73b33480628ece4e0d1b583))
+* **pairing:** track the source of worker requests ([#79](https://github.com/AksharP5/cohall/issues/79)) ([5f383c6](https://github.com/AksharP5/cohall/commit/5f383c6ec8c5068417fcb7bdd915aed4976e71dc))
+* **provider:** finish cancellation before releasing the worker ([#74](https://github.com/AksharP5/cohall/issues/74)) ([a4ff068](https://github.com/AksharP5/cohall/commit/a4ff0684be9d1fbbc543d141537f2d0d5232559d))
+* **relay:** isolate failed device connections ([#72](https://github.com/AksharP5/cohall/issues/72)) ([035868d](https://github.com/AksharP5/cohall/commit/035868d72fcf5894ff8dcf71407951522bf66d1c))
+* **service:** retain the configured file and Node runtime ([#73](https://github.com/AksharP5/cohall/issues/73)) ([9811d1b](https://github.com/AksharP5/cohall/commit/9811d1b83bc9e8249f7f514c200967e110f7befc))
+* **tasks:** preserve continuity after reconnects ([#76](https://github.com/AksharP5/cohall/issues/76)) ([3b22717](https://github.com/AksharP5/cohall/commit/3b2271726316d6b6364fda3a8adbecaf69149342))
+* **windows:** launch providers, upgrades, and background workers reliably ([#78](https://github.com/AksharP5/cohall/issues/78)) ([6ccc4f8](https://github.com/AksharP5/cohall/commit/6ccc4f89550dcb22449d3035daa96af716c2558e))
+
 ## [0.6.1](https://github.com/AksharP5/cohall/compare/v0.6.0...v0.6.1) (2026-09-23)
 
 

package/README.md

@@ -122,6 +122,13 @@ unset pairing_token
 `cohall join` remains available for scripts that only want to exchange a
 pairing token and write configuration.
 
+Full-worker pairings associate both credentials with the same device. Once the
+worker registers, its client requests record the source device and automatic
+routing prefers an equally suitable peer. Older pairings keep working; pair the
+worker again to enable source attribution and that routing preference. Forgetting
+a device revokes both associated credentials. Client-only pairings have no worker
+identity.
+
 ### 3. Keep the device available
 
 ```bash
@@ -190,8 +197,59 @@ npx -y @akshar5/cohall wait <task-id> --timeout 1800
 npx -y @akshar5/cohall trace <task-id> --follow
 ```
 
+Completed tasks also appear in the sending client's inbox. This covers queued
+work and tasks that finish after a wait times out:
+
+```bash
+npx -y @akshar5/cohall inbox
+npx -y @akshar5/cohall status <task-id>
+npx -y @akshar5/cohall inbox ack <task-id>
+```
+
+The inbox shows short previews; `status` returns the full result. Acknowledge a
+task after handling it. Synchronous `delegate` calls acknowledge their own
+results automatically. The inbox shows up to 20 oldest entries and sets
+`hasMore` when more are waiting; acknowledge handled entries to reveal the rest.
+Each client credential has its own inbox, including
+client-only pairings. The relay keeps at most 1,000 completed tasks by default,
+so an old unacknowledged result can leave the inbox when history is pruned.
+Tasks created before the inbox was added have no inbox entry.
+
+Attach up to two explicit files to a coding task. Each file may be up to 256 KiB.
+The target receives them as temporary files and can return up to two files by
+writing them to the output directory named in its task prompt. List task files
+or download a file using the task ID:
+
+```bash
+cohall delegate --target @macbook --attach ./screenshot.png \
+  --prompt 'Inspect the screenshot and return a short report file.'
+cohall attachments <task-id>
+cohall download <task-id> report.txt --output ./report.txt
+```
+
+The `delegate` MCP tool accepts `attachment_paths`; `list_task_attachments` and
+`download_task_attachment` provide the same retrieval flow. Downloads require a
+new destination path and never overwrite a local file. When an input and output
+share a name, downloads select the output by default; pass `--direction input`
+(or the MCP `direction` argument) to retrieve the input. File bytes remain on the
+relay until the task is removed by its configured history limit. Upgrade the
+relay and target worker before sending attachments; older workers do not
+advertise attachment support. Named Grok Bots do not support file attachments.
+If a long result and output files exceed the 1 MiB transfer limit, the task
+completes with its text result and a notice that the files were omitted.
+
+`--timeout` accepts 5 to 86400 seconds and defaults to 900. It limits how long
+the command waits; the task continues after that. Invalid timeout values are
+rejected before any work is sent, including with `--no-wait`.
+
 Reuse the returned `thread_id` for follow-ups so the target resumes its provider
-session.
+session. Queued follow-ups pick up the preceding turn's session when they start,
+including after a worker restart.
+
+Delegated child tasks inherit their parent's thread. Cohall routes them away
+from unfinished ancestors using the same worker slot, and rejects an explicit
+target that would make them wait on an ancestor. A Bot can still delegate to
+Codex or a different Bot on its own computer.
 
 ## Talk to your Grok Bots
 
@@ -200,13 +258,22 @@ through the local Grok Bot gateway on their computer. It uses each Bot's current
 conversation, tools, and permissions. Grok Bot remains the agent responding;
 Codex is a separate provider that the Bot can delegate to.
 
-On the Grok Bot computer, configure its gateway file and restart the Cohall
-worker:
+For a new computer, follow [Grok Bot setup](docs/grok-bot.md). It covers
+Tailscale access, the suggested `tag:grokbot` identity, secure pairing, gateway
+configuration, and recovery on hosts without systemd. Pair the computer once;
+its Cohall worker discovers every named Bot there. Tailscale policies can
+select the computer by its tag; Cohall does not require one.
+
+On an already paired Grok Bot computer, configure its actual gateway file and
+restart the Cohall worker:
 
 ```bash
-cohall configure --grok-gateway "$HOME/sand-data/gateway.json" --providers codex,grok-bot
+test -r "$HOME/agent-data/gateway.json" &&
+  cohall configure --grok-gateway "$HOME/agent-data/gateway.json" --providers grok-bot
 ```
 
+The path is an example; check the file on that computer before using it. Add
+`codex` to the provider list only when Codex is installed and signed in there.
 The path can also be supplied as `COHALL_GROK_GATEWAY`. The gateway credential
 stays on that computer; clients discover Bots through the Cohall relay. Upgrade
 the relay, workers, and clients before enabling this provider. Restart
@@ -234,9 +301,13 @@ and `delegate` tools; the Bot target selects the provider automatically.
 A Cohall thread records the exchange and lets follow-ups find the same Bot.
 It does not create an isolated Grok Bot conversation: messages sent in the
 Grok Bot app share that Bot's history. Bot tasks use the Bot's own permissions
-and computer context, so omit `--workspace`. Queued Bot tasks can be cancelled;
-active Bot turns must be stopped in Grok Bot because the gateway cannot safely
-cancel a specific Cohall turn.
+and computer context, so omit `--workspace`. Queued Bot tasks that have never
+been dispatched can be cancelled; active Bot turns must be stopped in Grok Bot because
+the gateway cannot safely cancel a specific Cohall turn.
+A dispatched Bot request remains non-cancellable through Cohall if a disconnect
+or relay restart puts it back in the queue, even if its acceptance message was lost.
+When upgrading an older relay without dispatch records, outstanding Bot requests
+are conservatively treated as potentially dispatched.
 
 Cohall includes a local callback command in each Bot request. After finishing,
 the Bot hands its result back by running `cohall reply <task-id> --message-file
@@ -342,6 +413,7 @@ configuration.
 ## Documentation
 
 - [Installation, pairing, providers, and upgrades](docs/install.md)
+- [Grok Bot computer setup, Tailscale, and recovery](docs/grok-bot.md)
 - [Agent skill and MCP integrations](docs/integrations.md)
 - [Linux, macOS, and Windows services](docs/services.md)
 - [Contributing](CONTRIBUTING.md)