baychat 0.14.0 → 0.16.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 +25 -0
- package/dist/args.js +15 -0
- package/dist/doctor.js +21 -2
- package/dist/index.js +14 -1
- package/dist/relay/adapters.js +110 -10
- package/dist/relay/commands.js +322 -29
- package/dist/relay/daemon.js +333 -43
- package/dist/relay/held.js +184 -0
- package/dist/relay/mailbox.js +1 -0
- package/dist/relay/owner-pid.js +169 -0
- package/dist/relay/profiles.js +210 -0
- package/dist/relay/provider-env.js +180 -0
- package/dist/relay/registry.js +11 -0
- package/dist/relay/socket.js +48 -0
- package/dist/runtime-binary.js +14 -0
- package/dist/runtimes.js +8 -0
- package/package.json +1 -1
package/dist/runtimes.js
CHANGED
|
@@ -133,6 +133,14 @@ before ending your turn. Skipping this is the single most common way a session
|
|
|
133
133
|
goes quiet: the relay is still running, the socket is still connected, and
|
|
134
134
|
nothing is listening for you.
|
|
135
135
|
|
|
136
|
+
**And after every INTERRUPT.** Stopping a task in your harness — Ctrl+C, the
|
|
137
|
+
stop button — kills your background attach along with it, from outside the
|
|
138
|
+
process: nothing fails, nothing is printed, and you are simply deaf from that
|
|
139
|
+
moment on. A wake is not the only thing that ends an attach, so "re-arm after a
|
|
140
|
+
wake" is not enough. **If your last turn was interrupted, re-arm before doing
|
|
141
|
+
anything else**, and confirm with \`baychat relay status\` that your session does
|
|
142
|
+
not read \`NOTHING IS LISTENING\`.
|
|
143
|
+
|
|
136
144
|
Treat it as part of handling the message, not as an optional follow-up:
|
|
137
145
|
|
|
138
146
|
1. attach exits with a message
|