@rembr/vscode 1.0.0 → 1.0.1

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@rembr/vscode",
-  "version": "1.0.0",
+  "version": "1.0.1",
   "description": "VS Code setup for REMBR RLM patterns - semantic memory for AI agents with GitHub Copilot recursive workflows",
   "main": "setup.js",
   "bin": {

package/setup.js

@@ -110,7 +110,7 @@ function setupGitHubCopilotAgent(projectRoot) {
   
   ensureDirectoryExists(agentsDir);
   
-  const templatePath = path.join(__dirname, 'templates', 'recursive-analyst.agent.md');
+  const templatePath = path.join(__dirname, 'templates', 'recursive-agent.agent.md');
   const agentContent = fs.readFileSync(templatePath, 'utf8');
   
   if (fs.existsSync(agentPath)) {
@@ -247,11 +247,9 @@ function setup(interactive = false) {
   console.log('\n🫐 Setting up REMBR client configuration...\n');
   
   try {
-    // Set up MCP for all supported tools
-    console.log('📡 Configuring MCP servers...');
+    // Set up MCP for VS Code
+    console.log('📡 Configuring MCP servers for VS Code...');
     setupVSCodeMCP(projectRoot);
-    setupCursorMCP(projectRoot);
-    setupWindsurfMCP(projectRoot);
     setupClaudeDesktopMCP(); // Global config
     
     console.log('\n🤖 Configuring AI agents and RLM patterns...');
@@ -260,23 +258,15 @@ function setup(interactive = false) {
     setupRLMHelper(projectRoot);
     setupRLMDocumentation(projectRoot);
     
-    console.log('\n⚙️ Configuring legacy AI tools...');
-    setupCursorRules(projectRoot);
-    setupWindsurfRules(projectRoot);
-    setupAiderConfig(projectRoot);
-    
     console.log('\n✨ @rembr/vscode setup complete!\n');
     console.log('🧠 RLM Pattern System Installed:');
     console.log('  • GitHub Copilot with auto-detection (51% token reduction)');
-    console.log('  • Recursive Analyst agent for complex tasks');
+    console.log('  • Sequential sub-agent orchestration for complex tasks');
     console.log('  • Semantic memory with rembr MCP integration');
     console.log('  • Task coordination and workflow optimization');
     console.log('\n📡 MCP Configured for:');
     console.log('  • VS Code + GitHub Copilot');
-    console.log('  • Cursor');
-    console.log('  • Windsurf');
     console.log('  • Claude Desktop');
-    console.log('  • Aider');
     console.log('\n📖 Documentation Created:');
     console.log('  • docs/rlm-patterns.md - Complete usage guide');
     console.log('  • docs/rlm-benchmarks.md - Performance analysis');
@@ -287,8 +277,8 @@ function setup(interactive = false) {
     console.log('   Settings → Extensions → MCP → rembr.env.REMBR_API_KEY');
     console.log('3. Reload VS Code to activate RLM patterns');
     console.log('4. Try a complex task like "implement rate limiting with Redis and monitoring"');
-    console.log('5. Watch GitHub Copilot automatically decompose into focused subagents\n');
-    console.log('💡 Tip: Use "node rlm-helper.js <task>" to analyze decomposition patterns\n');
+    console.log('5. Watch GitHub Copilot automatically decompose into sequential subagents\n');
+    console.log('💡 For other editors: Use @rembr/cursor or @rembr/aider\n');
   } catch (error) {
     console.error('❌ Setup failed:', error.message);
     process.exit(1);

package/templates/{recursive-analyst.agent.md → recursive-agent.agent.md}

@@ -1,18 +1,8 @@
 ---
-name: Recursive Analyst
-description: Analyses and implements complex tasks using recursive decomposition with semantic memory
+name: Recursive Agent
+description: Orchestrates complex tasks using sequential decomposition with semantic memory coordination
 tools:
-  - codebase
-  - editFiles
-  - runInTerminal
-  - runTests
-  - search
-  - fetch
-  - usages
-  - problems
-  - terminalLastCommand
-  - terminalSelection
-  - rembr/*
+  ['execute/runInTerminal', 'execute/runTests', 'read/terminalSelection', 'read/terminalLastCommand', 'read/problems', 'read/readFile', 'edit/editFiles', 'search', 'web/fetch', 'runSubagent', 'rembr/*']
 infer: true
 model: Claude Sonnet 4
 handoffs:
@@ -22,13 +12,15 @@ handoffs:
     send: false
 ---
 
-# Recursive Analyst
+# Sequential Task Orchestrator
 
-You implement the Recursive Language Model (RLM) pattern. You handle arbitrarily complex tasks by:
+You implement the Recursive Language Model (RLM) pattern adapted for VS Code Copilot. You handle arbitrarily complex tasks by:
 1. Never working with more context than necessary
 2. Using rembr to retrieve only relevant prior knowledge
-3. Spawning subagents for focused sub-tasks, each receiving targeted context from rembr
-4. Coordinating subagent results through structured returns
+3. Orchestrating sequential subagents for focused sub-tasks (one level only)
+4. Coordinating subagent results through structured returns and rembr storage
+
+**Platform Limitation**: VS Code Copilot does not support nested subagents. Use sequential decomposition instead of deep recursion.
 
 ## Subagent Contract
 

package/templates/aider.conf.yml

@@ -1,52 +0,0 @@
-# Aider configuration with REMBR semantic memory
-
-# REMBR Integration
-# 
-# REMBR provides persistent semantic memory for your coding sessions.
-# While Aider doesn't natively support MCP, you can integrate REMBR via:
-#
-# 1. Manual tool calls in prompts:
-#    "First, search REMBR for authentication patterns, then implement..."
-#
-# 2. External scripts that call the REMBR API:
-#    curl -X POST https://rembr.ai/api/v1/search \
-#      -H "Authorization: Bearer $REMBR_API_KEY" \
-#      -d '{"query": "authentication patterns"}'
-#
-# 3. Pre/post hooks that store session context:
-#    - Before: Retrieve relevant context from REMBR
-#    - After: Store findings and decisions to REMBR
-
-# Model configuration
-model: claude-sonnet-4
-
-# Enable git integration
-auto-commits: true
-dirty-commits: true
-
-# Editor for commit messages
-editor: vim
-
-# Suggested workflow with REMBR:
-#
-# 1. Before starting: Query REMBR for relevant context
-#    $ rembr-query "database migration patterns"
-#
-# 2. During coding: Aider makes changes
-#
-# 3. After completing: Store findings to REMBR
-#    $ rembr-store "Migrated users table to support OAuth. Added provider column."
-#
-# You can create these wrapper scripts to integrate REMBR with Aider.
-
-# Example bash aliases for ~/.bashrc:
-#
-# alias rembr-query='curl -X POST https://rembr.ai/api/v1/search \
-#   -H "Authorization: Bearer $REMBR_API_KEY" \
-#   -H "Content-Type: application/json" \
-#   -d "{\"query\": \"$1\", \"limit\": 5}" | jq -r ".memories[].content"'
-#
-# alias rembr-store='curl -X POST https://rembr.ai/api/v1/memories \
-#   -H "Authorization: Bearer $REMBR_API_KEY" \
-#   -H "Content-Type: application/json" \
-#   -d "{\"content\": \"$1\", \"category\": \"facts\"}"'

package/templates/cursorrules

@@ -1,141 +0,0 @@
-# REMBR - Recursive Language Model with Semantic Memory
-
-You have access to REMBR, a semantic memory system via MCP tools. Use it to implement the Recursive Language Model (RLM) pattern for complex tasks.
-
-## Core Principles
-
-1. **Never work with more context than necessary** - Query REMBR for only relevant prior knowledge
-2. **Break down complex tasks** - Spawn focused subtasks with targeted context
-3. **Store findings persistently** - Save discoveries to REMBR for future sessions
-4. **Coordinate through structured returns** - Each subtask returns a standard result format
-
-## Available REMBR Tools (via MCP)
-
-### Memory Management
-- `store_memory` - Store insights, facts, preferences, project info
-- `search_memory` - Hybrid semantic + text search across memories
-- `list_memories` - Browse recent memories by category
-- `get_memory` - Retrieve specific memory by ID
-- `delete_memory` - Remove outdated memories
-
-### Context Workspaces
-- `create_context` - Create workspace for related memories
-- `add_memory_to_context` - Link memories to contexts
-- `search_context` - Scoped search within a workspace
-- `list_contexts` - View available workspaces
-
-### Snapshots (for subtask handoffs)
-- `create_snapshot` - Immutable memory bundle with TTL
-- `get_snapshot` - Retrieve snapshot by ID
-- `list_snapshots` - View available snapshots
-
-### Insights
-- `get_stats` - Usage and limits
-- `get_context_insights` - Category distribution, patterns
-- `get_memory_graph` - Memory relationships
-- `detect_contradictions` - Find conflicting information
-
-## Memory Categories
-
-Organize memories semantically:
-- **facts** - Concrete information and data
-- **preferences** - User settings and choices
-- **conversations** - Conversation context
-- **projects** - Project-specific information
-- **learning** - Knowledge and insights
-- **goals** - Objectives and targets
-- **context** - Situational context
-- **reminders** - Future actions
-
-## RLM Pattern: Parent-Subtask Protocol
-
-### Before Decomposing
-
-1. Generate unique `taskId` (e.g., `implement-auth-20240106`)
-2. Query REMBR for relevant prior context:
-   ```
-   search_memory({ query: "authentication patterns OAuth JWT", limit: 10 })
-   ```
-3. Identify subtasks and what context each needs
-
-### When Spawning Subtasks
-
-Provide each subtask with:
-```
-## Subtask
-[Specific focused objective]
-
-## Context from REMBR
-[Relevant memories retrieved for this subtask]
-
-## Storage Instructions
-Store findings with:
-- Category: "facts"
-- Metadata: { "taskId": "implement-auth-20240106", "area": "oauth-flow" }
-
-## Return Format
-- Summary: [What you found/did]
-- Findings stored: [Search query to retrieve details]
-- Key points: [Most important items]
-- Status: [complete/partial/blocked]
-```
-
-### After Subtasks Complete
-
-1. Read each subtask's summary and key points
-2. If full details needed, query REMBR:
-   ```
-   search_memory({ query: "implement-auth-20240106 oauth-flow", category: "facts" })
-   ```
-3. Synthesize findings and store to REMBR for future sessions
-
-## Example Usage
-
-### Storing a Discovery
-```
-store_memory({
-  category: "facts",
-  content: "API uses rate limiting: 100 req/min per user via express-rate-limit + Redis",
-  metadata: {
-    taskId: "rate-limit-analysis",
-    area: "api-middleware",
-    file: "src/middleware/rateLimit.ts"
-  }
-})
-```
-
-### Retrieving Context
-```
-search_memory({
-  query: "rate limiting middleware patterns",
-  category: "facts",
-  limit: 5
-})
-```
-
-### Creating a Workspace
-```
-create_context({
-  name: "payment-service-refactor",
-  description: "Refactoring payment service to microservices",
-  category: "projects"
-})
-```
-
-## When to Use REMBR
-
-✅ **Do use** for:
-- Storing architectural decisions
-- Remembering project patterns and conventions
-- Building knowledge across sessions
-- Coordinating complex multi-step tasks
-- Sharing context between subtasks
-
-❌ **Don't use** for:
-- Temporary variables or transient data
-- Information already in the codebase
-- Simple single-step tasks
-
-## API Key Setup
-
-Ensure `REMBR_API_KEY` is set in your Cursor environment settings.

package/templates/windsurfrules

@@ -1,141 +0,0 @@
-# REMBR - Recursive Language Model with Semantic Memory
-
-You have access to REMBR, a semantic memory system via MCP tools. Use it to implement the Recursive Language Model (RLM) pattern for complex tasks.
-
-## Core Principles
-
-1. **Never work with more context than necessary** - Query REMBR for only relevant prior knowledge
-2. **Break down complex tasks** - Spawn focused subtasks with targeted context
-3. **Store findings persistently** - Save discoveries to REMBR for future sessions
-4. **Coordinate through structured returns** - Each subtask returns a standard result format
-
-## Available REMBR Tools (via MCP)
-
-### Memory Management
-- `store_memory` - Store insights, facts, preferences, project info
-- `search_memory` - Hybrid semantic + text search across memories
-- `list_memories` - Browse recent memories by category
-- `get_memory` - Retrieve specific memory by ID
-- `delete_memory` - Remove outdated memories
-
-### Context Workspaces
-- `create_context` - Create workspace for related memories
-- `add_memory_to_context` - Link memories to contexts
-- `search_context` - Scoped search within a workspace
-- `list_contexts` - View available workspaces
-
-### Snapshots (for subtask handoffs)
-- `create_snapshot` - Immutable memory bundle with TTL
-- `get_snapshot` - Retrieve snapshot by ID
-- `list_snapshots` - View available snapshots
-
-### Insights
-- `get_stats` - Usage and limits
-- `get_context_insights` - Category distribution, patterns
-- `get_memory_graph` - Memory relationships
-- `detect_contradictions` - Find conflicting information
-
-## Memory Categories
-
-Organize memories semantically:
-- **facts** - Concrete information and data
-- **preferences** - User settings and choices
-- **conversations** - Conversation context
-- **projects** - Project-specific information
-- **learning** - Knowledge and insights
-- **goals** - Objectives and targets
-- **context** - Situational context
-- **reminders** - Future actions
-
-## RLM Pattern: Parent-Subtask Protocol
-
-### Before Decomposing
-
-1. Generate unique `taskId` (e.g., `implement-auth-20240106`)
-2. Query REMBR for relevant prior context:
-   ```
-   search_memory({ query: "authentication patterns OAuth JWT", limit: 10 })
-   ```
-3. Identify subtasks and what context each needs
-
-### When Creating Flows/Cascades
-
-Provide each flow with:
-```
-## Objective
-[Specific focused objective]
-
-## Context from REMBR
-[Relevant memories retrieved for this flow]
-
-## Storage Instructions
-Store findings with:
-- Category: "facts"
-- Metadata: { "taskId": "implement-auth-20240106", "area": "oauth-flow" }
-
-## Return Format
-- Summary: [What you found/did]
-- Findings stored: [Search query to retrieve details]
-- Key points: [Most important items]
-- Status: [complete/partial/blocked]
-```
-
-### After Flows Complete
-
-1. Read each flow's summary and key points
-2. If full details needed, query REMBR:
-   ```
-   search_memory({ query: "implement-auth-20240106 oauth-flow", category: "facts" })
-   ```
-3. Synthesize findings and store to REMBR for future sessions
-
-## Example Usage
-
-### Storing a Discovery
-```
-store_memory({
-  category: "facts",
-  content: "API uses rate limiting: 100 req/min per user via express-rate-limit + Redis",
-  metadata: {
-    taskId: "rate-limit-analysis",
-    area: "api-middleware",
-    file: "src/middleware/rateLimit.ts"
-  }
-})
-```
-
-### Retrieving Context
-```
-search_memory({
-  query: "rate limiting middleware patterns",
-  category: "facts",
-  limit: 5
-})
-```
-
-### Creating a Workspace
-```
-create_context({
-  name: "payment-service-refactor",
-  description: "Refactoring payment service to microservices",
-  category: "projects"
-})
-```
-
-## When to Use REMBR
-
-✅ **Do use** for:
-- Storing architectural decisions
-- Remembering project patterns and conventions
-- Building knowledge across sessions
-- Coordinating complex multi-step tasks (Cascade flows)
-- Sharing context between flows
-
-❌ **Don't use** for:
-- Temporary variables or transient data
-- Information already in the codebase
-- Simple single-step tasks
-
-## API Key Setup
-
-Ensure `REMBR_API_KEY` is set in your Windsurf environment settings.