@paigy/harness 0.3.29 → 0.3.31
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/README.md +5 -5
- package/dist/cli.js +412 -68
- package/dist/main.js +415 -71
- package/package.json +1 -1
package/README.md
CHANGED
|
@@ -34,13 +34,13 @@ The point isn't notifications, it's a conversation with an agent that happens to
|
|
|
34
34
|
running on your laptop. Both directions close (`paigy/conversation.ts`):
|
|
35
35
|
|
|
36
36
|
- **Answering.** The agent asks through Paigy's `contact` — its only channel to you; the
|
|
37
|
-
harness never relays its terminal output (`companion.md` Part 4, one channel) → your
|
|
37
|
+
harness never relays its terminal output (`docs/clients/desktop/companion.md` Part 4, one channel) → your
|
|
38
38
|
reply lands on its Goal and goes straight back into stdin as the next turn. Without this
|
|
39
39
|
the loop is one-directional and dies at the first idle.
|
|
40
40
|
- **Initiating.** You say something unprompted from your phone → it arrives on the agent's
|
|
41
41
|
Goal → same stdin. You never have to wait to be asked. A Claude agent in the middle of a task
|
|
42
42
|
sees your words right after its next tool call, and gets them again as its next turn
|
|
43
|
-
(`companion.md` Part 4, words reach a running turn).
|
|
43
|
+
(`docs/clients/desktop/companion.md` Part 4, words reach a running turn).
|
|
44
44
|
|
|
45
45
|
Answers are read out of whatever shape they arrive in (`spokenText`) — a tapped option,
|
|
46
46
|
a spoken sentence, a whole call log — because the words are what the agent needs, not
|
|
@@ -264,7 +264,7 @@ node apps/desktop/dist/cli.js --harness codex --cwd ~/repo "fix the flaky test"
|
|
|
264
264
|
node apps/desktop/dist/cli.js host --grant ~/projects # standby, launchable from the phone
|
|
265
265
|
```
|
|
266
266
|
|
|
267
|
-
The window deliberately has NO run form — launching moved to the phone (companion.md).
|
|
267
|
+
The window deliberately has NO run form — launching moved to the phone (docs/clients/desktop/companion.md).
|
|
268
268
|
It shows pairing, the party, the broker's card and queue, the doctor, the workspace
|
|
269
269
|
allow-list, a Stop button, and the log.
|
|
270
270
|
|
|
@@ -304,7 +304,7 @@ LAST, after the hooks are gone.
|
|
|
304
304
|
frame is skipped, never fatal. If mirroring goes quiet after a CLI update, re-verify
|
|
305
305
|
the frame names in the driver doc comments first. An adapter can also leave a prompt
|
|
306
306
|
unanswered for good (claude-agent-acp#1145); the driver cancels one after a long quiet
|
|
307
|
-
with no tool running (`companion.md` Part 4, one way in).
|
|
307
|
+
with no tool running (`docs/clients/desktop/companion.md` Part 4, one way in).
|
|
308
308
|
- **Auth probes are vendor commands** (`claude auth status`, `codex login status`) and
|
|
309
309
|
can drift with CLI releases; a probe failure reads as "needs login", so drift shows
|
|
310
310
|
up as a nagging hint, not a broken start.
|
|
@@ -317,4 +317,4 @@ LAST, after the hooks are gone.
|
|
|
317
317
|
- **The host service IS the daemon** (`paigy-harness service`, launchd, KeepAlive) —
|
|
318
318
|
it claims phone launches and runs sessions. The WAKE channel for terminal-agent
|
|
319
319
|
replies still belongs to `paigy-listen` + `PAIGY_ON_WAKE` (#486); spawn-on-wake
|
|
320
|
-
needs the slot-lease design in companion.md before it auto-wires.
|
|
320
|
+
needs the slot-lease design in docs/clients/desktop/companion.md before it auto-wires.
|