MicroPython Studio — Live MicroPython Debugger for VS Code

Set breakpoints on a real Raspberry Pi Pico 2 W, step through MicroPython code, inspect locals and call stacks, and capture live runtime traces. MicroPython Studio also provides a REPL, device file manager, firmware tools, CircuitPython support and an optional local AI assistant.

Install from VS Code Marketplace · Watch the real-device debugger demo · Read the debugger guide

See what makes the debugger different

On compatible debugger-enabled firmware, MicroPython Studio provides source breakpoints, step/continue controls, local/global variable inspection, call stacks and live RTA function tracing, without requiring a separate JTAG probe for those software-debugging features. The demo shows the debugger operating on a real Pico 2 W.

Hardware-support status matters. The existing Pico 2 W debugger workflow has been exercised on real hardware. The new Pico-family frozen-firmware builds and ESP32-S3 debugger improvements are under separate hardware qualification; an ESP32-C3 debugger has not been released. Do not interpret a successful CI build as evidence that your board is supported. Read the board-specific firmware and test status before flashing anything.

Experimental debugger firmware — for debugging and testing your own code ONLY. NOT FOR PRODUCTION USE. This warning applies to unvalidated firmware in the TestBuilds download directory, not to an approved, board-specific stable release. A successful CI build does not mean the image is hardware-approved. Verify the exact board model, back up your files and follow the matching firmware instructions before flashing. Download Debug Firmware opens the file or download page; Studio does not automatically flash the board or overwrite boot.py.

Why Use It?

Main Features

• Device File Explorer Browse, upload, download, rename, delete, and create files on your board.

• One-Click Run and Shell Run the active Python file or open an interactive REPL from VS Code.

• Live Debugger Set breakpoints, step through code, inspect locals, and view call stack data.

• CircuitPython Support Detect CIRCUITPY drives, install libraries, sync files, and use Web Workflow.

• MicroPython WebREPL Configure Wi-Fi access and connect to supported boards over the network.

• Firmware Tools Download and flash firmware for supported targets, including debug firmware.

• QEMU Simulator Run code against an emulated MicroPython target when hardware is not nearby.

• Private AI Assistant Use local Ollama models for code help and device-error investigation.

Quick Start

1. Install the extension in VS Code.
2. Run MicroPython: Setup Development Environment.
3. Connect your board by USB.
4. Run MicroPython: Refresh Device Files.
5. Create or open a project.
6. Press Run to execute your active Python file.

That is the normal daily loop: connect, edit, run, inspect files, repeat.

Common Commands

Debugging

The debugger is designed for embedded Python workflows where JTAG is not always practical.

It supports:

• breakpoints

• stepping

• locals inspection

• call stack view

• runtime trace events

• live function/runtime tracing (observed elapsed-time share, not CPU utilisation)

• debugger-enabled firmware for supported board-specific configurations; existing published Pico firmware may need the legacy setup steps

• test-only frozen debugger images are not published as stable releases until hardware validation

For best results, start with a simple script first, confirm upload/run works, then enable the debugger.

Debugger USB connections

The debugger uses a separate connection from the REPL. For compatible debugger-enabled test firmware, the connection layout is:

Firmware must match the exact board. See board support and firmware status for stable versus experimental builds and connection guidance.

Simulator

The built-in simulator is useful when you want to test application logic before connecting a board.

• Start or stop it from the status bar.
• Run code through the same VS Code workflow.
• Use local lib/ folders for dependencies.
• The simulated filesystem is read-only, so direct uploads are blocked with a clear warning.

Local AI Assistant

MicroPython Studio can use Ollama for private local AI help.

1. Install Ollama.
2. Open the MicroPython Studio AI view.
3. Let the extension prepare the local model.
4. Ask questions about your active file, device errors, or MicroPython APIs.

Your source code stays on your machine.

Supported Workflows

Project Status

MicroPython Studio is actively developed and already used by many embedded Python developers. The current focus is reliability: port locking, debugger setup, ESP32-S3 workflows, automated CI checks, and better regression testing.

If something breaks, please open an issue with:

• board name
• firmware type and version
• operating system
• selected port
• output from the MicroPython IDE or MPy Debugger Setup panel

Useful Links

• Project Website
• MicroPython Documentation
• CircuitPython Documentation
• Project Repository
• Issue Tracker
• Contributing Guide
• Code of Conduct
• YouTube Channel

Acknowledgements

MicroPython Studio builds on excellent open source projects:

All bundled third-party files retain their original license headers.

Support

Questions, bugs, and ideas are welcome.

• Email: niwantha33@gmail.com
• Issues: github.com/niwantha33/micropython-studio/issues
• YouTube: youtube.com/@NiwanthaDev

License

MicroPython Studio is licensed under the MIT License.

XBee MicroPython type hints and libraries are sourced from Digi International's xbee-micropython, also under the MIT License.