Abdallah El BelkasyA. El Belkasy
Dubai --:-- 120 BPM

Off the bed

3D prints · No. 04

Monitor Buddy: a tiny screen that keeps an eye on my workday

A 1.47-inch ESP32 touchscreen on a printed keyboard dock. It follows Odoo, GitHub, Google Calendar and Claude Code, and it took eight docks before one stopped resetting the board.

  • Black silk PLA
  • 4 h 24 min printing
  • 5 prints
  • 2 parts
  • ESP32-C6
Monitor Buddy on its black printed dock in front of a keyboard, showing THURSDAY NOV 19 2026 with a row of page dots underneath, a white USB-C cable plugged into its right side.
The Buddy on dock version 8, 19 November 2026.

A 1.47-inch screen sits on my keyboard, and it has opinions. When I lock the laptop at lunch, it starts chewing. When one of my pull requests goes red, its eyes turn red and shake. When Claude Code stops to ask me something, it looks up, surprised, and says so. Knock twice on its head and it asks "WHAT'S UP?".

The Buddy's face: two white eyes on black, half-closed and focused, with teal pupils and the caption LOCKED IN
Fig. 01 · LOCKED IN, read from the Buddy's own frame buffer like every screenshot here. The screen is 320 by 172 pixels.

This is the story of how a cheap ESP32 touchscreen became a desk companion that follows my working day: Odoo, GitHub, Google Calendar and Claude Code, on a screen smaller than a matchbox.

Where it started

Monitor-Buddy by IdefixRC is a lovely open-source project under the MIT licence: a Waveshare ESP32-C6-Touch-LCD-1.47 board in a 3D-printed holder, with an animated face that follows the motion sensor, a clock, weather, moon phase, stocks, coins, a GitHub page, a browser-based flasher and a captive-portal Wi-Fi setup. I flashed it, put it next to my monitor, and it made me smile. Then I started wondering what it would take to make it care about my actual day.

If you only want to build one, skip to Build one at the end.

Three days later the firmware had grown to about 6,000 lines, and the laptop had a helper service, a Chrome extension and a handful of small Python tools. Most of that came out of pair-programming sessions with Claude Code, which is also why the Buddy keeps an eye on Claude.

Diagram: on the laptop, a Chrome extension reads www.odoo.com, gh reads GitHub, and GNOME's calendar cache holds Google Calendar; with Claude Code hooks, the screen lock and the microphone they feed buddy-link, a small Python service, every 5 seconds. buddy-link talks to the Buddy over Wi-Fi with every packet sealed with AES-256-GCM, and over USB as a fallback. The Buddy itself fetches weather from Open-Meteo, its GitHub profile and the time.
Fig. 02 · Who talks to whom. The laptop does the private reading and the Buddy only answers.

What it follows

The Buddy only fetches the public bits itself: weather from Open-Meteo, my GitHub streak and stars, and the time. Everything about my work comes from the laptop, where a small Python service called buddy-link wakes up every five seconds and reads:

the screen lock, from logind. GNOME's own ScreenSaver.GetActive stays false when you lock with Super+Escape, which is why my first lock detection passed every test and failed every real lock.

the microphone, from PipeWire. If something records on two polls in a row, I'm ON AIR.

pull requests, reviews and CI, through the gh CLI.

Claude Code: hooks write "needs" or "done" and the project name to a small file, and my status line leaves the 5-hour and 7-day usage in another.

Google Calendar, read-only from the cache GNOME keeps for its online accounts. No Google credentials involved.

Odoo, through the browser.

It sends all of that to the Buddy over Wi-Fi, and over the USB cable when the Buddy is plugged in and the Wi-Fi isn't answering.

The API key that died every day

My first Odoo integration was the obvious one: an API key compiled into the firmware, and the Buddy calling odoo.com itself. The key stopped working the next afternoon. My odoo.com keys expire after a day, so every renewal meant a new build, a new flash, and a fresh secret on a board that anyone with a USB cable can read.

So the Buddy stopped holding a key at all. A tiny Chrome extension (Manifest V3, allowed to talk to www.odoo.com and nothing else) wakes up every minute and asks Odoo for my numbers with the session the browser already has: today's hours, the previous working day's hours, open tasks, what's in development or code review, activities due, and the next meetings. It hands the JSON to a native messaging host, a 30-line Python script that writes it to a private file, and buddy-link forwards it. If Chrome is closed or I'm signed out, the data ages out after 30 minutes and the Odoo page drops out of the rotation. It only ever reads. Nothing writes back to Odoo.

