Image credits and source versions

Clawd Mochi displaying its Claude Code screen ↗ · Yousuf Amanuel · MIT
Clawd Mochi web controls shown by the creator ↗ · Yousuf Amanuel · MIT

CAIBI ASSESSMENT

Clawd Mochi

CAIBI VERDICTBUILD IT

A small ESP32-C3 desk companion with animated faces, web controls and a published low-cost parts list.

See what the build involves Original source ↗

Build or buy?

Compare the documented build with the purchase reference.

Build it yourself

Build estimate£5–£6Source estimate · high confidenceOne companion; electronics and enclosure material

Time: ~1 hour
Difficulty: 2/5
Physical processes: 3D printer · ESP32

See build requirements →

Purchase reference

Buy price referencePrice not checkedNo priced alternative recorded

Check the source for the exact model, availability and what is included.

Check comparison evidence →

Purchase comparison not yet priced

What the prices cover

Creator-published parts cost, with GBP shown as an approximate conversion.

Includes: Published electronics and basic printed enclosure materials.

Not included: 3D printer ownership; Shipping; Optional modifications.

Build evidence recorded 4 Sep 2026. Currency conversions are approximate.

Commercial desk companions exist, but they do not reproduce this small open ESP32 platform closely enough for a savings claim.

BUILD AT A GLANCE

Source view and main parts

Check the source ↗

**Clawd Mochi displaying its Claude Code screen**Yousuf Amanuel · MITSource and version ↗

Clawd Mochi · Yousif Amanuel ↗

PHYSICAL BUILD7 key parts or groups

No.	Source specification
01	ESP32-C3 Super Mini
02	1.54 inch ST7789 240 × 240 TFT display
03	8 short jumper wires
04	2 × M2 × 6mm screws
05	Double-sided tape
06	USB-C cable
07	3D printed PLA or PETG case

Full source specifications

ESP32-C3 Super Mini
1.54 inch ST7789 240 × 240 TFT display
8 short jumper wires
2 × M2 × 6mm screws
Double-sided tape
USB-C cable
3D printed PLA or PETG case, about 30g

TOOLS / PROCESSES2 involved

3D printer
ESP32

The real-world work

YOU STILL HAVE TOThe real-world work

Print and finish the enclosure
Wire the display to the ESP32-C3 correctly
Route and secure the electronics inside the case
Judge whether the finished object looks and feels tidy enough to keep on a desk

THE BUILD SEQUENCE

How it comes together

1Preparation

Print and test-fit the case
Print the published case, then test-fit the display before fixing or soldering anything. The creator recommends 0.15 to 0.20mm layers, 15% gyroid and supports for the display overhang.
YOU
Wire the display
Connect the ST7789 display to the ESP32-C3 using the published GPIO mapping. The source explicitly requires 3.3V for VCC.
YOU

2Build and assembly

Set up Arduino
Install ESP32 board support and the Adafruit graphics libraries, then apply the board settings published by the project.
AI + YOU
Flash the firmware
Upload the supplied sketch over USB-C. AI can help diagnose board, library or compile issues, but the source firmware already provides the baseline.
AI + YOU

3Configure and test

Assemble the enclosure
Route the wires, secure the display, fix the ESP32 to the back plate and close the case around the USB-C connection.
YOU
Connect and customise
Join the device Wi-Fi hotspot, open its browser controller, then change animations, views, colours or code once the base build works.
AI + YOU

Benchmark this project

Use the Clawd Mochi prompt. Compare what different models deliver, then add what happened when you tried it.

Try this benchmark

View the project prompt

CAIBI adaptation · Prompt 1.0 · Project source

Prompt for Clawd Mochi

CAIBI project benchmark: Clawd Mochi
Prompt version 1.0

Help me build Clawd Mochi using the existing creator project at https://github.com/yousifamanuel/clawd-mochi. This is a CAIBI benchmark adaptation of the project build brief, not a claim about how the creator used AI.

