RECENTLY CHECKED
All projects →
CAIBI guided build · Playful objects

A desk buddy with expressive eyes

A USB-powered character with three expressions and one button. No voice service, motors or battery in the first version.

Not yet assessed Not built by CAIBI

A staged completion guide and prompts. The parts and finished result still need physical validation.

Share your build

What you will work towards

A small character that blinks, changes expression and responds to a button. Give it a personality through animation and an original printed shell.

CAIBI’s proposed addition: Start with USB power, a supported display and three expressions. Add one input and idle sleep before considering voice or moving parts.

Guide version 1.0. AI can help explain, adapt and debug; you still measure, assemble and test the physical result.

Start with the original

Software foundation

Source read 10 October 2026. RoboEyes is a GPL-3.0 animation library, not a conversational AI. The linked C6 touchscreen build is a separate hardware route; compatibility with other displays is untested.

Watch the creator’s demonstration

FluxGarage RoboEyes animation demonstration, not a CAIBI physical build

Watch on YouTube · FluxGarage: original library demonstration · Source context

Parts to confirm before buying

  • Exact controller board and a display supported by a working driver example; record the screen controller, resolution and wiring
  • RoboEyes and its documented graphics dependencies; retain GPL licence obligations if distributing derivative firmware
  • One suitable button, USB supply/cable, measured fixings and enclosure material

Use the source wiring and bill of materials as the starting point. Confirm exact variants, availability, tools and complete cost before ordering.

The completion route

  1. Photograph the board identity and run the manufacturer’s display example unchanged. Save the dependency versions and serial output.
  2. Run the upstream eye example on compatible hardware; if the display needs a port, stop and isolate that work before adding features.
  3. Add one debounced button that cycles three expressions without blocking the animation. Add idle dimming or sleep with a reliable wake action.
  4. Measure the working assembly and print a fit coupon before a removable shell. Keep the USB port and reset accessible.

Prompts to move it forward

Copy a prompt into your AI tool with the source material and your actual parts. Work through one small step at a time and check the output before using it. Choose an AI tool or practise the skills first.

Check the source before buying
Review the source material I supply for A desk buddy with expressive eyes. Make a table of what is provided, missing, contradictory or dependent on a paid service. Identify exact hardware revisions, firmware files, library versions, CAD files and licences. Separate creator claims from your proposed additions. Do not fill gaps with guessed specifications. Finish with one small test that can resolve the biggest uncertainty before I buy parts.

Sources:
FluxGarage RoboEyes: https://github.com/FluxGarage/RoboEyes
Flox-linked Tiny ESP Desk Buddy: https://www.schematik.io/projects/build-an-esp-c6-touch-lcd-gadget
Deskimon: separate paid build route: https://creative-chance.com/products/poko-deskimon
Plan the next step
Help me build a USB desk character. First ask for the exact board, display driver, working example and library versions. Check RoboEyes compatibility and licence. Make one change at a time: three expressions, one debounced input, non-blocking timing and idle/wake behaviour. Do not invent pins or add voice, motors or a cloud service. Provide a compile check and observable test for each step.

Sources:
FluxGarage RoboEyes: https://github.com/FluxGarage/RoboEyes
Flox-linked Tiny ESP Desk Buddy: https://www.schematik.io/projects/build-an-esp-c6-touch-lcd-gadget
Deskimon: separate paid build route: https://creative-chance.com/products/poko-deskimon
Design a measured enclosure
Design an original shell for the measured working display and board. Ask for outlines, mounting holes, screen active area, USB plug clearance and button travel. Make a small fit coupon first, then a removable back with cable clearance and stable feet. Keep reset reachable; do not copy another creator’s character.

Sources:
FluxGarage RoboEyes: https://github.com/FluxGarage/RoboEyes
Flox-linked Tiny ESP Desk Buddy: https://www.schematik.io/projects/build-an-esp-c6-touch-lcd-gadget
Deskimon: separate paid build route: https://creative-chance.com/products/poko-deskimon
Check and document the result
Create a test log for A desk buddy with expressive eyes. Intended outcome: A small character that blinks, changes expression and responds to a button. Give it a personality through animation and an original printed shell. Separate expected behaviour from observed results. Include power restart, disconnected inputs, communication failure and the actual physical use. Ask me to provide results, firmware versions, changes, photos and unresolved problems. Never mark a test passed without my evidence.

Sources:
FluxGarage RoboEyes: https://github.com/FluxGarage/RoboEyes
Flox-linked Tiny ESP Desk Buddy: https://www.schematik.io/projects/build-an-esp-c6-touch-lcd-gadget
Deskimon: separate paid build route: https://creative-chance.com/products/poko-deskimon

What to test and record

  • Run for 30 minutes on the bench; record resets, flicker and dropped input. This is a functional trial, not certification.
  • Cycle every expression with 20 button presses and check for double triggers.
  • Test idle, wake and three power cycles; record exact observed behaviour.
  • Photograph the fit coupon and enclosed unit from front and rear, with the guide version.

Keep photos, exact parts and software versions with the test log. Failed or incomplete attempts are useful evidence too.

A possible next version

Once the simple companion is reliable, try a local focus timer. Voice, networking and a different display are separate extensions.

Community ideas & builds

What builders are contributing

Suggest something useful, improve a route or share what you made. Contributions are reviewed before publication. Community builds remain attributed to their builders.

Contribute to this idea

Loading reviewed contributions…