✅ Project compiled successfully
✅ All dependencies installed
In VS Code:
- Open the
agentMemoryproject folder - Press F5 (or Run → Start Debugging)
- A new VS Code window will open labeled [Extension Development Host]
Check Status Bar:
- Look for
🧠 Memory: Initializing...in the bottom-right status bar - After a few seconds, it should change to
🧠 Memory: Active
Check Output:
- Open Output panel (View → Output)
- Select "agentMemory" from the dropdown
- Verify you see activation logs
Open Dashboard:
- Press
Cmd/Ctrl+Shift+Pto open Command Palette - Type "agentMemory: Open Memory Dashboard"
- Press Enter
Expected Result:
- Webview panel opens with dashboard
- Shows overview cards (all zeros initially)
- Charts render correctly (Agent Activity, Memory Types, Token Metrics)
- No console errors
Test Refresh:
- Click the "🔄 Refresh" button
- Dashboard should update without errors
Check Settings File:
- In Extension Development Host, check if
.vscode/settings.jsonwas created - Should contain MCP server configuration for detected agents
Check Rule Files:
.clinerules(if Cline is installed).roomodes(if RooCode is installed).kilocode/config.yaml(if KiloCode is installed)
Create a test file test-api.js:
const vscode = require('vscode');
async function testAPI() {
const agentMemory = vscode.extensions.getExtension('webzler.agentmemory');
if (!agentMemory) {
console.error('Extension not found');
return;
}
const api = await agentMemory.activate();
console.log('API activated:', api);
// Try to write a test memory
try {
await api.write('test-key', 'Test content', {
type: 'feature',
tags: ['test']
});
console.log('✅ Write successful');
} catch (error) {
console.error('❌ Write failed:', error.message);
}
}
testAPI();Check MCP Server Process:
- Open Task Manager/Activity Monitor
- Look for a
nodeprocess running the MCP server - Should be running with the project ID as an argument
Check MCP Data Directory:
- Navigate to
./mcp-data/in your workspace - Should see a folder named after your project
- Contains memory data files
Permission Prompts:
- The permission system won't trigger unless another extension tries to access memory
- For manual testing, you can check the SecurityManager is initialized
Check Audit Logs (Developer Console):
- Open Developer Tools in Extension Development Host
- Help → Toggle Developer Tools
- Check Console for security-related logs
Solution:
- Check Terminal for compilation errors
- Run
npm run compileagain - Check for missing dependencies:
npm install
Solution:
- Check if
out/mcp-server/server.jsexists - Verify Node.js is in PATH
- Check Extension Host output for error messages
Solution:
- Check browser console for JavaScript errors
- Verify Chart.js CDN is accessible
- Check webview content security policy
Solution:
- Check if workspace folder is open
- Verify file system permissions
- Check Extension Host output for errors
- Extension activates without errors
- Status bar shows "Memory: Active"
- Dashboard opens and displays correctly
- Dashboard charts render (even with zero data)
- Refresh button works
-
.vscode/settings.jsonis created - Rule files are created (if agents detected)
- MCP server process starts
-
./mcp-data/directory is created - No console errors in Developer Tools
-
If everything works:
- Initialize git:
git init - Create
.gitignore(already exists) - Commit:
git add . && git commit -m "Initial commit" - Add remote:
git remote add origin https://github.com/webzler/agentMemory.git - Push:
git push -u origin main
- Initialize git:
-
If issues found:
- Note the error messages
- Check the specific component that failed
- Debug and fix before publishing
-
Package extension:
- Run:
npm run package - Creates
agentmemory-0.1.0.vsix - Test install:
code --install-extension agentmemory-0.1.0.vsix
- Run:
# From the agentMemory directory
code .
# Then press F5 in VS CodeGood luck with testing! 🚀