@akshar5/cohall 0.6.1 → 0.6.2
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/CHANGELOG.md +17 -0
- package/README.md +25 -4
- package/bin/cohall.js +205 -81
- package/bin/cohall.js.map +10 -10
- package/deploy/windows/install-device.ps1 +21 -2
- package/docs/install.md +1 -1
- package/docs/services.md +17 -4
- package/package.json +5 -3
package/CHANGELOG.md
CHANGED
|
@@ -1,5 +1,22 @@
|
|
|
1
1
|
# Changelog
|
|
2
2
|
|
|
3
|
+
## [0.6.2](https://github.com/AksharP5/cohall/compare/v0.6.1...v0.6.2) (2026-09-24)
|
|
4
|
+
|
|
5
|
+
|
|
6
|
+
### Bug Fixes
|
|
7
|
+
|
|
8
|
+
* **bot:** retain cancellation limits after uncertain dispatch ([#81](https://github.com/AksharP5/cohall/issues/81)) ([e324530](https://github.com/AksharP5/cohall/commit/e324530ee578bae7fd5a244a70daffa4304d8eb7))
|
|
9
|
+
* **cli:** reject invalid timeouts before sending work ([#70](https://github.com/AksharP5/cohall/issues/70)) ([bac67e9](https://github.com/AksharP5/cohall/commit/bac67e9a2dc8c9c460f2b5df7b882d098177c5ae))
|
|
10
|
+
* **config:** reject files as workspace roots ([#75](https://github.com/AksharP5/cohall/issues/75)) ([7b86305](https://github.com/AksharP5/cohall/commit/7b86305f36f68d264441c0d09fabbcbc23f457ae))
|
|
11
|
+
* **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))
|
|
12
|
+
* **deps:** update packages with published advisories ([#77](https://github.com/AksharP5/cohall/issues/77)) ([10801c9](https://github.com/AksharP5/cohall/commit/10801c9bc620b61da73b33480628ece4e0d1b583))
|
|
13
|
+
* **pairing:** track the source of worker requests ([#79](https://github.com/AksharP5/cohall/issues/79)) ([5f383c6](https://github.com/AksharP5/cohall/commit/5f383c6ec8c5068417fcb7bdd915aed4976e71dc))
|
|
14
|
+
* **provider:** finish cancellation before releasing the worker ([#74](https://github.com/AksharP5/cohall/issues/74)) ([a4ff068](https://github.com/AksharP5/cohall/commit/a4ff0684be9d1fbbc543d141537f2d0d5232559d))
|
|
15
|
+
* **relay:** isolate failed device connections ([#72](https://github.com/AksharP5/cohall/issues/72)) ([035868d](https://github.com/AksharP5/cohall/commit/035868d72fcf5894ff8dcf71407951522bf66d1c))
|
|
16
|
+
* **service:** retain the configured file and Node runtime ([#73](https://github.com/AksharP5/cohall/issues/73)) ([9811d1b](https://github.com/AksharP5/cohall/commit/9811d1b83bc9e8249f7f514c200967e110f7befc))
|
|
17
|
+
* **tasks:** preserve continuity after reconnects ([#76](https://github.com/AksharP5/cohall/issues/76)) ([3b22717](https://github.com/AksharP5/cohall/commit/3b2271726316d6b6364fda3a8adbecaf69149342))
|
|
18
|
+
* **windows:** launch providers, upgrades, and background workers reliably ([#78](https://github.com/AksharP5/cohall/issues/78)) ([6ccc4f8](https://github.com/AksharP5/cohall/commit/6ccc4f89550dcb22449d3035daa96af716c2558e))
|
|
19
|
+
|
|
3
20
|
## [0.6.1](https://github.com/AksharP5/cohall/compare/v0.6.0...v0.6.1) (2026-09-23)
|
|
4
21
|
|
|
5
22
|
|
package/README.md
CHANGED
|
@@ -122,6 +122,13 @@ unset pairing_token
|
|
|
122
122
|
`cohall join` remains available for scripts that only want to exchange a
|
|
123
123
|
pairing token and write configuration.
|
|
124
124
|
|
|
125
|
+
Full-worker pairings associate both credentials with the same device. Once the
|
|
126
|
+
worker registers, its client requests record the source device and automatic
|
|
127
|
+
routing prefers an equally suitable peer. Older pairings keep working; pair the
|
|
128
|
+
worker again to enable source attribution and that routing preference. Forgetting
|
|
129
|
+
a device revokes both associated credentials. Client-only pairings have no worker
|
|
130
|
+
identity.
|
|
131
|
+
|
|
125
132
|
### 3. Keep the device available
|
|
126
133
|
|
|
127
134
|
```bash
|
|
@@ -190,8 +197,18 @@ npx -y @akshar5/cohall wait <task-id> --timeout 1800
|
|
|
190
197
|
npx -y @akshar5/cohall trace <task-id> --follow
|
|
191
198
|
```
|
|
192
199
|
|
|
200
|
+
`--timeout` accepts 5 to 86400 seconds and defaults to 900. It limits how long
|
|
201
|
+
the command waits; the task continues after that. Invalid timeout values are
|
|
202
|
+
rejected before any work is sent, including with `--no-wait`.
|
|
203
|
+
|
|
193
204
|
Reuse the returned `thread_id` for follow-ups so the target resumes its provider
|
|
194
|
-
session.
|
|
205
|
+
session. Queued follow-ups pick up the preceding turn's session when they start,
|
|
206
|
+
including after a worker restart.
|
|
207
|
+
|
|
208
|
+
Delegated child tasks inherit their parent's thread. Cohall routes them away
|
|
209
|
+
from unfinished ancestors using the same worker slot, and rejects an explicit
|
|
210
|
+
target that would make them wait on an ancestor. A Bot can still delegate to
|
|
211
|
+
Codex or a different Bot on its own computer.
|
|
195
212
|
|
|
196
213
|
## Talk to your Grok Bots
|
|
197
214
|
|
|
@@ -234,9 +251,13 @@ and `delegate` tools; the Bot target selects the provider automatically.
|
|
|
234
251
|
A Cohall thread records the exchange and lets follow-ups find the same Bot.
|
|
235
252
|
It does not create an isolated Grok Bot conversation: messages sent in the
|
|
236
253
|
Grok Bot app share that Bot's history. Bot tasks use the Bot's own permissions
|
|
237
|
-
and computer context, so omit `--workspace`. Queued Bot tasks
|
|
238
|
-
active Bot turns must be stopped in Grok Bot because
|
|
239
|
-
cancel a specific Cohall turn.
|
|
254
|
+
and computer context, so omit `--workspace`. Queued Bot tasks that have never
|
|
255
|
+
been dispatched can be cancelled; active Bot turns must be stopped in Grok Bot because
|
|
256
|
+
the gateway cannot safely cancel a specific Cohall turn.
|
|
257
|
+
A dispatched Bot request remains non-cancellable through Cohall if a disconnect
|
|
258
|
+
or relay restart puts it back in the queue, even if its acceptance message was lost.
|
|
259
|
+
When upgrading an older relay without dispatch records, outstanding Bot requests
|
|
260
|
+
are conservatively treated as potentially dispatched.
|
|
240
261
|
|
|
241
262
|
Cohall includes a local callback command in each Bot request. After finishing,
|
|
242
263
|
the Bot hands its result back by running `cohall reply <task-id> --message-file
|