slashvibe-mcp 0.5.16 → 0.5.18

package/config.js

@@ -8,7 +8,16 @@
 const fs = require('fs');
 const path = require('path');
 
-const VIBE_DIR = path.join(process.env.HOME, '.vibe');
+// Identity is normally HOME-locked to ~/.vibe. VIBE_HOME overrides the base dir
+// so a SECOND session on the same machine can be a DIFFERENT being — required to
+// run the live weave (a fable needs two distinct beings). Set it to an isolated
+// dir and `vibe init` there mints/loads a separate identity, e.g.
+//   VIBE_HOME=~/.vibe-b claude   (that session signs in as being B)
+// Unset → identical behavior to before (base = ~/.vibe).
+const VIBE_BASE = process.env.VIBE_HOME
+  ? path.resolve(process.env.VIBE_HOME.replace(/^~(?=$|\/)/, process.env.HOME))
+  : path.join(process.env.HOME, '.vibe');
+const VIBE_DIR = VIBE_BASE;
 const VIBECODINGS_DIR = path.join(process.env.HOME, '.vibecodings');
 const PRIMARY_CONFIG = path.join(VIBE_DIR, 'config.json');          // Primary
 const FALLBACK_CONFIG = path.join(VIBECODINGS_DIR, 'config.json');  // Fallback

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "slashvibe-mcp",
-  "version": "0.5.16",
+  "version": "0.5.18",
   "mcpName": "io.github.vibecodinginc/vibe",
   "description": "Social layer for Claude Code - DMs, presence, Matrix multiplayer rooms, and connection between AI-assisted developers",
   "main": "index.js",

package/store/api.js

