@vibe-assurance/cli 1.0.4 → 1.0.6

package/README.md

@@ -1,6 +1,6 @@
 # @vibe-assurance/cli
 
-Connect Claude Code to your Vibe Assurance governance platform.
+Connect AI coding agents to your Vibe Assurance governance platform via the Model Context Protocol (MCP).
 
 ## Installation
 
@@ -16,13 +16,13 @@ npm install -g @vibe-assurance/cli
    ```
    This opens your browser for authentication.
 
-2. **Configure Claude Code:**
+2. **Configure your MCP client:**
    ```bash
    vibe setup-claude
    ```
-   This adds the Vibe Assurance MCP server to your Claude Code configuration.
+   This adds the Vibe Assurance MCP server to your MCP client configuration.
 
-3. **Restart Claude Code** and start using governance tools!
+3. **Restart your AI agent** and start using governance tools!
 
 ## Usage
 
@@ -32,24 +32,39 @@ npm install -g @vibe-assurance/cli
 |---------|-------------|
 | `vibe login` | Authenticate with Vibe Assurance |
 | `vibe logout` | Clear stored credentials |
-| `vibe mcp-server` | Start the MCP server (used by Claude Code) |
-| `vibe setup-claude` | Configure Claude Code to use Vibe Assurance |
+| `vibe mcp-server` | Start the MCP server (used by AI coding agents) |
+| `vibe setup-claude` | Configure MCP client to use Vibe Assurance |
+| `vibe --version` | Show CLI version |
 
-### Available Tools in Claude Code
+### MCP Tools
 
-Once configured, Claude Code has access to these tools:
+Once configured, your AI coding agent has access to these tools:
+
+#### Roles (AI Analyst Prompts)
+
+| Tool | Description |
+|------|-------------|
+| `vibe_get_role` | Get an AI analyst role prompt by ID |
+| `vibe_list_roles` | List all available roles |
+| `vibe_update_role` | Update a role's system prompt |
+| `vibe_create_role` | Create a new custom role |
+
+#### Context & Templates
 
 | Tool | Description |
 |------|-------------|
-| `vibe_get_role` | Get an AI analyst role prompt |
-| `vibe_list_roles` | List available roles |
-| `vibe_get_context` | Get your governance context (CRs, risks, vulns) |
+| `vibe_get_context` | Get your governance context (CRs, risks, vulns, next CR ID) |
 | `vibe_get_template` | Get a document template |
 | `vibe_list_templates` | List available templates |
-| `vibe_store_artifact` | Store a created document |
+
+#### Artifacts (Governance Documents)
+
+| Tool | Description |
+|------|-------------|
+| `vibe_store_artifact` | Store a created document (CR, risk, vulnerability, etc.) |
 | `vibe_update_artifact` | Update an existing artifact |
 | `vibe_list_artifacts` | List your stored artifacts |
-| `vibe_get_artifact` | Get a specific artifact |
+| `vibe_get_artifact` | Get a specific artifact by ID |
 | `vibe_delete_artifact` | Delete an artifact |
 
 ### Example Session
@@ -57,7 +72,7 @@ Once configured, Claude Code has access to these tools:
 ```
 User: Create a change request for adding user authentication
 
-Claude: I'll help you create a change request. Let me get your context first.
+AI Agent: I'll help you create a change request. Let me get your context first.
 
 [Calls vibe_get_context]
 [Calls vibe_get_role("implementation-planner")]
@@ -66,12 +81,7 @@ Claude: I'll help you create a change request. Let me get your context first.
 Based on your governance context, your next CR ID is CR-2026-001.
 
 [Creates the CR documents...]
-
-Done! Would you like me to store this in Vibe Assurance?
-
-User: Yes
-
-Claude: [Calls vibe_store_artifact(...)]
+[Calls vibe_store_artifact(...)]
 
 Your CR-2026-001 has been stored! View it at:
 https://vibeassurance.app/governance/artifacts/CR-2026-001
@@ -103,8 +113,8 @@ If the system keychain is unavailable, credentials fall back to `~/.vibe/credent
 ## Requirements
 
 - **Node.js 18** or later
-- **Vibe Assurance account**
-- **Claude Code**
+- **Vibe Assurance account** - [Sign up](https://vibeassurance.app)
+- **MCP-compatible AI agent** (e.g., Claude Code, Gemini CLI, or any MCP client)
 
 ## Troubleshooting
 
@@ -115,7 +125,7 @@ Run `vibe login` to authenticate. If you see this error during MCP server startu
 ### MCP server not connecting
 
 1. Run `vibe setup-claude` again
-2. Restart Claude Code completely (not just reload)
+2. Restart your AI agent completely
 3. Check that `vibe` command is in your PATH
 
 ### "Port 38274 is already in use"
@@ -155,10 +165,7 @@ vibe logout
 rm -rf ~/.vibe/
 ```
 
