-
Notifications
You must be signed in to change notification settings - Fork 2
Home
Welcome to the comprehensive technical documentation for the Remember MCP VS Code Extension! This wiki contains in-depth guides, discoveries, and implementation details that we've uncovered while building an extension that provides analytics and insights for GitHub Copilot usage.
This wiki serves as our living knowledge base where we document:
- Reverse Engineering Discoveries: Deep dives into how VS Code and Copilot work internally
- Implementation Guides: Complete technical documentation for extension developers
- Empirical Analysis: Evidence-based findings from testing and experimentation
- Best Practices: Patterns and approaches that work reliably across VS Code versions
- Troubleshooting: Common issues and debugging techniques
VS Code Session and Window Architecture Deep Dive
- Understanding VS Code's session and window management
- Extension context and log file navigation
- Real-time vs historical monitoring strategies
- Implementation patterns for window-aware extensions
VS Code Copilot Chat Session Files Technical Guide
- Complete documentation for Copilot chat session files
- File discovery, structure, and parsing techniques
- Cross-platform implementation examples
- Performance considerations for large datasets
- Concise canonical schema for
chatSessions/<id>.json - Turn structure, analytics mapping, and pitfalls
- Separation from editing state & enrichment boundaries
- Fine-grained editing timeline (
linearHistory/stops/entries) - Telemetry correlation (
telemetryInfo.requestId) and change detection heuristics - Enrichment strategy for model request attribution
More guides will be added as we discover new aspects of Copilot integration and VS Code extension development.
The Remember MCP VS Code Extension provides:
- Usage Analytics: Track your Copilot conversations and tool usage
- Session Insights: Analyze chat patterns and model interactions
- Real-time Monitoring: Live updates from your current VS Code window
- Historical Analysis: Comprehensive reports across all your VS Code sessions
- Visual Interface: Clean, intuitive panel for exploring your data
Our development approach emphasizes:
- Evidence-Based Analysis: We don't guess - we test, measure, and document
- Empirical Testing: Real-world experiments to understand VS Code behavior
- Cross-Platform Validation: Ensuring compatibility across Windows, macOS, and Linux
- Version Compatibility: Supporting both VS Code Stable and Insiders editions
| Topic | Description | Status |
|---|---|---|
| VS Code Session and Window Architecture Deep Dive | Understanding VS Code's internal architecture | Complete |
| VS Code Copilot Chat Session Files Technical Guide | Working with Copilot session data | Complete |
| Chat Session File Format | Canonical per-turn chat session schema | Complete |
| Editing State File Format | Editing timeline & telemetry correlation | Complete |
| Extension Development Patterns | VS Code extension best practices | Planned |
| Copilot Analytics Engine | Building usage analytics systems | Planned |
| Cross-Platform File Monitoring | File watching across operating systems | Planned |
This wiki grows with our discoveries! As we implement new features and uncover more about VS Code and Copilot internals, we document our findings here for the benefit of the extension development community.
This wiki is maintained as part of the Remember MCP VS Code Extension project.
Repository: NiclasOlofsson/remember-mcp-vscode