@diffclarity/companion 0.3.1 → 0.4.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.
Files changed (3) hide show
  1. package/README.md +20 -3
  2. package/dist/main.js +20 -12
  3. package/package.json +1 -1
package/README.md CHANGED
@@ -10,9 +10,9 @@ npx @diffclarity/companion@latest connect
10
10
 
11
11
  It connects to DiffClarity at `https://diffclarity.com`. For another DiffClarity, such as a local stage or your own deployment, name it with `--origin`, as the review's Assistant panel shows (`npx @diffclarity/companion@latest connect --origin https://diffclarity.example`); `disconnect` takes it too. Leaving out `--origin` and naming `https://diffclarity.com` are the same, and use the same saved access.
12
12
 
13
- The first run opens your browser to allow the companion for one workspace. It then waits for questions from the review page's Ask tab and runs the agent you choose there, from an empty directory, with DiffClarity's tools as its only tools (Codex also keeps its own code execution, in its read-only sandbox). Keep it running while you review.
13
+ The first run opens your browser, where you tick each workspace the companion may answer in. It then waits for questions from the review page's Ask tab and runs the agent you choose there, from an empty directory, with DiffClarity's tools as its only tools (Codex also keeps its own code execution, in its read-only sandbox). Keep it running while you review.
14
14
 
15
- It prints each step. Once connected it says which workspace it answers for:
15
+ It prints each step. Once connected it says which workspace it answers in:
16
16
 
17
17
  ```text
18
18
  Found Claude Code 2.1.314, Codex 0.166.0.
@@ -26,7 +26,24 @@ In a terminal, it names its tab "DiffClarity companion" instead of "node", and a
26
26
 
27
27
  When it can't connect, it says which step failed and why, for example `DiffClarity didn't answer the connection within 20 s.` or `DiffClarity refused the connection (HTTP 401: …).`, then tries again after a pause that grows to a minute.
28
28
 
29
- A companion answers in the workspaces you allowed it in, each over its own connection. To allow it in another too, stop it, run this and choose that workspace in the browser; it then answers in all of them:
29
+ A companion allowed in several workspaces answers in each over its own connection, and each line it prints starts with its workspace (`[Acme] Connected…`); the terminal's tab names them too. At each start in a terminal it asks which to answer in this time, all ticked at first:
30
+
31
+ ```text
32
+ Answer in which workspaces this time?
33
+ › [x] Personal
34
+ [x] Acme
35
+ [ ] Better Off
36
+ ↑↓ move · space tick · a all or none · + allow it in more workspaces · enter connect · q stop
37
+ ```
38
+
39
+ For a script, name them instead, once for each, by name or id (`personal` is your own); nothing is asked. `--all-workspaces` answers in every one, as `connect` does when it can't ask (its output isn't a terminal, or in CI). `workspaces` lists them with their ids:
40
+
41
+ ```sh
42
+ npx @diffclarity/companion@latest connect --workspace Acme --workspace personal
43
+ npx @diffclarity/companion@latest workspaces
44
+ ```
45
+
46
+ To allow it in more workspaces, press `+` in the list, or run this; tick each in the browser, in one visit:
30
47
 
31
48
  ```sh
32
49
  npx @diffclarity/companion@latest connect --add-workspace