-Then remove the MCP configuration from Claude Code:
-1. Open `~/.claude/mcp.json` (or your platform's config location)
-2. Remove the `vibeassurance` entry from `mcpServers`
-3. Restart Claude Code
+Then remove the MCP configuration from your AI agent's config file.
 
 ## Security
 
@@ -171,8 +178,8 @@ Then remove the MCP configuration from Claude Code:
 
 MIT
 
-## Related
+## Links
 
-- [Vibe Assurance](https://vibeassurance.app) - Governance platform
-- [Claude Code](https://claude.ai/code) - AI coding assistant
-- [MCP Protocol](https://modelcontextprotocol.io) - Model Context Protocol
+- [Vibe Assurance](https://vibeassurance.app) - AI Governance Platform
+- [MCP Protocol](https://modelcontextprotocol.io) - Model Context Protocol specification
+- [Documentation](https://agent-platform-prod.azurewebsites.net/docs-cli.html) - CLI setup guide

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@vibe-assurance/cli",
-  "version": "1.0.4",
+  "version": "1.0.6",
   "description": "Vibe Assurance CLI - Connect AI coding agents to your governance platform via MCP",
   "main": "src/index.js",
   "bin": {

package/src/config/credentials.js

@@ -90,7 +90,10 @@ async function deleteCredentials() {
 }
 
 /**
- * Check if credentials exist and are valid (not expired)
+ * Check if credentials exist and can be used (valid or refreshable)
+ * Returns true if:
+ * - Access token exists and is not expired, OR
+ * - Access token is expired but refresh token exists (will auto-refresh on API call)
  * @returns {Promise<boolean>}
  */
 async function hasValidCredentials() {
@@ -99,14 +102,19 @@ async function hasValidCredentials() {
     return false;
   }
 
-  // Check if token is expired (with 5 minute buffer)
+  // Check if access token is expired (with 5 minute buffer)
   if (creds.expiresAt) {
     const expiresAt = new Date(creds.expiresAt);
     const now = new Date();
     const bufferMs = 5 * 60 * 1000; // 5 minutes
 
     if (expiresAt.getTime() - bufferMs < now.getTime()) {
-      return false;
+      // Access token expired - check if we have a refresh token
+      // If we do, the API client will auto-refresh on first request
+      if (creds.refreshToken) {
+        return true; // Can refresh, so credentials are usable
+      }
+      return false; // No refresh token, truly expired
     }
   }
 

package/src/mcp/tools.js

@@ -50,6 +50,79 @@ const tools = [
     }
   },
 
+  {
+    name: 'vibe_update_role',
+    description: 'Update an AI analyst role\'s system prompt in Vibe Assurance. Use this to modify role instructions, add new guidance, or fix issues in role prompts.',
+    inputSchema: {
+      type: 'object',
+      properties: {
+        roleId: {
+          type: 'string',
+          description: 'Role ID to update (e.g., "implementation-planner", "security-auditor")'
+        },
+        systemPrompt: {
+          type: 'string',
+          description: 'The full updated system prompt content (markdown format). This should be the COMPLETE prompt, not a partial update.'
+        },
+        name: {
+          type: 'string',
+          description: 'Optional: Updated role name'
+        },
+        description: {
+          type: 'string',
+          description: 'Optional: Updated role description'
+        },
+        version: {
+          type: 'string',
+          description: 'Optional: New version number (e.g., "1.1.0")'
+        }
+      },
+      required: ['roleId', 'systemPrompt']
+    },
+    handler: async ({ roleId, ...updates }) => {
+      return await api.put(`/api/mcp/roles/${roleId}`, updates);
+    }
+  },
+
+  {
+    name: 'vibe_create_role',
+    description: 'Create a new AI analyst role in Vibe Assurance. Use this to add custom roles with specific instructions.',
+    inputSchema: {
+      type: 'object',
+      properties: {
+        roleId: {
+          type: 'string',
+          description: 'Unique role ID (lowercase, hyphenated, e.g., "custom-reviewer")'
+        },
+        name: {
+          type: 'string',
+          description: 'Display name for the role (e.g., "Custom Code Reviewer")'
+        },
+        description: {
+          type: 'string',
+          description: 'Brief description of what this role does'
+        },
+        systemPrompt: {
+          type: 'string',
+          description: 'The full system prompt content (markdown format)'
+        },
+        version: {
+          type: 'string',
+          description: 'Version number (default: "1.0.0")'
+        },
+        tier: {
+          type: 'string',
+          enum: ['free', 'starter', 'pro', 'agency', 'enterprise'],
+          description: 'Access tier (default: "free")'
+        }
+      },
+      required: ['roleId', 'name', 'systemPrompt']
+    },
+    handler: async (params) => {
+      return await api.post('/api/mcp/roles', params);
+    }
+  },
+
   {
     name: 'vibe_get_context',
     description: 'Get your current governance context including existing CRs, open risks, vulnerabilities, and the next available CR ID. Use this before creating new CRs to ensure proper ID sequencing.',