Nerves sets an AI policy
August 20, 2026 • Issue 114
maintaining a trustworthy fundament No images? Click here Nerves has an AI policy nowThis was established through discussion in the core team around many, many .. many instances of our use of LLMs, drive-by contributions via LLMs, thoughtful contributions via LLMs and everything we know so far. This is the new policy . There is a copy in every official nerves repo to hopefully encourage agents to surface this as well as help people find it. "Contributions are made by people, not tools." The core team have all tried LLMs to various extents and dialed up and dialed back their usage as we've seen where it works and what it does for us. The reason we land on having a person do all the textual communication around a contribution is multifaceted. Primarily it is about building trust with contributors and hopefully having a long-term exchange. "Pull request titles, descriptions, issue reports, commit messages, and review discussions should be written by the contributor. Using AI to translate or tighten your own writing is fine. Using it to write in your place is not." Friction is kind of the point. Unfortunately it is completely possible for one enthusiastic well-meaning individual (such as myself), with the help of some agents, to completely saturate the bandwidth of the Nerves core team in terms of review and feedback. And the review, the feedback and the consideration are all very important in keeping Nerves a solid foundation to build on top of. The more relied upon a piece of Nerves is the more seriously it is taken. If you feel like this might be in response to something you specifically did. No. You are not in trouble. This is a very broad thing and we needed to make decisions to guide ourselves and others, and apparently their agents, on what we think will work. We see plenty of AI-driven development around Nerves and we see people achieve things that would have been baffling in complexity a year or two ago. People push their products to new heights or they create new libraries and frameworks (see Damir's work on Emerge & Solve ) that simply wouldn't have been feasible without LLMs. We are not inherently against it. We are also well aware of the many good reasons to be concerned about the AI hype. The project doesn't take a hard stance in that because you'll do what you do. We set the contribution policy to ensure we can keep Nerves as a very stable foundation. Feel free to reach out with any questions, notes or concerns. Best place for discussion is the Discord but you can respond to this email to reach me specifically. Lars NervesConf EU at Goatmire ElixirThe Goatmire Elixir website has all the planned speakers and workshop. Check it out :) All the hardware-centric workshops are completely booked solid. You can get on the waiting lists but I don't expect a ton of slots to open up. Very excited for this. And we have some awesome Nerves talks lined up. Don't miss the year's only NervesConf. Oh.. did you hear about Nerves 2?Since it will be teased in the changelogs below I just wanted to say. More info will come about Nerves 2 and what it means. It will be glorious in terms of what it fixes. I think it will be nearly invisible in terms of breakage, carnage and churn. The coming updates contains a lot of groundwork for this that Frank has been hacking away at for a while now. Software updates
Applications updated kiosk_example, v0.4.2
kiosk_example, v0.4.1 This release include dependency updates and a fix for RPi5 WPA3 SAE users. kiosk_demo, v0.4.2
kiosk_demo, v0.4.1 This release include dependency updates and a fix for RPi5 WPA3 SAE users. circuits_quickstart, v0.16.2
circuits_quickstart, v0.16.1
nerves_livebook, v0.19.5 This is mostly a security and bug fix release.
nerves_livebook, v0.19.4
nerves_livebook, v0.19.3
nerves_livebook, v0.19.5 This is mostly a security and bug fix release.
nerves_livebook, v0.19.4
Systems updated This is a security fix release.
Most updates update to nerves_system_br v1.34.1 (see above) and:
And then.. This is a major update to the Linux kernel from the original custom fork to mainline.
Other updates ssh_subsystem_fwup, v0.6.8
nerves_bootstrap, v1.17.0 This release adds support for the Nerves 2.x mix integration. At the time of this release, Nerves 2.0.0 has not been released so mix nerves.new continues to create Nerves 1.x projects. There are no plans to drop support for the Nerves 1.x mix integration since it’s easy to support both. nerves_bootstrap, v1.16.0 This release primarily includes internal code cleanup and more unit tests.
atecc508a, v1.5.0
circuits_spi, v2.1.0
vintage_net_wifi, v0.12.11 This release adds a mechanism for per-device customizations to cookbook configurations. For example, to apply the sae_pwe fix for WPA3 support on Raspberry Pi 5.
vintage_net_wifi, v0.12.1
nerves, v1.15.0 This release adds support for using Apple Container as an alternative to Docker for building Nerves systems on macOS. It’s used automatically if available. (@tomfarm) Reports vary but this seems on par with UTM speeds for building Nerves systems which has historically beaten Docker by a wide margin.
circuits_gpio, v2.3.0 This is a larger than usual feature update. While it is unexpected to be backwards incompatible, please review the compatibility notes below just in case.
ring_logger, v0.11.6
vintage_net_qmi, v0.4.5
Community projectsbb, v0.29.0 - waypoint rates are optional, and survive a transmission (#226) by James Harton bb, v0.28.1
- break the compile-time cycle that deadlocks the Elixir 1.19 compiler (#223) by James Harton bb, v0.28.0
- vectorise
link_transforms/9 over a batch axis (#220) by James Harton bb, v0.27.0
- implement multi-DoF (:planar and :floating) joints (#217) bb, v0.26.0
bb, v0.25.0
bb, v0.24.0
bb, v0.23.0
bb, v0.22.3
bb, v0.22.2
bb_so101, v0.3.0
bb_so101, v0.2.4
bb_so101, v0.2.3
feetech, v0.4.0
feetech, v0.3.0
bb_ik_fabrik, v0.7.0
bb_ik_fabrik, v0.6.0
bb_ik_fabrik, v0.5.0
bb_ik_dls, v0.5.0
bb_ik_dls, v0.4.2
bb_jido, v0.2.0
bb_jido, v0.1.4
bb_kino, v0.4.0
bb_kino, v0.3.8
bb_liveview, v0.3.0
bb_mcp, v0.2.0
bb_servo_pca9685, v0.9.0
bb_servo_pca9685, v0.8.1
bb_servo_pca9685, v0.8.0
bb_servo_pca9685, v0.7.1
bb_servo_pca9685, v0.7.0
bb_pid_controller, v0.3.0
bb_sensor_bmi323, v0.1.4
bb_sensor_ina219, v0.2.4
bb_servo_feetech, v0.5.1
bb_servo_feetech, v0.5.0
bb_servo_feetech, v0.4.0
bb_servo_feetech, v0.3.5
bb_servo_feetech, v0.3.4
bb_servo_robotis, v0.5.1
bb_servo_robotis, v0.5.0
bb_servo_robotis, v0.4.0
bb_servo_robotis, v0.3.4
bb_pigpio_servo, v0.8.0
bb_pigpio_servo, v0.7.1
bb_pigpio_servo, v0.7.0
bb_servo_pigpio, v0.8.0
bb_servo_pigpio, v0.7.1
bb_servo_pigpio, v0.7.0
rebar3_grisp, 2.12.0
Full Changelog : https://github.com/grisp/rebar3_grisp/compare/2.11.0…2.12.0 grisp_tools, 2.9.2
grisp_tools, 2.9.0
You can buy an official Nerves shirt from oswag . Fair trade, organic and high-quality. Family-scale business. Got questions?Trouble-shooting is best done on the Nerves Forum over at Elixir's Forum. But if you have big-picture questions you would like to ask around Nerves, feel free to send them in and we might just have ourselves a column here. Participating in the communityThe Nerves community is found wherever Elixirists gather. But our primary focus is the Nerves Discord . You are very welcome to join us there. Also fine to throw questions into the Elixir Forum's Nerves section . How you can help NervesContribute in the way that works for you:
Finally, if you have questions about the newsletter or want to suggest something you can simply respond to this email. - Lars |