@akshar5/cohall 0.6.2 → 0.8.0

package/CHANGELOG.md

@@ -1,5 +1,20 @@
 # Changelog
 
+## [0.8.0](https://github.com/AksharP5/cohall/compare/v0.7.0...v0.8.0) (2026-09-27)
+
+
+### Features
+
+* **doctor:** verify MCP server exposes tools ([#89](https://github.com/AksharP5/cohall/issues/89)) ([bee2abc](https://github.com/AksharP5/cohall/commit/bee2abcf64bd5715a88c560d07b8515455cd90d1))
+
+## [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)
 
 

package/README.md

@@ -197,6 +197,47 @@ 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`.
@@ -217,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
@@ -363,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)