slashvibe-mcp 0.8.25 → 0.8.26

package/README.md

@@ -1,10 +1,9 @@
 # slashvibe-mcp
 
-Reach your collaborators from any coding session. Presence, DMs, and messages that wait across sessions
-between the people (and agents) you already work with — nobody has to be online at the
-same time.
+**Message people from Claude Code or Codex.**
 
-**Works in:** Claude Code, Codex, Cursor — anything that speaks MCP.
+Presence, DMs, and messages that wait across sessions, between the people (and agents)
+you already work with — nobody has to be online at the same time.
 
 ## Install — one command
 
@@ -12,15 +11,23 @@ same time.
 npx slashvibe-mcp
 ```
 
-That's the whole thing: it configures Claude Code, Codex, and Cursor in one run, opens
-GitHub to sign you in, and your GitHub username becomes your @handle. About 30 seconds.
+It configures your coding agent, opens GitHub to sign you in, and your GitHub username
+becomes your @handle. About 30 seconds. **Then restart your coding session** so it loads
+the /vibe server.
 
-**Then restart your coding agent** so it loads the /vibe MCP server. (Setup writes the
-config; the agent only picks up a new MCP server on start.) After the restart, run
-`vibe init` if you weren't signed in during setup.
+## Then talk normally
 
-Invited by someone? After setup and restart, say `vibe inbox` — their message is waiting.
-Reply and you're done; that's the whole onboarding.
+```
+show me who's on /vibe
+message @brightseth — what are you building?
+did anyone message me?
+```
+
+No commands to learn. Your coding agent routes those to /vibe. If it ever asks you to
+sign in, say `sign in to /vibe`.
+
+**Works in:** Claude Code and Codex. Setup also writes Cursor's config; Cursor is not part
+of the walked, proven path yet.
 
 ## Put waiting messages at the top of your next Claude session
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "slashvibe-mcp",
-  "version": "0.8.25",
+  "version": "0.8.26",
   "mcpName": "io.github.vibecodinginc/vibe",
   "description": "Presence + messaging for terminal coding agents (Claude Code, Codex, Cursor) — the /vibe kernel",
   "main": "index.js",

package/tools/inbox.js

@@ -248,7 +248,18 @@ async function handler(args) {
     };
   }
 
-  const threads = await store.getInbox(myHandle);
+  // A failed read is not an empty inbox. getInbox() flattens "nobody
+  // answered" into [] — and the tool then said "no messages yet", which every
+  // host repeated as "you're caught up" (routing corpus R02, 0/6). Keep the
+  // outcome, as vibe_start already does, and say what is actually known.
+  const read = await store.getInboxResult(myHandle);
+  if (read.ok !== true) {
+    return {
+      display: `⚠️ could not check your inbox (${read.error || 'unknown'}) — unread is unknown, not zero. Try again in a moment.`,
+      footer: 'minimal',
+    };
+  }
+  const threads = read.threads;
 
   // Check for guest session messages (multiplayer)
   let guestMessages = [];

package/version.json

@@ -1,11 +1,9 @@
 {
-  "version": "0.8.25",
-  "updated": "2026-09-02",
-  "changelog": "Waiting means their words. After you replied to someone, their next session could open with their own message echoed back as if it had just arrived; now a waiting message is always the other person's newest words. And handles keep their dashes — a GitHub login like synth-stan is looked up as written, so the thread opens instead of coming back empty.",
+  "version": "0.8.26",
+  "updated": "2026-09-04",
+  "changelog": "A failed read is not an empty inbox. When the inbox could not be reached, vibe_inbox said \"no messages yet\" and every host repeated it as \"you're caught up\" — six out of six runs in the Sep 4 routing corpus. Now it says what is actually known: could not check your inbox, unread is unknown, not zero. A real empty inbox still reads as empty.",
   "features": [
-    "A waiting message at session start is always the other person's newest message, never your own reply",
-    "Handles with dashes open the right thread",
-    "Long threads read from the end, and the startup check finishes inside its time budget"
+    "vibe_inbox reports a failed read as unknown, never as caught up (routing corpus R02)"
   ],
   "deprecated": [],
   "breaking": false,