Project context:
- A small ESP32-C3 desk companion with animated faces, web controls and a published low-cost parts list.
- Build context: ESP32-C3 Super Mini; 1.54 inch ST7789 240 × 240 TFT display; 8 short jumper wires; 2 × M2 × 6mm screws; Double-sided tape; USB-C cable; 3D printed PLA or PETG case, about 30g.
- Where AI helps: Firmware changes, UI changes, Debugging.
- Physical work: Print, Wire, Assemble, Fit.
- Main limitation: The concept is simple enough that finish quality matters. A rough print and untidy wiring quickly make it feel like a prototype.

Read the source first. Use its published design, files, dimensions and parts as the baseline; do not redesign it unless a missing detail requires a clearly labelled proposal. If you cannot access a source or verify a revision, say so.

Provide one practical build package:
1. Design and files: explain the source design, link the original editable files, and identify missing files or modifications.
2. Parts and fabrication: give quantities, exact variants and compatibility, plus a cutting or printing list where applicable. Preserve source dimensions; flag anything unconfirmed.
3. UK and US purchasing: direct product links, checked dates, stock, pack sizes, taxes, delivery and regional costs. Mark unverifiable details as unknown; do not invent links, prices or availability.
4. Assembly: an ordered guide covering fabrication, fitting, wiring or software as applicable, setup, checks and troubleshooting.
5. Cost and time: separate parts, fabrication, delivery, hands-on time and machine time, with assumptions and exclusions.
6. Function and ease: a test plan for the project's stated purpose, likely difficulties, required skills and any corrections or limitations.

Keep source facts, your proposals and items needing physical verification distinct. An estimate is not a measured build result. Do not claim to have built or tested hardware. Include failed attempts and omissions. If a section does not apply, say why.

Use the source as accessed during this run and record its revision or access date. The prompt is fixed; the linked source can change.

Open and copy prompt →

Benchmark results 0

No reviewed results yet for Clawd Mochi. Add the first result →

AI IN THIS PROJECT

Get AI help on this build

CAIBI · AI CAN HELP

AI can help with

Firmware changes
UI changes
Debugging

CAIBI · AI CAN'T DO

You still need to

Print and finish the enclosure
Wire the display to the ESP32-C3 correctly
Route and secure the electronics inside the case
Judge whether the finished object looks and feels tidy enough to keep on a desk

Original source AI use and prompts

SOURCEThe original project does not publish an AI prompt

The prompts below are CAIBI helpers for this build. They are not presented as instructions from the creator.

CAIBI STARTING PROMPTS

Copy a prompt for this build

Each prompt tells AI to keep the original project source as the reference and to flag anything you must verify on the real build.

Ways to take it further

AFTER THE FIRST BUILD

Ways to take it further

New expressions and animationsWeather or clock viewsBuzzerTouch or other sensorsMQTT or Home Assistant integrationOTA updates

More routes and resources

OTHER WAYS TO GET THERE

You do not have to follow one route.

ORIGINAL BUILDFollow the creator route

Use the published files and instructions as the baseline.

OUTSOURCE A PROCESSGet specialist fabrication done

You do not necessarily need to own every capability used here: 3D printer, ESP32.

ALTERNATIVE PROJECTImageGenCam

A buildable Raspberry Pi camera designed around a Codex-assisted hardware and software workflow.

REVIEWED RESOURCES

Useful places beyond the main source

FILESClawd Mochi case on MakerWorld

Published printable enclosure files linked by the creator.

SOURCE · CAIBI · BUILDERS

What supports the verdict

SOURCEYousif Amanuel

Source available with detailed beginner build instructions

Open source ↗

CAIBIBUILD IT

Cheap, compact and easy to modify. It is a good example of AI-assisted embedded work becoming approachable without turning into a large electronics project.

Evidence: Strong

BUILDERSNo published reports yet

Actual time, cost, changes and outcomes appear here after submitted builds are reviewed.

Be the first builder to report ↓

Leave a build review

HAVE YOU MADE THIS?

Leave a build review.

First-hand evidence improves the assessment

What we want to know

What happened when you actually tried to make it.

Did it work?
Actual time and cost
What did you change?
What was harder than the source suggested?
Would you build it again?