The Odoo page: my trigram (ODOO in these pictures) and the time, a ring showing 2:30 of 8 hours logged, 49 open tasks, 4 in review, and a sample task card, Add CSV export to the weekly report, in the Development stage.
Fig. 03 · The Odoo page, filled with sample data for this post.

Faces with personality

The face is still the heart of it: nine moods you can tap through, plus the status faces the Buddy picks by itself. On every frame it walks down a ladder and shows the first status that applies:

The face priority ladder, highest first: knock greeting, shake, night, on air, meeting soon, focus timer, timer done, laptop locked, Claude needs you, log your hours, CI red, Claude done, locked in. When nothing applies, the plain face.
Fig. 04 · The ladder the Buddy walks down on every frame. The first status that applies wins.

A few favourites:

LOG TUESDAY'S HOURS. If the previous working day has under four hours on my timesheet, the eyes droop and a blue tear runs down. It names the day, so there's no arguing.

CI RED. Red eyes shaking from side to side, with a "!" flashing between them.

LOCKED IN. While one of my tasks is in development, the pupils sweep left to right like they're reading code, and a cursor blinks after the caption.

LUNCH BREAK. I rejected three lunch faces drawn from lines and circles. What worked was a picture generated with Gemini, cropped and warped by a script into two 320 by 172 frames that swap every 260 ms. It chews.

Log your hours

Log your hours: droopy eyes, a blue tear, and the caption LOG TUESDAY'S HOURS

Lunch break

Lunch break: closed happy eyes, a chewing mouth and falling crumbs, with the caption LUNCH BREAK
Fig. 05 · Two of the more than 20 status faces. The lunch face is the only one that started as a generated picture.

Claude needs you

Claude needs you: tall surprised eyes with the caption CLAUDE NEEDS YOU

On air

On air: a red ON AIR sign with the caption IN A MEETING 12:34
Fig. 06 · Claude Code waiting for an answer, and the microphone in use.

Put together, a day looks like this:

An example working day as a timeline: night until 07:00; at the first unlock a YESTERDAY card, then GOOD MORNING; LOG MONDAY'S HOURS until they are logged; LOCKED IN; MEETING IN 5 MIN, then ON AIR; LUNCH BREAK while locked between 12:00 and 14:00; a focus timer laid flat, then FOCUSED with fireworks; DAY DONE when locked after 17:00; the bouncing Buddy logo after 30 minutes away; night from 23:00.
Fig. 07 · An example day, from the first unlock to the screensaver.

The first unlock of the day brings a YESTERDAY card (hours, tasks I touched, pull requests merged and reviewed), then the Today page. Meetings from Odoo and Google Calendar get a five-minute countdown. Laying the Buddy flat starts a focus timer that counts up. While it runs, the laptop turns notification banners off and keeps the screen awake with the Caffeine extension, which lets go after 30 idle minutes so an unattended laptop still locks. Locking up after 17:00 shows a DAY DONE recap.

The Today page: the next meeting, Weekly sync at 19:17, 5:15 logged and 0:00 focus, 2 to review, 1 with changes, 3 open, 2 activities due and 12 tasks
Fig. 08 · The Today page, with sample data for this post.

Knock knock

The Buddy also reacts to being handled. Shake it and it goes dizzy, spiral eyes and circling stars, then gives you a flat "REALLY?" before showing the Today page. Spin it and it looks surprised. Knock twice on its head and it greets you.

While shaken

Dizzy: spiral eyes with stars and the caption WHOAAA

Right after

Unimpressed: flat half-shut eyes with the caption REALLY?
Fig. 09 · What a shake gets you, in order.

The knock was the hardest feature to get right, and the one that taught me the most. My first detector looked at the change in the total pull, the length of the acceleration vector. A knock from the side barely changes that length, so desk knocks read 0.08 to 0.19 g, right on top of ordinary desk bumps. I then spent far too long nudging thresholds by feel: too strict and it missed knocks, too loose and typing set it off.

