Simplicity AI SDK Beta1 (Sept 2026) Release Notes#

Welcome to the first public Beta release of the Simplicity AI SDK, which provides AI-assisted access to supported Silicon Labs development workflows.

Release Summary#

Enables natural-language Bluetooth LE application development, including application creation and configuration, code generation, project builds, firmware flashing on supported hardware, and iterative development.
Provides Simplicity SDK-grounded guidance using Silicon Labs documentation, APIs, examples, and project metadata to deliver contextual, version-specific responses.
Enables AI assistants to use Silicon Labs configuration and hardware tools for project configuration, GATT profile creation and validation, board discovery, device programming, and firmware flashing.
Introduces AI-guided debugging workflows for investigating build failures and device behavior, including log interpretation, GDB-based inspection, fault analysis, and suggested corrective actions.
Enables AI assistants to work with Silicon Labs analysis tools, including Advanced Energy Monitoring (AEM), Network Intelligence, and Channel Sounding Analyzer.
Provides initial support for GitHub Copilot and Codex IDE agents through Visual Studio Code.

All bug fixes are listed in the table below.


UID	Issue	Workaround
None	Wireless Protocol Support: This release supports Bluetooth LE development workflows only. Other wireless protocols and their associated SDK and tools are not fully supported.	-
None	Network Intelligence Support: On Windows OS, the Network Intelligence workflow does not install Wireshark automatically.	Manually install Wireshark before using the Network Intelligence workflow on Windows.
None	Codex Authentication with mcp.silabs.com: Codex refreshes MCP credentials while the refresh token is valid. After the refresh token expires and the server returns a standard `400 invalid_grant` response, Codex logs that reauthorization is required. However, Codex does not clear the rejected credentials or display the Authenticate button. Instead, it continues retrying the expired refresh token.	Log out and sign in again. Alternatively, run: `codex mcp logout <server>`. Then reload Codex and authenticate again. This issue is caused by Codex client UI state management and is not a server-side OAuth failure.


UID	Description
-	None