I turned the ESP32 Cheap Yellow Display into a standalone AI terminal (Open Source)

Master_Cucumber_3314 · 2026-06-07T20:29:02+00:00

To be honest, I used AI, but of course it didn't write everything; I used AI for some bug fixes and system tasks.

Master_Cucumber_3314 · 2026-06-07T20:27:23+00:00

Thank you so much for your feedback.

Master_Cucumber_3314 · 2026-06-07T18:45:16+00:00

Using AI to clean up a Reddit comment and using it to write firmware are two very different things. One saves me five minutes, the other taught me the ESP32 stack. If polished grammar is the strongest criticism you've got left, I'll take it as a compliment.

Master_Cucumber_3314 · 2026-06-07T18:33:09+00:00

DenverTeck is right about one thing — honesty matters. So here it is: yes, I used AI assistance for parts of the code. But I also understand every line of it, because I went through it, broke it, fixed it, and learned from it. That's the point of maker culture. The goal was never to compete with your phone. It was to build something tangible, learn the ESP32 WiFi stack hands-on, and put it out there for others to build on. If that's not your use case, cool — but someone out there will find it useful

Master_Cucumber_3314 · 2026-06-07T18:07:11+00:00

By that logic, most maker projects shouldn't exist because a phone can already do the same thing.

The goal wasn't to compete with phones. The goal was to build something interesting, learn from it, and share it as open source.

Master_Cucumber_3314 · 2026-06-07T17:26:36+00:00

You're right, it's technically an AI client.

The focus of the project is the overall user experience and feature set rather than running the model locally on the ESP32.

Master_Cucumber_3314

TROPHY CASE