What fixed it was measuring. The Buddy's health answer now carries its last eight knock strengths, and its serial status line prints the largest jolt every 1.2 seconds. With real numbers in front of me, the cause was obvious, and so was the fix: measure the change in every direction, against a slow running average. Knocks on the Buddy itself now read 0.27 to 3.2 g, comfortably above anything the desk does.

Chart of measured jolts on a log scale: at rest 0.01 to 0.05 g, desk bumps 0.10 to 0.17 g, desk knocks with the first method 0.08 to 0.19 g, knocks on the Buddy with the final method 0.27 to 3.2 g, screen taps and handling 1.1 to 2.5 g. A knock starts at 0.25 g; still means under 0.08 g.
Fig. 10 · Measured jolts on a log scale. The first method put desk knocks right on top of desk bumps.

A dedicated FreeRTOS task reads the QMI8658 motion sensor every 3 ms. A knock is a jolt of at least 0.25 g after the Buddy was still, and the first one needs 150 ms of stillness before it, which typing never provides. The second must come 80 to 700 ms later. Anything under a quarter of the first knock is the Buddy rocking on its stand, and a third strong jolt cancels the pair. Screen taps arrive with a touch, and picking the Buddy up never lets it get still.

Diagram of a double knock: still for 150 ms, knock 1 at 1.1 g, a small rocking echo ignored, knock 2 at 0.78 g within 80 to 700 ms, then 250 ms with no third knock gives the greeting. Not knocks: a tap on the screen, picking it up, a third strong jolt.
Fig. 11 · What counts as a double knock, and what does not.

In the last test it caught two double knocks out of three, ignored a single knock, and fired on nothing else.

Memes on a 1.47-inch screen

One page plays animations from the microSD card, and three of them play by themselves as reactions: a ring that fills up and bursts into confetti when my Odoo hours pass eight for the day, a green tick that draws itself when the last failing pull request goes green, and fireworks after a focus session of 25 minutes or more. After 30 minutes away, your name (you give it in the installer) bounces around the screen like the logo of an idle DVD player, and yes, it lands exactly in a corner twice per loop.

My own card also holds a few classics of the old internet, and those belong to their creators, so they stay on my card. Everything that ships with the project I drew with a script: the three reactions, the bouncing Buddy logo, a starfield, code rain, demo-scene fire, a game of Pong where nobody ever misses, and an install bar that crawls to 99% and fails.

An animation drawn for the Buddy: a progress bar at 33% under the words DOWNLOADING COFFEE...
Fig. 12 · One frame of the install bar. It never finishes.

A helper script fits any GIF to the screen (three canvas sizes drawn at 4×, 2× or 1×, one shared 64-colour palette), and another sends it to the Buddy over the same link everything else uses.

Locking it down

The Buddy sits on an office desk, shows my tasks and talks over Wi-Fi, so it got the same attention as the faces.

A sealed link. Every UDP packet is encrypted and authenticated with AES-256-GCM. The nonce starts with the laptop's clock in milliseconds, and the Buddy only accepts stamps that keep increasing and sit within a minute of its own clock, so a recorded packet is useless a minute later. The Buddy never opens a connection. It only answers.

Signed updates. Firmware sent over Wi-Fi carries an ECDSA P-256 signature, and the private key never leaves the laptop. The Buddy only has the public half, so someone who somehow got the link key still couldn't install firmware.

Rollback. There are two firmware slots. A new firmware boots on trial and is kept only once it hears from the laptop again. If it crashes before that, the bootloader goes back to the old one. That found a real bug: a start-up crash when a network fetch looked up a host name while the time sync had its own DNS query open. The Buddy rolled itself back, the crash dump kept on flash pointed at the cause, and the time sync now gets IP addresses instead of names.

A privacy lock. While the laptop is locked, swipes, taps, the game, the Wi-Fi setup hotspot and the Today pages after a knock or a shake are all blocked. Anyone walking past sees a face, not my task list.

No borrowed secrets. Odoo comes through the browser, I deleted the stock-price API key, and I erased the spare firmware slot that still held old images with the expired Odoo key. What remains on the board is the link key and the Wi-Fi passwords.

The honest part. USB is still the master key. There's no flash encryption and no secure boot, so anyone with a cable can read the board or flash it. It lives on my desk, not in a hallway.

