[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"$f1rzt2ycnayvfp":3},{"code":4,"message":5,"data":6,"timestamp":37},10000,"success",{"full_name":7,"position":8,"description":9,"language":10,"stars":11,"forks":12,"stars_gained":13,"age_days":14,"hn_threads":15,"one_liner":16,"summary_md":17,"topic":18,"github_topics":21,"license":27,"homepage":28,"updated_at":29,"history":30},"jamro\u002Ftiny-engineer",16,"A small desktop robot that brings an AI coding assistant to life, physically acting out when it reads files, thinks, writes code, and finishes work.","C++",869,108,27,64,[],"A 3D-printed desk robot that mirrors an AI coding agent's reading, thinking and writing through motion, faces and a bell.","**Adoption takeaway:** this is a build-it-yourself desk object, not a software install. It is worth considering if you want a physical signal for long agent runs and are comfortable with a soldering-free but multi-part ESP32 assembly.\n\n## The problem\n\nAgentic coding sessions now run for minutes at a time, and the only feedback is a scrolling terminal. You either keep switching tabs to check progress, or you let the run finish unseen. Tiny Engineer changes the output side of that loop: hook scripts attached to Cursor, Claude Code or Antigravity send poses over Wi-Fi, and a small robot on the desk looks around when files are read, types when code is written, looks up while the agent thinks, and rings a bell when the task ends. The result is a secondary, ambient status indicator you can read from across the room.\n\n## What's different\n\nThis is not a software-only indicator light. The project combines a printable body, an open-source KiCad main control board, an ESP32-C3 firmware and a Node hook client, with the board designed so the ESP32, five SG90 servos, an OLED and a speaker plug in rather than requiring soldering. Motions are driven by pose messages sent either over HTTP or over framed USB serial, so any script that can POST can drive it; the README points to a documented [HTTP API](https:\u002F\u002Fgithub.com\u002Fjamro\u002Ftiny-engineer\u002Fblob\u002Fmain\u002Fdocs\u002Fapi.md) and [integration guide](https:\u002F\u002Fgithub.com\u002Fjamro\u002Ftiny-engineer\u002Fblob\u002Fmain\u002Fdocs\u002Fintegration.md) beyond the one-command `npx` setup for three named agents. Speech playback is exposed as a separate endpoint, which makes the robot usable as a small notification device even outside coding.\n\nThe trade-off is scope: the author labels the build difficulty \"medium\" and describes it as a fair first hardware project for a software engineer rather than a one-LED kit. You take on ordering a PCB from a fab, printing or ordering parts, and assembling servos and screws. The default client is an npm package, so the plug-and-play path assumes a Node-capable machine; the HTTP and serial interfaces are the escape hatches for other setups. Licensing is split: software is MIT, while the CAD and PCB designs use CERN-OHL-S-2.0, and the name and logo are explicitly not licensed.\n\n## Who should try it\n\nA good fit is a developer who already runs long agent sessions in Cursor, Claude Code or Antigravity and wants a desk object that shows state at a glance, and who is willing to treat the PCB and print work as part of the hobby. Someone with a 3D printer and basic experience plugging modules onto a board will get the most out of it. A poor fit is anyone who wants a pure software status light, or who needs a finished product out of the box: the assembled board is still only a proposal in a discussion thread, not something you can currently buy. If you have no printer, the documented alternative is ordering prints, which adds a step but keeps the project open to non-printers.\n\n## Requirements and limitations\n\nThe hardware list is concrete: the main control board plus ESP32, five SG90 servos, an OLED, a speaker, M2 screws and a 5 V supply rated at least 2 A. You also need a 3D printer and filament or an external print order. Assembly is described as medium difficulty, and the project provides a primer for software engineers new to circuits. On the software side, the default `npx` client targets Cursor, Claude Code and Antigravity; Codex, Windsurf and other tools must go through the HTTP API or serial protocol, which is more setup for you. Ongoing upkeep means keeping the firmware and hook script in sync as integrations evolve; the roadmap lists more agent integrations and a simpler build process as future work, not current features.\n\n## HotRepo's take\n\nHotRepo recorded 862 stars on 2026-10-24 and 865 on 2026-10-25, with two days on the daily trending board; the tracked sample is too short to judge persistence. The repository was created 2026-08-21, so the project is young. Before committing to a build, check the [shopping list](https:\u002F\u002Fgithub.com\u002Fjamro\u002Ftiny-engineer\u002Fblob\u002Fmain\u002Fdocs\u002Fshopping.md) against what is locally orderable and confirm your agent appears in the integration docs.",{"slug":19,"name":20},"hardware","Hardware & IoT",[22,23,24,25,26],"ai-agents","antigravity","claude-code","cursor","esp32","NOASSERTION",null,"2026-10-25T03:12:56Z",[31,35],{"date":32,"stars":33,"stars_gained":34},"2026-10-24",862,26,{"date":36,"stars":11,"stars_gained":13},"2026-10-25",1792906133]