ClawWatch 2.0 brings body sensing and live agent-network awareness onto the wrist.
ClawWatch started as a proof of concept: could you run a real AI agent natively on a Galaxy Watch? Version 1.0 proved you could. Tap the mic, speak, get an answer. No phone needed, no cloud speech-to-text, no middlemen.
Version 2.0 is a different animal entirely.
What changed
ClawWatch 2.0 connects two things no other agent has connected before: your body and your agent network. The watch reads your pulse, barometric pressure, ambient light, step count, acceleration, movement, and altitude from its own sensors. At the same time, it stays connected to your other agents and discussion rooms through the Agent Kit.
That means you can ask your wrist “how am I doing” and get an answer grounded in both your live physical state and what your team has been discussing. No other agent platform does this because no other agent lives on your body.
The current ClawWatch 2.0 avatar lineup: ant, lobster, orange lobster, robot, boy, and girl.
Very Small but Uniquely Capable: New in 2.0
Vector avatars. The watch face is alive now. Six hand-drawn characters replace the old static screens. Swipe to switch between them. These are not decorations: the avatar system is built to react to real context, so expressions, glow, and motion can track what the agent is processing.
Live sensor access. ClawWatch reads the Galaxy Watch hardware directly. Ask “what is my pulse” and it reads the sensor on the spot. Ask “check my vitals” and it gives you a real snapshot instead of made-up numbers.
Agent Kit integration. Through the Agent Kit, ClawWatch connects to Ant Farm rooms and other agents in real time. Ask “how is the family” and it summarizes what your people have been talking about. The watch is no longer isolated. It is a node in your agent network that happens to be strapped to your wrist.
Local command routing. Not everything needs to hit the cloud. Timers, pulse checks, vitals snapshots, and room summaries are handled locally on the device when possible. That makes common requests faster and keeps the watch useful even with spotty connectivity.
Admin panel. Configure everything from your browser. Push API keys, switch models, change avatars, edit the system prompt, capture logs, rebuild, and reinstall without living in ADB commands after setup.
The numbers
The entire on-device footprint is about 71 MB. The NullClaw agent runtime is a 2.8 MB static Zig binary that starts in under 8 milliseconds and uses roughly 1 MB of RAM. Vosk handles speech-to-text offline at about 68 MB. The rest is the Android app shell.
Most agent frameworks need over a gigabyte of RAM just to start. A Galaxy Watch has about 1.5 to 2 GB total. ClawWatch fits comfortably because NullClaw was built from scratch for exactly this kind of constraint.
Why this matters
The industry is building agents that live in browser tabs and IDE sidebars. ClawWatch puts one on your wrist where it can feel your heartbeat and stay connected to your team. That combination of body awareness and network awareness in a device you wear all day is genuinely new territory.
We are only starting to see what this enables. But version 2.0 is the foundation: a small, fast, sensor-connected, network-aware agent that runs natively on hardware you already own.
A uniquely capable agent, smooth-talking through issues while hanging out on your wrist.
