Clarity for AI buildersSponsored by AI Routing
adoption

Why AI agents could favor devices with replaceable firmware

Why AI agents could favor devices with replaceable firmware

M-Vave opened its FM-1 firmware after owners built alternatives. Geoff Stearns argues AI agents could reward that openness.

In an essay on how AI could change hardware buying, Stearns points to the roughly $70 M-VAVE FM-1 pocket synthesizer. Owners began writing replacement firmware in September, and by October their projects included a virtual analog synth, a multitrack groovebox, a dark ambient sampler and a port of Doom. Judging by developers’ forum posts, Stearns says nearly all of the projects used AI coding tools.

In October, M-Vave published its firmware under GPLv3 and provided a development kit and a browser emulator for testing builds before installing them.

The essay separates two changes: AI can lower the cost of writing firmware, but the hardware maker still determines whether replacing it is practical. An agent asked to fix a device could try its existing settings before looking for replacement software. If a replacement is warranted, the device still needs a supported way to install it and a way to recover if it fails.

Stearns says M-Vave’s recovery tool restores the stock firmware in about ten seconds. Testing and recovery solve different problems: the emulator lets developers try a build before flashing it, while the recovery tool gives owners a way back afterward.

Stearns argues that this difference could show up in purchase recommendations. An agent working for the buyer might prefer a synth, printer, TV or router it can adapt later, even if the buyer never intends to install custom firmware. But compatibility with accounts, apps and cloud services can matter as much as access to the device itself. Stearns cites Chamberlain’s 2023 cutoff of Home Assistant access to MyQ garage door openers as an example of how a vendor can limit an integration without changing what owners can install on a device.

The essay also distinguishes firmware signing from a vendor-only lock. A device can reject unsigned code while letting its owner add a trusted signing key, an option Stearns says Pixel phones already offer. That gives owners a choice about whose code to trust; it does not establish that a signed build is safe. Stearns points to verified installers, firmware checks and recovery tools as additional safeguards against malicious software presented as a useful upgrade.

The FM-1 shows that a manufacturer can support owner-built firmware with tools for testing and recovery. It does not show that agents are already steering hardware sales. Stearns’s forecast depends on buyers delegating those choices and on agents recommending devices in the buyer’s interest rather than favoring products sold by their own providers.