@vibescope/mcp-server 0.4.1 → 0.4.3

package/dist/api-client.js

@@ -4,7 +4,11 @@
  * HTTP client for communicating with the Vibescope API.
  * All database operations are handled server-side through these endpoints.
  */
+import crypto from 'crypto';
 const DEFAULT_API_URL = 'https://vibescope.dev';
+// Stable instance ID for this process — persists across start_work_session calls
+// so the API can recognise reconnections after context clears
+const PROCESS_INSTANCE_ID = crypto.randomUUID();
 // Retry configuration defaults
 const DEFAULT_RETRY_STATUS_CODES = [429, 503, 504];
 const DEFAULT_MAX_RETRIES = 3;
@@ -133,7 +137,10 @@ export class VibescopeApiClient {
     }
     // Session endpoints
     async startSession(params) {
-        return this.request('POST', '/api/mcp/sessions/start', params);
+        return this.request('POST', '/api/mcp/sessions/start', {
+            ...params,
+            instance_id: PROCESS_INSTANCE_ID,
+        });
     }
     async heartbeat(sessionId, options) {
         return this.request('POST', '/api/mcp/sessions/heartbeat', {

package/dist/handlers/session.js

@@ -295,7 +295,7 @@ export const startWorkSession = async (args, ctx) => {
     // Task lifecycle rules
     agentRules.push('COMPLETE TASKS: Always call complete_task(task_id, summary, session_id) immediately after creating a PR. This is mandatory — it updates the dashboard and triggers validation.');
     agentRules.push('SESSION ID: Pass session_id on EVERY update_task and complete_task call. Without it, the dashboard shows "Agent" instead of your name.');
-    agentRules.push('STATUS UPDATES: Call update_agent_status(status_message: "Working on: TASK_TITLE") whenever you start or finish a task.');
+    agentRules.push(`STATUS UPDATES: Call update_agent_status(status_message: "Working on: TASK_TITLE", project_id: "${data.project?.id || ''}", agent_name: "${result.persona || ''}") whenever you start or finish a task.`);
     agentRules.push('TRACK PROGRESS: Call update_task with progress_percentage (0-100) every 15-20% of task completion.');
     // Validation rules (dynamic based on project settings)
     if (data.project?.validation_required !== false) {

package/docs/TOOLS.md

@@ -2,7 +2,7 @@
 
 > Auto-generated from tool definitions. Do not edit manually.
 >
-> Generated: 2026-02-19
+> Generated: 2026-02-21
 >
 > Total tools: 159
 
@@ -33,7 +33,7 @@
 - [roles](#roles) - Agent role management (4 tools)
 - [file_locks](#file-locks) - File checkout/locking for multi-agent (6 tools)
 - [connectors](#connectors) - External integration connectors (7 tools)
-- [cloud_agents](#cloud-agents) - Cloud agent management and cleanup (2 tools)
+- [cloud_agents](#cloud-agents) - Cloud agent management and cleanup (3 tools)
 - [chat](#chat) - Project-wide chat channel for agent and user communication (2 tools)
 - [version](#version) - MCP server version management and updates (2 tools)
 
@@ -2416,6 +2416,34 @@ Get event history for a connector or project. Shows delivery status and errors.
 
 *Cloud agent management and cleanup*
 
+### update_agent_status
+
+Report what you're currently doing. This updates the status message shown on the dashboard.
+
+Call this at key milestones during boot and work:
+
+- "Installing dependencies..."
+
+- "Running start_work_session..."
+
+- "Working on: <task title>"
+
+- "Running tests..."
+
+- "Committing changes..."
+
+Keep messages short (under 80 chars). The dashboard shows this in real-time.
+
+**Parameters:**
+
+| Parameter | Type | Required | Description |
+|-----------|------|----------|-------------|
+| `status_message` | `string` | Yes | Short status message to display on dashboard (max 80 chars) |
+| `project_id` | `string` | No | Project UUID (optional if session has project context) |
+| `agent_name` | `string` | No | Agent name (used to find the spawned_agents record) |
+
+---
+
 ### cleanup_stale_cloud_agents
 
 Clean up stale cloud agents that failed to start or lost connection.
@@ -2515,35 +2543,3 @@ Update the Vibescope MCP server to the latest version. Runs npm install to fetch
 | `global` | `boolean` | No | If true, update the global installation (npm install -g). If false, update locally. Default: true. |
 
 ---
-
-## Uncategorized
-
-*Tools not yet assigned to a category*
-
-### update_agent_status
-
-Report what you're currently doing. This updates the status message shown on the dashboard.
-
-Call this at key milestones during boot and work:
-
-- "Installing dependencies..."
-
-- "Running start_work_session..."
-
-- "Working on: <task title>"
-
-- "Running tests..."
-
-- "Committing changes..."
-
-Keep messages short (under 80 chars). The dashboard shows this in real-time.
-
-**Parameters:**
-
-| Parameter | Type | Required | Description |
-|-----------|------|----------|-------------|
-| `status_message` | `string` | Yes | Short status message to display on dashboard (max 80 chars) |
-| `project_id` | `string` | No | Project UUID (optional if session has project context) |
-| `agent_name` | `string` | No | Agent name (used to find the spawned_agents record) |
-
----

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@vibescope/mcp-server",
-  "version": "0.4.1",
+  "version": "0.4.3",
   "description": "MCP server for Vibescope - AI project tracking tools",
   "type": "module",
   "main": "dist/index.js",

package/src/api-client.ts

@@ -5,8 +5,14 @@
  * All database operations are handled server-side through these endpoints.
  */
 
+import crypto from 'crypto';
+
 const DEFAULT_API_URL = 'https://vibescope.dev';
 
+// Stable instance ID for this process — persists across start_work_session calls
+// so the API can recognise reconnections after context clears
+const PROCESS_INSTANCE_ID = crypto.randomUUID();
+
 // Retry configuration defaults
 const DEFAULT_RETRY_STATUS_CODES = [429, 503, 504];
 const DEFAULT_MAX_RETRIES = 3;
@@ -282,7 +288,10 @@ export class VibescopeApiClient {
 		next_action?: string;
 		error?: string;
 	}>> {
-		return this.request('POST', '/api/mcp/sessions/start', params);
+		return this.request('POST', '/api/mcp/sessions/start', {
+			...params,
+			instance_id: PROCESS_INSTANCE_ID,
+		});
 	}
 
 	async heartbeat(sessionId: string, options?: {

package/src/handlers/session.ts

@@ -341,7 +341,7 @@ export const startWorkSession: Handler = async (args, ctx) => {
 	// Task lifecycle rules
 	agentRules.push('COMPLETE TASKS: Always call complete_task(task_id, summary, session_id) immediately after creating a PR. This is mandatory — it updates the dashboard and triggers validation.');
 	agentRules.push('SESSION ID: Pass session_id on EVERY update_task and complete_task call. Without it, the dashboard shows "Agent" instead of your name.');
-	agentRules.push('STATUS UPDATES: Call update_agent_status(status_message: "Working on: TASK_TITLE") whenever you start or finish a task.');
+	agentRules.push(`STATUS UPDATES: Call update_agent_status(status_message: "Working on: TASK_TITLE", project_id: "${data.project?.id || ''}", agent_name: "${result.persona || ''}") whenever you start or finish a task.`);
 	agentRules.push('TRACK PROGRESS: Call update_task with progress_percentage (0-100) every 15-20% of task completion.');
 
 	// Validation rules (dynamic based on project settings)