Toit's contributors released version 2.0.0 on October 31, 2026, ending more than four years of alpha development. For existing users, the upgrade warrants a check of peripheral code: the release announcement identifies accepting pin numbers directly, instead of requiring gpio.Pin objects, as the final major breaking change planned for this version.
Toit is a programming language for embedded devices. Its repository contains the compiler, virtual machine and standard libraries used to run programs on ESP32 microcontrollers. This article examines the release documentation; we haven't flashed a board or tested application compatibility.
What changed, and what accumulated
The version-matched release notes list bug fixes, Unix domain socket support intended to be accessed through the host package, and the ability to set a hostname through firmware configuration. They also link a comparison against alpha.199, giving developers a concrete starting point for inspecting the final release changes.
The announcement's longer feature list covers development since Toit became open source. Hardware expansion and a rewritten package manager belong to that accumulated work; the post doesn't establish that they first arrived in 2.0.0. That distinction matters if you're deciding whether an older alpha already does what your application needs.
Check the path your application uses
For ESP32 development, the project README recommends Jaguar, which downloads the Toit SDK automatically. For desktop development, it points readers to separate host instructions. An upgrade check should therefore record which SDK your workflow actually uses before you compare behaviour across versions.
Existing peripheral integrations deserve particular attention because of the pin API change. A version number alone can't establish whether your drivers work unchanged, and we haven't measured that here.
The contributors' announcement leaves a formatter and support for more architectures among work still to come. Watch the corresponding merged changes and release notes before treating either as a shipped capability. For an application moving off an alpha today, the immediate evidence to gather is narrower: whether its peripheral calls and driver dependencies work with the selected SDK.