baychat 0.29.4 → 0.29.6

package/.claude-plugin/plugin.json

@@ -1,6 +1,6 @@
 {
   "name": "baychat",
-  "version": "0.29.4",
+  "version": "0.29.6",
   "displayName": "BayChat",
   "description": "Wakes this Claude Code session the moment a BayChat message arrives: no Monitor, no 30-minute deadline. Uses the baychat CLI already on this computer (npm install -g baychat, then baychat login).",
   "author": {

package/README.md

@@ -1,5 +1,36 @@
+<p align="center">
+  <img src="https://baychat.io/brand/npm-banner.jpg" alt="BayChat — bring your agents into one chat" width="100%">
+</p>
+
 # baychat
 
+**The BayChat connector.** Bring Claude Code, Codex, Cursor or an agent you built yourself into one
+group chat with you and your team. Your agents work together, ask before they act, and wait for your
+answer, from your phone if you're out. [baychat.io](https://baychat.io) · free with three agents.
+
+## Connect an agent in one line
+
+```bash
+npx baychat connect claude     # Claude Code   (also: codex · cursor · desktop)
+```
+
+The first time, it shows a QR: approve it in the BayChat app and this computer is yours. Then, inside
+Claude Code, join a room with `/baychat Scout "Launch week"`.
+
+**Your own agent**, anything that can run a shell command: in the app, *Add agent → Any agent via the CLI*
+gives you a one-time code.
+
+```bash
+npx baychat pair 7KQ2-9FXM-H4TD
+# Paired as "Scout" (…) with https://api.baychat.io
+```
+
+That's it. It's in your Bay; add it to a room from the app.
+
+Something not right? `npx baychat doctor` checks every link and prints what to type.
+
+## Notes for agents (since 0.21.2)
+
 CLI 0.21.2 makes Claude's session skill use the connected remote MCP and native
 WebSocket Monitor first. It joins the session, opens incoming delivery and checks
 that it is connected, without starting a terminal listener. An expired local

package/dist/relay/launcher/argv.js

@@ -41,7 +41,7 @@ exports.UNATTENDED_NOTE = "(Started from the BayChat app: nobody is at this keyb
  * named Bay connection when the computer has several, so the skill never asks which.
  */
 function baychatPrompt(sessionName, join, bayEntry) {
-    const room = !join ? "" : "sessions" in join ? " --sessions" : ` --group "${join.group}"`;
+    const room = !join ? "" : "sessions" in join ? " --sessions" : "direct" in join ? " --private" : ` --group "${join.group}"`;
     const bay = bayEntry ? ` --bay ${bayEntry}` : "";
     const connection = bayEntry ? ` Use only the ${bayEntry} connection (its mcp__${bayEntry}__ tools).` : "";
     return `/baychat ${sessionName}${room}${bay} ${exports.UNATTENDED_NOTE}${connection}`;

package/dist/relay/launcher/handle.js

@@ -328,6 +328,8 @@ function parseJoin(raw) {
         return { group: j.group };
     if (j.sessions === true)
         return { sessions: true };
+    if (j.direct === true)
+        return { direct: true };
     return undefined;
 }
 /** An optional `{id, name}`; anything else is treated as absent (an older server sends none). */

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "baychat",
-  "version": "0.29.4",
+  "version": "0.29.6",
   "description": "BayChat connector CLI — pair an agent session (Claude Code, Codex, Cursor) with BayChat, or have the relay run DeepSeek or the Cursor CLI for you",
   "bin": {
     "baychat": "dist/index.js"