Frequently Asked Questions

Everything you need to know about ProbeCodex, the AI-powered embedded debugger for ARM Cortex-M development.

Ready to try ProbeCodex?

Free beta access available now - no credit card required.

Download Free Beta

Yes, during the public beta! You can test all tiers (Basic, Pro, Team, Enterprise) completely free. Your beta license refreshes every 7 days, so you can explore different feature sets. After beta ends, we'll introduce tiered pricing. ProbeCodex is an MCP server - you'll need your own AI tool subscription (Claude Code, Cursor, Windsurf, etc.) to use it.

During the beta, you can test ALL tiers completely free: Basic, Pro, Team, and Enterprise. Your beta license refreshes every 7 days, giving you the perfect opportunity to explore different tiers and features. This includes OpenOCD and J-Link integration, FreeRTOS task introspection, memory and register inspection, ITM/SWO trace capture, SVD peripheral register access, remote hardware sharing, and team collaboration features. Note: You'll need your own AI tool subscription (Claude Code, Cursor, etc.) to use ProbeCodex.

The public beta started January 15, 2026. During beta, all users get free access to ALL tiers - Basic, Pro, Team, and Enterprise. Beta licenses refresh every 7 days. After beta ends, we'll introduce tiered pricing, but early beta users will receive special loyalty discounts. Sign up now to lock in beta benefits.

The ProbeCodex MCP server is not currently open source, but we're evaluating open-sourcing parts of it in the future. We use and contribute to many open source tools including OpenOCD, GDB, and FreeRTOS. Our goal is to balance openness with sustainable business development.

We offer a 14-day money-back guarantee on all paid subscriptions. If you're not satisfied with ProbeCodex for any reason, contact support@probecodex.com within 14 days of purchase for a full refund. No questions asked.

Absolutely. You can cancel your subscription at any time from your account settings. You'll retain access to paid features until the end of your current billing period. After cancellation, your account will revert to the free tier with all your projects and settings preserved.

ProbeCodex is an MCP (Model Context Protocol) server that extends any compatible AI agent's capabilities for embedded debugging. It works with Claude Code, Cursor, Windsurf, and other AI tools that support the MCP standard. ProbeCodex runs locally and provides your AI agent with tools to interact with debug probes, read memory, inspect RTOS tasks, and more.

ProbeCodex works with any AI agent that supports the MCP (Model Context Protocol) standard. This includes Claude Code, Cursor, Windsurf, and other MCP-compatible tools. You'll need an active subscription to your preferred AI tool. ProbeCodex adds embedded debugging capabilities through MCP, allowing you to debug ARM microcontrollers using natural language commands.

ProbeCodex supports all ARM Cortex-M microcontrollers (M0, M0+, M3, M4, M7, M23, M33, M55) through OpenOCD, J-Link, and ST-Link debug probes. This includes popular chips from STMicroelectronics (STM32), Nordic Semiconductor (nRF52/53), NXP (LPC, Kinetis), Microchip (SAM), and many more.

Yes! ProbeCodex has deep RTOS integration, including FreeRTOS. You can list tasks, view task states and priorities, inspect stack usage, monitor queues and semaphores, and get heap statistics - all through natural language commands to your AI tool.

Yes! If your firmware includes SEGGER RTT, ProbeCodex can read RTT output via OpenOCD's RTT support. This enables high-speed, low-overhead debug logging without needing a dedicated UART - perfect for real-time debugging where printf over serial would be too slow.

Yes! Using the RTT feature, ProbeCodex can read your device's screen buffer memory directly through the debug probe. This allows your AI tool to 'see' what's displayed on an LCD, e-paper, or other display - perfect for debugging UI issues, verifying graphics rendering, or testing display drivers without needing a camera pointed at your device.

Yes! All tiers include some remote debugging capability. Pro, Team, and Enterprise tiers offer enhanced remote features plus portal support for sharing devices with your team. A developer in one location can debug a device connected to another team member's computer using our secure WireGuard VPN. The ProbeCodex Agent handles VPN setup automatically — it downloads your config, connects to the VPN, and even detects if your network blocks UDP and switches to a WebSocket tunnel (wstunnel) automatically. Peer-to-peer access is enforced per booking session, so only you and the hardware owner can communicate during approved time slots. See our Hardware Sharing Guide (/docs/hardware-sharing) for full details.

Many mobile carriers block the UDP port that WireGuard VPN uses (port 51820). This is a known limitation of mobile hotspot tethering. The solution is wstunnel — a tool that wraps WireGuard's UDP traffic inside a standard HTTPS connection (TCP port 443), which passes through any network. Install wstunnel (brew install wstunnel on macOS, or download from github.com/erebe/wstunnel/releases) and the ProbeCodex Agent will automatically detect the UDP block and switch to wstunnel mode. No manual configuration needed. See the Restrictive Networks section in our Hardware Sharing docs for manual setup instructions if you're not using the agent.

Very secure. ProbeCodex uses WireGuard, a modern VPN protocol with state-of-the-art cryptography (ChaCha20, Poly1305, Curve25519). Each team member gets a unique cryptographic key pair, and all traffic is encrypted end-to-end. Organizations are isolated into separate VPN subnets. Most importantly, peer-to-peer access is enforced per session — team members can only reach each other during active, approved hardware bookings. Outside booking windows, all peer traffic is blocked at the server level. Your private key never leaves your machine after the initial download. For more details, ask the AI Support Chat in the portal.

Installation is simple: 1) Download ProbeCodex for your platform (macOS, Linux, or Windows), 2) Run the ProbeCodex Agent with the --install flag to set up the MCP server and configure your AI tools automatically, 3) Connect your debug probe and start debugging! ProbeCodex works with Claude Code, Cursor, Windsurf, and other MCP-compatible AI tools.

Absolutely. ProbeCodex runs locally on your machine - your source code and debug data never leave your computer. The only data transmitted is anonymized telemetry (which you can disable) and license validation. We're GDPR compliant and take security seriously.

Still have questions?

Can't find what you're looking for? Our support team is here to help.