ToolBB-0121

Silico: a framework for agents to build and maintain firmware for a real device

In Silico, coding agents write and maintain a device's firmware from a spec kept in a GitHub repo. The agent scaffolds firmware, a simulator with its own HAL, an install tool and CI that runs on the simulator and on hardware. MicroPython is the default, with C on ESP-IDF as an option. Three demo specs target an M5Stack M5GO kit.

Open original source github.com · Charlie Kindel

Claimed
Why this evidence label?

The author describes it but shows no evidence we could check yet.

How we check entries
Preview image for Silico: a framework for agents to build and maintain firmware for a real device
The source's own preview image, from github.com.

Briefing

The agent starts from one prompt that points it at Silico's AGENTS.md and works inside the product's own repo. Silico calls each device a GCU, a shippable edge product, and the shared host tooling a spine. MicroPython boards get their first flash by UF2 or esptool and later updates by mpremote file copy. The Xuss-Lame demo spec is deliberately thin. The agent has to interview the person to fill it in.

Silico covers firmware and the host path, not PCB design. Arduino, PlatformIO and the Pico C SDK are not supported deploy paths yet. The README lists three products built with it, including Zakalwe, an RP2040 MicroPython module for 1980s BMW, Volvo and Mercedes cars by Holy Grail Labs.

From the GitHub API

Repository facts

Repository facts for tig/silico, from the GitHub API
Repositorytig/silico
Stars13
LicenseApache-2.0 Permissive
LanguagePython
Last push31 Jul 2026 2 mo ago

Tags

Interface

Report a problem with this entry