sessionpipe 0.6.1 → 0.7.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/README.md +16 -1
- package/dist/cli.js +1819 -1223
- package/dist/cli.js.map +4 -4
- package/dist/control/aliases.d.ts +15 -0
- package/dist/control/aliases.d.ts.map +1 -0
- package/dist/control/cli.d.ts.map +1 -1
- package/dist/control/daemon.d.ts +50 -10
- package/dist/control/daemon.d.ts.map +1 -1
- package/dist/control/pair.d.ts +2 -0
- package/dist/control/pair.d.ts.map +1 -1
- package/dist/control/route.d.ts +5 -2
- package/dist/control/route.d.ts.map +1 -1
- package/dist/hook.js +1 -1
- package/dist/index.js +69 -41
- package/dist/index.js.map +4 -4
- package/dist/run.d.ts.map +1 -1
- package/dist/worker.js +73 -45
- package/dist/worker.js.map +4 -4
- package/package.json +1 -1
package/README.md
CHANGED
|
@@ -25,7 +25,7 @@ No telemetry. Secrets never leave (`secrets@1` runs above tier 0, always). Your
|
|
|
25
25
|
server or none. Pre-release: the reference receiver is still being built; see the
|
|
26
26
|
[roadmap](https://github.com/micmmakarov/sessionpipe/blob/main/ROADMAP.md).
|
|
27
27
|
|
|
28
|
-
## Control: messages to your sessions (M6
|
|
28
|
+
## Control: messages to your sessions (M6: Claude Code, Codex, Antigravity)
|
|
29
29
|
|
|
30
30
|
A receiver that lists `control` can carry a message from your phone to a session on
|
|
31
31
|
this machine. It is signed on your device and **checked here**, against a key you
|
|
@@ -68,6 +68,21 @@ comes first wins. Nothing is ever auto-allowed. Safe mode (the default) runs hea
|
|
|
68
68
|
turns with `--permission-mode dontAsk`, so nothing that needs approval runs while
|
|
69
69
|
you're away.
|
|
70
70
|
|
|
71
|
+
Codex and Antigravity sessions are reached headlessly too, when `codex` or `agy` is
|
|
72
|
+
installed (the daemon looks on PATH, beside its own Node, in `~/.local/bin`, or where
|
|
73
|
+
`SESSIONPIPE_CODEX` / `SESSIONPIPE_AGY` point). A new session is
|
|
74
|
+
`codex exec --json -C <folder>` or `agy -p … --output-format stream-json`; the next
|
|
75
|
+
message is `codex exec resume <thread>` or `agy --conversation <id>`. Safe mode runs
|
|
76
|
+
Codex in its `workspace-write` sandbox and agy with no permission flag (it denies, and
|
|
77
|
+
the reply lists, what it wasn't allowed to do); auto mode passes `--approve-for-me` /
|
|
78
|
+
`--mode accept-edits`. The bypass flags are never passed. Both CLIs pick a new
|
|
79
|
+
session's id themselves, so the daemon keeps the one your start named: it records the
|
|
80
|
+
pair in `~/.local/state/sessionpipe/control/aliases.json`, and your receiver keeps
|
|
81
|
+
seeing one session under one id. A message to a Codex session someone has open (its
|
|
82
|
+
rollout written in the last 90 seconds) is acked `unsupported` rather than resumed beside them.
|
|
83
|
+
Before a Codex run the daemon checks `codex login status` (or `CODEX_API_KEY`) and says
|
|
84
|
+
`codex login --device-auth` if it isn't signed in.
|
|
85
|
+
|
|
71
86
|
## Updates
|
|
72
87
|
|
|
73
88
|
The control daemon keeps its own copy current. About a minute after it starts, and then
|