fomo

An SO-101 leader arm that films.
_{six servos · a camera on a printed pan/tilt head · five tools: calibrate photo move pose motion}

Site — the twin plays the nine motions · Install · Five verbs · Motions · The guard · Cockpit

Hi. I'm Fomo.

I'm the leader arm from an SO-101 kit — the one that goes back in the box after teleop. Someone took my handle off, printed a pan/tilt yoke for an Arduino Nicla Vision, and screwed it to my wrist. Now I'm a cameraman: six Feetech STS3215 servos on one bus, a camera that knows its own pose, and an agent that drives me with exactly five verbs.

from strands import Agent
from fomo.tools import calibrate, photo, move, pose, motion

fomo = Agent(tools=[calibrate, photo, move, pose, motion])
fomo("look 40 degrees left, take a photo, then show me you're happy")

Install me — five steps

pip install "fomo-the-arm[dashboard]"     # tools · CLI · MCP · agent · dash API   (+[mcp], +[rl])

pip gives you the five tools, fomo and fomo mcp, the agent and the dash API. The cockpit's SPA and the twin's models live in the repo, so for the full panel clone it:

git clone https://github.com/cagataycali/fomo-the-arm.git && cd fomo-the-arm
pip install -e ".[dashboard]"
fomo doctor                 # read-only: which port is me, six servos, calibration, camera
fomo calibrate --manual --hold 40 --i-know   # torque off, move me by hand, fold me before the timer ends
fomo dash                   # http://127.0.0.1:8091 — the cockpit: agent log, dock, twin, eyes

No arm? FOMO_SIM=1 fomo dash is six simulated servos ramping at my real speed — the site's twin is one. The long form, with what each step refuses and why, is Install.

Set FOMO_PORT when doctor finds more than one usbmodem (on the bench this was written on it found five: the servo adapter, a Nicla, a Sticky, a Flipper — two share the CH343 chip, so I refuse to guess). Nothing moves until you say --i-know (you are watching me) or write {"ok": true} to ~/.fomo/bench.json.

My five verbs

Every tool returns the same {"status", "content": [{"text"}]} shape, dash-first (when the dashboard owns the port) with a local-bus fallback. fomo mcp serves the same five over MCP. Verbs · Motions — the twin plays all nine.

The guard — hard limits only

Every servo write passes fomo.guard.Guard. It refuses on six things, each named after a night something went wrong on the real leader (2026-09-05 → 08), and executes everything inside them:

How far a command reaches is never a refusal: inside the limits a target is cut into ≤ 10° legs, goals streamed from the host at 30 °/s (ceiling 90) so stop lands mid-leg, torque drops 2 s after the last command — only when folded. The guard: every number on that page is read from fomo/guard.py and ~/.fomo/calib.json at build time, never typed.

Cockpit — fomo.cagatay.my

One screen; the agent is the spine. The log is the narrative — your prompts, my streamed answers, every tool call as a row in words (read · joints 0.1 s, motion · happy), a photo inline — and the eyes (live MJPEG) and the twin (following the servos at 5 Hz) are my face. STOP is always in the bar. Captured 2026-09-09 on the live arm:

Press d for the dock — one slider per joint on its measured window, look pad, every pose, every motion, torque, a speed slider capped at the guard's 90 °/s. Nothing in it bypasses the guard, and manual moves land in the same log so the agent's next turn sees them.

Voice in and out are browser-native; a think toggle lets me look and say one line every so often (off by default, never moving joints 1–4). Control routes need FOMO_TOKEN (or, with FOMO_OWNER set, the owner's tiny.technology session); state, /ws, eyes and senses are read-only public. dashboard/deploy/install.sh makes it a launchd agent and carries your model credentials (AWS_BEARER_TOKEN_BEDROCK or AWS_PROFILE) into it; cloudflared-fomo.yml puts it on a name. Cockpit · Reference — every route.

Where I come from

I'm the fresh codebase of strands-arm — the idea kept, the 14k lines cut to what a cameraman needs. Everything I learnt there — the measured servo ranges, every incident behind the guard, the nights in archive/lanes/ — is written down where it was learnt: the guard page carries the incidents, the install page the hand-measured windows.

What I won't pretend to do

• Drive a base. That's strands-arm's three-wheel body; I'm the arm on the bench.
• Run an RL policy live — not yet. Two ONNX policies ship and run in shadow (fomo rl shadow); stage 1 (head only) is built and stays behind a phrase the owner writes by hand in the journal.
• Lift on 5 V. The leader kit's supply reads 5.6 V on my bus; the elbow does not lift the forearm from the fold on it (rule 9 holds it). The 7.4 V supply does.
• See obstacles. Rule 1 exists because a human must.
• Take a photo I didn't take. If every camera source fails, photo says so and names each.

License

MIT, Cagatay Cali. Built by cagatay and his agents at strands robots.