Sequence diagram of a signed update: the laptop signs the image with ECDSA P-256; it sends B with the size and signature and gets back the offset to start from; it sends 1 KB D pieces; the Buddy writes the spare slot, checks the signature against the public key in its firmware, and refuses a mismatch; it restarts into the new slot on trial; the next packet from buddy-link keeps it, and a crash before that rolls it back. A broken-off update goes on where it stopped.
Fig. 13 · A signed update, step by step.

Signed updates worked perfectly on my desk and fell apart in a weak spot on a charger. There, 8 of 40 sealed pings got lost, the median round trip was 187 ms, and three installs broke off between 67 and 135 KB of a 1.9 MB image.

Chart of the Wi-Fi link: pings lost 0 of 40 on the desk, 8 of 40 in the weak spot and 13 of 20 in its worst run; round trip median 4 to 60 ms on the desk, 187 ms in the weak spot, slowest 762 ms; updates in the weak spot broke off at 67 to 135 KB of 1.9 MB.
Fig. 14 · The same link on my desk and in a weak spot on a charger.

So updates became resumable. The Buddy keeps a broken-off update for ten minutes, and because the signature is deterministic (RFC 6979), running the same command again sends exactly the same header. The Buddy recognises it and answers with the offset where it stopped. I tested it by cutting the Wi-Fi at 63%: the second run went on from 65% and finished. Over USB an install takes 23 to 25 seconds. Over Wi-Fi, in 1 KB pieces, about 90.

Chart of install times: 23 to 25 seconds over USB, about 90 seconds over Wi-Fi; a first run cut at 63% and a second run that went on at 65%
Fig. 15 · Install times, and the update I cut at 63 %.

From 12 to 30 frames a second

The firmware I started from sent the whole 320 by 172 frame to the display on every pass, which takes about 30 ms on its own. Add Wi-Fi upkeep, the motion sensor, touch and a fixed delay, and the face ran at 11 to 12 frames a second.

Chart of frames per second: the start 11 to 12; Wi-Fi upkeep every 500 ms, 14; only changed rows sent with frames paced, 29 to 30; knock watch on a 100 kHz sensor bus, 26 to 28; sensor bus at 400 kHz, 29; animation page with GIFs from the SD card, 21 to 23. The game went from 13 to 16 up to 29 to 40 with its own partial flush.
Fig. 16 · Frames per second after each change.

Doing Wi-Fi upkeep every 500 ms instead of every pass bought a little. The big win was hashing every row of the frame buffer and sending only the rows that changed, with frames paced at 33 ms: the normal pages went to 30. The eyes still move on springs that step every 70 ms, with the frames in between blended, so the face kept the feel it had at 12. The Bug Hop game, a one-tap runner hidden one swipe past the animations, has its own partial flush and no pacing, so it runs at 29 to 40. Adding the knock watch cost a few frames while the sensor bus ran at 100 kHz, and moving it to 400 kHz brought them back. GIFs from the SD card land at 21 to 23, probably because the card shares its SPI bus with the display.

A dock for the keyboard

The original holder sticks to the side of a monitor. Mine wanted to live on the keyboard, where a knock is one finger away and laying it flat for a focus timer is a single move. So the holder became the head of a two-part dock: a 7 mm slab that sits on the keyboard's top strip, and a head that leans the screen back toward me. The head drops into a dovetail groove, slides 8 mm and clicks. Slide it back and it lifts off with its cable.

Docked

The Buddy on its dock, showing the weather page

Lifted off

The head slid out of the base and lifted, still running
Fig. 17 · Two frames from a phone video on 19 November. The head slides 8 mm and lifts off with its cable.

It took eight versions. Version 7 looked finished and reset the board every time I seated it: a ledge inside the holder stood exactly where the BOOT and RST buttons stick out of the board's edge. Version 8 clears both buttons by 1.5 mm and leaves two small pin slots to reach them.

Small bugs, big lessons

millis() | 1. Time stamps were stored as millis() | 1, so that zero could mean "unset". That can put a stamp one millisecond in the future, and then millis() - stamp underflows to about four billion. "Lie flat for two seconds" fired instantly: a surprise focus timer that also muted my notifications. Every such comparison now goes through a helper that handles it.

A button with a mind of its own. The BOOT button read as pressed during a restart, and the upstream rule "hold BOOT for five seconds to forget the Wi-Fi" wiped the saved Wi-Fi three times in one day. BOOT lost that job. Today a press locks the laptop, which travels over the same sealed link as everything else.