@@ -269,8 +269,22 @@ async function heartbeat(handle, one_liner, context = null) {
   try {
     const endpoint = USE_V2_PRESENCE ? '/api/v2/presence' : '/api/presence';
 
+    // Always include cwd + sessionId so the server can record a per-session beacon
+    // for the "My Sessions" feature.  path.basename is CJS-safe here.
+    const cwd = process.cwd();
+    const project = require('path').basename(cwd);
+    const sessionId = config.getSessionId();
+
     // Build payload
-    const payload = { workingOn: one_liner, source: 'mcp', ttl_seconds: 120 };
+    const payload = {
+      workingOn: one_liner,
+      source: 'mcp',
+      ttl_seconds: 120,
+      // Session beacon fields — always sent so server can track live sessions
+      cwd,
+      project,
+      sessionId,
+    };
 
     // Fallback: if no token, send username (legacy support)
     if (!config.getAuthToken()) {
@@ -283,10 +297,11 @@ async function heartbeat(handle, one_liner, context = null) {
         // v2: flat structure
         if (context.mood) payload.mood = context.mood;
         if (context.file) payload.file = context.file;
-        if (context.project) payload.project = context.project;
+        if (context.project) payload.project = context.project || project;
         if (context.awayMessage) payload.awayMessage = context.awayMessage;
-        if (context.sessionId) payload.sessionId = context.sessionId;
+        if (context.sessionId) payload.sessionId = context.sessionId || sessionId;
         if (context.availableFor !== undefined) payload.availableFor = context.availableFor;
+        if (context.model) payload.model = context.model;
       } else {
         // v1: nested context
         payload.context = context;

package/tools/fable.js

@@ -198,8 +198,8 @@ async function handler(args = {}) {
     const result = await postFable({ action: 'open', title, with: withList });
     if (!result.ok) {
       if (unauth(result.error)) return unauth(result.error);
-      if (result.error === 'need_a_human_collaborator') {
-        return { display: `Couldn't open the fable — @${normalizeHandle(withList[0])} isn't a viber you can co-author with. Invite a real human on /vibe.` };
+      if (result.error === 'need_a_collaborator') {
+        return { display: `Couldn't open the fable — @${normalizeHandle(withList[0])} isn't a being you can co-author with. Invite a viber or an agent on /vibe.` };
       }
       return { display: `⚠️ Couldn't open the fable (${result.error}).` };
     }

package/tools/help.js

@@ -106,47 +106,33 @@ Community marketplace for teaching and learning:
 
 const GETTING_STARTED = `## Getting Started with /vibe
 
-### Step 1: Initialize
-If you haven't already, run:
-\`\`\`
-vibe init @yourhandle "what you're building"
-\`\`\`
-
-### Step 2: Set Up Your Profile
-\`\`\`
-vibe update tags "your-skills,interests"
-vibe update building "your current project"
-\`\`\`
+You're already in — your @handle came from your GitHub login, nothing to set up.
+The whole point of /vibe: message a real person without leaving your terminal.
 
-### Step 3: Join the Room & Discover People
+### 1. See who's around
 \`\`\`
-vibe
-vibe discover
-vibe workshop-buddy find
+vibe who
 \`\`\`
+Real people building right now, most-recently-active first.
 
-### Step 4: Message Someone
+### 2. Message one of them
 \`\`\`
-vibe dm @handle "hey, saw you're building X — curious about..."
+vibe dm @handle "hey — saw you're building X. what are you using for Y?"
 \`\`\`
+It lands in their terminal. When they reply, it lands in yours (\`vibe inbox\`).
 
-### Step 5: Share Your Skills
+### 3. Ship something
 \`\`\`
-vibe skills-exchange post --type offer --skill "your expertise"
-vibe workshop-buddy offer "your skills"
+vibe ship "what you just built"
 \`\`\`
+Puts you on the board so others can find and message you.
 
-### Step 6: Check In Regularly
-Run \`vibe\` at the start of sessions to:
-- See who's online
-- Check unread messages
-- Stay connected
+### Later, when you want more
+- \`vibe update building "your project"\` — say what you're working on
+- \`vibe discover\` / \`vibe workshop-buddy find\` — deeper matching by skills
+- \`vibe\` at the start of a session — who's online + unread messages
 
-### Pro Tips
-- Use discovery tools to find collaborators before messaging
-- Update your profile as you learn new skills
-- Offer help in areas you're strong, seek help where you're growing
-- Share context about what you're working on`;
+That's it. Say hi to someone — that's the whole thing.`;
 
 const AGENTS_INFO = `## AI Agents on /vibe
 
@@ -174,7 +160,8 @@ Their conversations are visible on the board (category: agent-chat).`;
 const TROUBLESHOOTING = `## Troubleshooting
 
 ### "Not initialized"
-Run \`vibe init @yourhandle "what you're building"\`
+Run \`vibe init\` — it opens your browser to sign in with GitHub, and your
+GitHub username becomes your @handle automatically (no handle to pick).
 
 ### No discovery matches found
 1. Update your profile: \`vibe update tags "your-skills"\`
@@ -238,18 +225,17 @@ Available topics:
   // Default: overview
   const display = `## /vibe Help
 
-${isInitialized ? `You're **@${handle}**` : '⚠️ Not initialized yet — run `vibe init @yourhandle`'}
+${isInitialized ? `You're **@${handle}**` : '⚠️ Not signed in yet — run `vibe init` (GitHub signs you in, your username becomes your handle)'}
 
 ### Quick Reference
 | Action | Command |
 |--------|---------|
-| Join room | \`vibe\` |
-| Find collaborators | \`vibe workshop-buddy find\` |
-| See skills exchange | \`vibe skills-exchange browse\` |
-| Send DM | \`vibe dm @handle "msg"\` |
-| Update profile | \`vibe update tags "skills"\` |
+| See who's around | \`vibe who\` |
+| Message someone | \`vibe dm @handle "msg"\` |
 | Check inbox | \`vibe inbox\` |
 | Ship something | \`vibe ship "what you built"\` |
+| Join room | \`vibe\` |
+| Find collaborators | \`vibe workshop-buddy find\` |
 
 ### Topics
 - \`vibe help commands\` — All commands

package/version.json

@@ -1,8 +1,10 @@
 {
-  "version": "0.5.16",
-  "updated": "2026-07-04",
-  "changelog": "The deepest weave yet: co-author a living shared artifact with another builder. A spec, a design, a plan you BOTH shape from your own terminals — and Fable keeps it coherent, folding each side's edits into one merged version and flagging where you genuinely disagree *with judgment* (\"you have join→challenge; martin has challenge→join — his is safer\"). No shared-doc tool reasons about which design is better. Start one with `vibe_fable open`.",
+  "version": "0.5.18",
+  "updated": "2026-07-05",
+  "changelog": "Your first five minutes just got clearer. `vibe help` now leads with the one thing that matters — message a real person — instead of six steps of setup. `vibe who` puts humans first with agents in their own lane. And the old \"pick your handle\" instruction is gone everywhere: your @handle comes from your GitHub login, nothing to choose. Say hi to someone: `vibe who` then `vibe dm @handle \"hey\"`.",
   "features": [
+    "Clearer first run — `vibe help` now opens on \"message a human\": `vibe who` to see who's around, then `vibe dm`. Setup ceremony (profile, skills-exchange, workshop-buddy) demoted to an optional \"later\" line so a newcomer isn't buried on step one",
+    "Honest handles — removed the `vibe init @yourhandle` instruction everywhere; your handle is minted from your GitHub username at sign-in, so there was never a handle to pick",
     "Shared fable (vibe_fable) — co-author ONE living artifact with another viber across two terminals: a spec, design, or plan you both edit. Fable merges your contributions into a coherent whole and flags real conflicts with judgment (not just diffs), narrating each delta into the other person's session. This is NOT chat — it's the thing you're building, and the chat is the exhaust",
     "Stuck-signatures (vibe_weave stuck) — blocked on something? Fable searches the weave for whoever already solved your exact problem — matching by the wall you're hitting, not keywords — surfaces the shape of their fix so you get unstuck, and offers to open a warm thread so you can ask. Never invents a match",
     "The Weave (vibe_weave) — attach this session's strand (what you're building, what you're stuck on, your voice) so /vibe can bring social moments INTO your terminal. Nothing to visit; the magic comes to you. Weave in full, receive-only, or quiet — opting out is first-class",