Repository navigation
v0.3.1
Everything since v0.2.1, the last version anyone received.
0.3.0 was written up as a release and never published, so its cellular work reaches you here for the first time. Both entries are included below rather than only the newest, because both are new to you.
[0.3.1] - 2026-08-26
Added
- Every device tool is a Tool bit: versioned, credited, and hash-verified before it runs.
- CRA advisory hints and package mappings update from the registry instead of a release.
- Crash-address decoder that picks
addr2lineby chip architecture and reports where it looked. - Board and chip names come from knowledge, including a catalogue of ten shipping ESP32 targets.
- Fanstel LEW840X boards route to their own product knowledge.
Changed
- A newer registry copy of a bit or tool wins over the bundled one; bundled remains the fallback.
- An update cannot widen what a tool may do on its own; the stricter rule stands.
- Credit reports the copy that actually served, not always the bundled one.
- About names both platforms and the CRA check, and links the docs rather than a chip vendor.
- Building the extension no longer depends on the build machine's Node version.
Fixed
- A CVE scan that could not run no longer reads as a clean one.
- Large captures no longer return truncated with a success status.
- A tool improved in the registry could still be read back from an older copy on disk.
- Third-party code bundled into a tool is now named in its notice file.
- Two links pointed at a repository that had been renamed.
- Setting
ADSUM_AUTHOR_TOKENempty now means "published only", so drafts can be compared against it. - A multi-chip product had nowhere to keep its project memory.
- The ESP monitor put the chip into the bootloader when opening the port.
- A silent ESP capture now retries the reset once, and a retry never leaves less evidence than the first attempt.
- ESP commands source the toolchain environment in the terminal that actually runs them.
idf.py is not recognizedis reported as a broken virtual environment, not a missing source step.- The native-module allow-list never matched on Windows.
Known issues
- Modem trace needs firmware built with tracing enabled, and a SIM, or the capture is empty.
[0.3.0] - 2026-08-22
0.2.2 was never released; its work ships here.
Added
- nRF91 cellular: NB-IoT, LTE-M, NTN and DECT NR+, each loaded only for the project that needs it.
- GNSS positioning knowledge for nRF91.
- Board knowledge for the nRF9161 DK, nRF9151 DK and nRF9160 DK.
- Device tools are Tool bits, each with its own descriptor and author credit.
- Tool bits can arrive from the registry, verified against a published hash before running.
- Board shell: send AT and Zephyr shell commands and read until the board finishes, on all platforms.
- Modem trace: capture, decode and explain registration state, refusal reason, radio mode and search events.
log-shape: describe a log's structure in one call, then read any message kind in context.- Knowledge is named when it loads, not only when the agent reads a file.
Fixed
- A tool that could not run no longer reports as though it had.
- Device tools no longer try to install Python packages; the wrappers no longer hide the install location.
- An empty answer from a device is no longer reported as a finding.
- The "Open project folder" button did nothing, could point at the wrong project, and never appeared for copied samples.
- A scaffolded project you never opened stopped following you into unrelated tasks.
- Refusing to write project memory now says plainly that it is a blocker.
- Log and code search: the search program was not found, so nearly every search returned no results.
- Mermaid diagrams render more reliably.
Known issues
- NTN needs an nRF9151 with the LACA A1A variant and its own modem firmware.
- DECT NR+ needs a separate modem firmware image, available from Nordic sales rather than as a download.
- Two sessions using one development kit at the same time can interfere with each other.