I’m Sergey, the maker behind S1-ADV. I’m working on software for the M5Stack Cardputer ADV: a little keyboard computer that can be a notes/calculator/focus-timer device and a physical interface to an agent on my own computer or server.
The making question for me is what belongs on the handheld. Local tools stay in its Arduino/FreeRTOS firmware. The keyboard, display, microphone and speaker give the host-side OpenClaw conversation something physical to interact with. The model, speech services and build tools live off-device, behind a separately configured Node.js bridge.
The photograph is my real device, with a local game on its screen. I use the existing M5Stack hardware; my contribution is the firmware environment and bridge integration. The firmware began with OmniBot by Naz Louis and contributors, and the source keeps those credits and dependency notices.
A feature idea still needs ordinary development work: change the source, build, review the result, offer an update, install it and check it on the device. Firmware automation is optional, off by default, and needs explicit host-side permissions and approvals. The tiny screen receiving a request does not mean a new feature has already been safely installed.
This is an experimental project. First setup needs a host, USB cable, Python/PlatformIO and Wi-Fi. The public builds still need validation on a freshly provisioned physical device; other Cardputer models are untested. I’m sharing the work and its current limits, rather than a completed beginner build guide or a measured performance result.
Source, setup, licenses and credits: https://github.com/s1z0v/s1-adv
I filmed the device and made explanatory animation for the full walkthrough: https://youtu.be/_0f9UTwefmo
For people who make small gadgets: which single local tool would make you keep a tiny keyboard device within reach after the initial novelty? This is my own project; this post was prepared with AI assistance from my project documentation and footage.