-
Notifications
You must be signed in to change notification settings - Fork 335
VSCode ESP‐IDF Extension Roadmap 2026
Kondal Kolipaka edited this page Jan 14, 2026
·
7 revisions
This roadmap outlines the strategic direction, guiding principles, and planned development focus for the ESP-IDF VS Code extension in 2026. It positions VS Code as the primary IDE for ESP-IDF development, with strong emphasis on scalability, stability, and AI-assisted workflows.
⚠️ This roadmap reflects current priorities and may evolve based on community feedback, ecosystem changes, and Espressif product direction.
- Position VS Code as the go-to IDE for ESP-IDF development.
- Leverage AI integration to improve developer productivity, debugging efficiency, and onboarding.
- Stability & Maintainability first – reduce friction in common setup and “get started” workflows.
- Better integration with EIM – seamless ESP-IDF installation, updates, and recovery.
- Scalability for new Espressif targets – smooth support for new chips.
- Clear diagnostics – unified, actionable diagnostic logs.
- AI-first IDE – design workflows assuming AI-assisted development as a core capability.
- Ensure build, flash, monitor, and debug workflows work reliably for new ESP targets.
- Add or extend target-specific configurations where required.
- Fix high-priority EIM ↔ VS Code integration issues.
- Improve setup, update, and recovery workflows.
- Ensure clear diagnostics when EIM-related failures occur.
- Improve OpenOCD detection scripts and capability handling.
- Address unstable debugging issues across platforms.
- Dynmaic hardware watchpoints limit - instead of hard coding in the IDE's, we can get it from the tools/openocd.
- Improve board identification when multiple identical targets are connected (e.g. 2× ESP32-C5).
- Prevent incorrect JTAG flashing or debugging caused by stale adapter paths.
- Ensure at least one quarterly release with documented improvements and fixes.
- Developing a separate extension dedicated to ESP-IDF developers would help them use it alongside the existing ESP-IDF VS Code functionality. During ESP-IDF development, developers may create multiple development profiles, frequently switch between different projects, switch between different IDF versions, and work on specific Git commits. We need to think about how to address these use cases effectively.
- Webview for editing multiple project configurations.
- Enable Hints Viewer support for monitor output.
- Power Optimization Viewer
- SBOM integration for ESP-IDF
-
idf.pyMCP integration. - Component Registry MCP integration.
- Documentation MCP integration.
- GPIO Checker.
- AI-powered code generation.
- Hints Viewer integration with AI explanations.
- Pre-built prompts for common ESP-IDF workflows - Check Agent Skills
- Given a build error, stack trace, or crash log, AI suggests likely causes and solutions.
- Use data from:
- IDF Hints Viewer
- OpenOCD Hints Viewer
- ESP-IDF documentation via AI agents
- Track AI-native IDEs such as Cursor.
- Test and ensure compatibility with ESP-IDF VS Code workflows.
- Keep documentation up to date, especially for EIM integration.
- Maintain Chinese translations.
- Create tutorials for each major VS Code extension functionality.
- Document about availablity of espressif MCP servers https://mcp.espressif.com/