Tiny Engineer CLI
CLI connects Claude Code and Cursor events to a desk robot's movements, screen expressions and end-of-task bell
- 1,074 ★ on the repository
- Last commit
Extended access
Why this level
- Setup changes editor hooks that subsequently invoke a local CLI
- Commands reach physical hardware and can move servos or play audio
Install
- Works in
In your terminal, with SkillFoxx CLI
npx skillfoxx add cli/tiny-engineerDetects the agents on your machine, shows the access level and pins the version.
Other ways to install
Access and checks
How we reviewExtended accessThe tool runs code or makes network calls and only reads external data.
- Setup changes editor hooks that subsequently invoke a local CLI
- Commands reach physical hardware and can move servos or play audio
This is third-party code. Review the repository files before installing.
What it does
Tiny Engineer CLI sends coding-agent events to a small ESP32 desk robot. Reading or writing activity changes its pose and screen expression. A bell can announce that a task has finished. Setup adds hooks for the selected editor to a project. They invoke a shared CLI that sends an animation name over local HTTP or USB serial. Ready-made integrations cover Claude Code, Cursor and Antigravity; other agents can call the HTTP API directly. The robot can also play short audio clips. A separate skill prepares speech audio and sends it to the device. Build or buy the device and install its firmware separately.
Who it is for. For developers and electronics hobbyists who want a physical device beside their computer to reflect a coding agent's activity.
Good fit when
- Notice a long task finishing through a robot's movement or bell
- Connect an assembled robot to editor events without writing your own HTTP scripts
- Send events over a serial port in a USB-only environment
- Play a short spoken message through the robot’s speaker
Not a fit when
- You need software notifications without building or buying a device
- You need a general industrial robot or ROS interface
- You expect the robot to verify code quality or perform the agent's task
Example request
Connect my assembled Tiny Engineer to Claude Code over USB. Show which project files setup will change, then check connectivity and the completion signal.Limitations
A built, flashed robot and a 5 V supply rated for at least 2 A are required; the CLI does not replace the device. HTTP needs network reachability between computer and robot; firmware uses 2.4 GHz Wi-Fi. Device token checks are optional; when enabled, supply TINY_ENGINEER_TOKEN through the environment or user configuration. A project .env can override the user’s connection settings; inspect doctor warnings before sending commands.
How to disable. Use `npx -y tiny-engineer uninstall cursor --yes` for Cursor hooks, choosing the appropriate editor name for another integration. This removes Tiny Engineer hook entries but retains user connection settings. Disconnect device power to stop physical operation.
FAQ
Which files does hook setup change?
It uses `.cursor/hooks.json` for Cursor, `.claude/settings.json` for Claude Code and `.agents/hooks.json` for Antigravity. Connection settings live separately in the user's Tiny Engineer directory. Setup does not write keys into a project's `.env`.
How can I check connectivity before building my own integration?
Run `npx -y tiny-engineer doctor`. An HTTP device also exposes `/health` to check firmware responsiveness without motion. Its screen can show the device address.
Can I use Codex?
Yes, by connecting Codex events to the HTTP API or serial protocol yourself. There is no built-in Codex hook setup; the wizard configures Cursor, Claude Code and Antigravity.
What audio does the robot play?
It expects 16-bit mono PCM WAV at 22,050 Hz. The `tiny-engineer-play` skill uses a local speech synthesizer and FFmpeg conversion. Normal animation hooks wait while a clip is playing.
What about the older editor-specific packages?
Use the shared `tiny-engineer` package. Earlier separate Cursor, Claude Code and Antigravity binaries are deprecated. Check hooks after migration to avoid sending duplicate events.
Which licenses apply?
Software uses MIT and hardware designs use CERN-OHL-S-2.0. The name and logo have separate restrictions.
Discussion
No questions or reviews yet.
Related
CLI toolsConnects Claude Code, Cursor, Codex or OpenCode to Telegram, Slack and Discord: teammates message a bot, an agent replies
A gateway for a desktop robot on M5Stack CoreS3: voice, a wake word and an MCP server through which an agent makes it speak
SwitchBot smart-home CLI for devices and scenes, with a built-in MCP server for Claude Code, Codex and Gemini CLI.
A plugin and CLI catalog for agents: generates command-line interfaces for GUI apps like GIMP and Blender and installs ready ones via CLI-Hub
A CLI that loops Claude Code, Codex, OpenCode and other agents over a task list or PRD until everything is done
quackd connects robots to Claude Code and Claude Desktop over MCP: nine tools and an executor with an allowlist
README in short
The hardware project includes body models and a controller-board design. Assembly guides explain component wiring and firmware installation.