@akshar5/cohall 0.8.0 → 0.9.0
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 +14 -0
- package/README.md +19 -0
- package/bin/cohall.js +203 -26
- package/bin/cohall.js.map +13 -12
- package/docs/integrations.md +29 -0
- package/package.json +1 -1
package/docs/integrations.md
CHANGED
|
@@ -10,6 +10,18 @@ the sending client has not handled. Fetch a full result with `cohall status
|
|
|
10
10
|
`acknowledge_completion` to remove it from the inbox. A synchronous `delegate`
|
|
11
11
|
call acknowledges its result automatically.
|
|
12
12
|
|
|
13
|
+
Workers can report a brief milestone with `cohall progress --message "Running
|
|
14
|
+
tests"` or MCP `task_progress`. Both inherit the task ID during delegated work;
|
|
15
|
+
otherwise supply the task ID explicitly. Notes must be nonblank and at most
|
|
16
|
+
1024 UTF-8 bytes. Only the task's target device or relay owner may update a
|
|
17
|
+
running task. Use milestones, never logs or secrets.
|
|
18
|
+
|
|
19
|
+
`cohall status <task-id>`, `cohall trace <task-id> --follow`, and MCP `task_status`
|
|
20
|
+
and `task_trace` include the latest note and timestamp. Notes replace one another
|
|
21
|
+
and clear when work is requeued or finishes.
|
|
22
|
+
Reporting progress requires an updated relay; it does not change task status
|
|
23
|
+
or acknowledge a completion.
|
|
24
|
+
|
|
13
25
|
## CLI plus skill
|
|
14
26
|
|
|
15
27
|
```bash
|
|
@@ -27,6 +39,23 @@ With a client credential, `doctor` starts Cohall's MCP server and verifies that
|
|
|
27
39
|
it lists tools. This checks the local server; the agent host still needs a
|
|
28
40
|
working MCP configuration to load it.
|
|
29
41
|
|
|
42
|
+
A running MCP server checks its launched executable at most once per minute
|
|
43
|
+
when returning tool results. If that file changes to a different Cohall version,
|
|
44
|
+
the next checked result includes a notice to restart the Cohall MCP connection
|
|
45
|
+
in your agent host. Each detected version produces one notice; the tool's
|
|
46
|
+
normal result is preserved. The server does not restart an active session.
|
|
47
|
+
Version probes time out after two seconds and failed probes retry on a later
|
|
48
|
+
tool call. This detects changes to the launched file, including a replaced
|
|
49
|
+
symlink target. It does not check the npm registry or other installations. An
|
|
50
|
+
`npx` session using an unchanged cache path must be restarted to load a newer
|
|
51
|
+
package.
|
|
52
|
+
|
|
53
|
+
`doctor` also checks the client credential with an authenticated relay request.
|
|
54
|
+
The `client_authentication` result separates rejected credentials and relay
|
|
55
|
+
request failures from an offline device. `client_credential` reports only
|
|
56
|
+
whether a credential is configured. The authentication check is skipped when
|
|
57
|
+
the relay is unreachable or no client credential is configured.
|
|
58
|
+
|
|
30
59
|
Any other harness with shell access can invoke the CLI directly. No Cohall UI
|
|
31
60
|
extension is required.
|
|
32
61
|
|