Add the knock and the API key, and two rules stick: measure before you tune, and don't store a secret you can borrow from somewhere safer.

What's next

A battery: the board has a charger chip, and a small LiPo with a protection board would let the Buddy leave the cable behind. And the Buddy could use a few more faces, which, if the lunch face taught me anything, will start as generated pictures rather than circles.

Build one

This is a free, open-source hobby project; nothing is for sale. You need a Waveshare ESP32-C6-Touch-LCD-1.47 (the touch version, ~US$15, e.g. from Waveshare), a small microSD card, a USB-C data cable and about 23 g of PLA.

1. Print the dock (two parts, about 1 h 24 min at 0.16 mm) or the original holder. The original holder, with its print settings, is on MakerWorld. My dock goes up there as a remix of it; the link lands here and in the README when it is listed.

2. Install from the browser. Plug the board in, open the installer in Chrome or Edge, click Connect your Buddy, then Install. One form asks for your Wi-Fi and your city. Nothing has to be built or installed on the computer.

3. Copy the animations from the release's monitor-buddy-v1.0.0-sdcard.zip onto the card and put it in while the Buddy is unplugged (the card is read at start-up).

4. Connect your laptop (Linux, optional): install monitor-buddy_1.0.0_all.deb from the latest release (Ubuntu and Debian), or download the project from github.com/Abdaishere/monitor-buddy and run open-app.sh (or ./setup.sh in a terminal). With the Buddy on USB, click Set up. It makes the keys, hands them to the Buddy over the cable, starts the helper for the lock, microphone, pull request, calendar and Claude Code features, and offers the Odoo extension. It can be run again at any time and only does what is left.

5. Make it yours. The same app is the Buddy's editor: it shows the Buddy's screen live next to its settings (the real firmware, built to run in the page), lets you drag the pages into your own order, and writes the changes over the cable, with undo. The editor also runs on Windows.

Updates come from the same installer page, or over Wi-Fi with python3 tools/buddy_flash.py. The README has the steps with screenshots, and the handover document has every detail.

Credits

Monitor Buddy stands on Monitor-Buddy by IdefixRC (MIT), which builds on the Tiny ESP DeskBuddy idea from schematik.io and took additional face designs from DESKBUDDY-1.0 by Edison Science Corner. The firmware uses Arduino_GFX, ArduinoJson, U8g2, AnimatedGIF and AyresWiFiManager, and the weather comes from Open-Meteo. The dock's head is built on IdefixRC's printed holder, so the dock is published on MakerWorld only, as a remix of it. Thanks to IdefixRC and to the original's contributors, AmyJoT and Killo1988. The browser installer uses esptool-js by Espressif and posix_tz_db by Nayar Systems. The full list is in CREDITS.md.

Built on

Where the ideas came from. Their files stay on their pages.

  • Monitor-BuddyIdefixRC · MakerWorld · MakerWorld Exclusive LicenseThe holder my dock's head is built on, and the idea of a face beside the monitor.
  • Monitor-Buddy firmwareIdefixRC and contributors · GitHub · MITThe firmware mine grew from: the face, the settings engine, the Wi-Fi setup.

How it was printed

Printer
Creality K1 Max, rooted, Klipper
Slicer
OrcaSlicer 2.5.1, K1M 0.20 Standard, Black Silk PLA (K1M)
Board
Waveshare ESP32-C6-Touch-LCD-1.47, 8 MB flash
Dock v8
Head and base on one plate, 0.16 mm layers, first layer 0.24 mm, 1 h 23 min 39 s and 22.91 g in the slicer
Head
Standing on its end, 6 walls, 25 % infill
Base
Flat, 100 % infill, 60 by 31.4 by 7 mm
Supports
Normal (auto), build plate only

5 prints: the original holder, a wider holder I cancelled after 4 minutes, and dock versions 6, 7 and 8. Versions 1 to 5 never left the slicer. Times are from the printer's history.

The model

The original holder is IdefixRC's. Its licence keeps remixes on MakerWorld, so my dock goes up there as a remix and not here. The firmware and the laptop tools are on GitHub under MIT.

Designer
IdefixRC

Not hosted here. Get it from the designer’s page, where the license travels with it.

Open the model page

Off the bed