ClawdBod is a free Claude Code plugin that slips short fitness breaks into your coding
sessions, so you ship features instead of turning into a mass of prompt-shaped jelly. It
bundles 54+ exercises across strength, mobility, and cardio, tracks your reps locally on
your own machine, estimates calories burned, and lets you export your history to CSV or
JSON. Break timing is tracked per session, so parallel terminals never steal each other's
breaks. Everything runs local-first — no account, no cloud, no leaderboard.
Install from the Claude Code plugin marketplace with
/plugin install clawdbod --marketplace khur/clawdbod then /reload-plugins.
Exercises
54 exercises in six categories: upper body (push-ups, tricep dips), lower body (squats,
lunges, wall sits), core (planks, mountain climbers), cardio (jumping jacks, burpees),
mobility (neck rolls, cat-cow), and desk-friendly moves (seated twists, chair squats).
FAQ
Does it interrupt my flow?
Only when your spine is about to. Breaks need a configurable number of prompts AND a minimum time gap (8 prompts and 20 minutes by default), counted per session. No permission prompts mid-break. You control both numbers.
What if I skip a break?
Nothing happens. ClawdBod suggests, it doesn't enforce. But your future self will judge you.
What does the plugin actually run on my machine?
Two small hooks and a handful of slash commands. A Stop hook decides when a break is due; a PreToolUse hook auto-approves only ClawdBod's own scripts (never anything else, and never the export, which still asks). It reads and writes JSON files under ~/.claude/clawdbod and makes no network requests. The source is on GitHub, so you can read every line before installing.
Are the calorie estimates accurate?
They use MET-based calculations with your height, weight, and age. Ballpark accurate -- not medical-grade, but way better than zero.
Can my team see my data?
No. Every rep is logged to a local file on your machine -- nothing is uploaded anywhere. Want it out? /clawdbod:export gives you CSV or JSON.
I run four terminals at once. Do they fight over breaks?
No. Break timing is tracked per Claude Code session, so each terminal counts its own prompts and subagents never burn your counter. Pause and resume still apply everywhere at once.
What about long builds and deploys?
Claude is told to skip a break when you're mid-deploy or deep in a hairy bug. For a long focus block, /clawdbod:pause 2h mutes breaks everywhere. If you'd rather use the wait, /clawdbod:fitness hiit 5 gives you a timed workout on demand.
Does it work with vim keybindings?
ClawdBod is a Claude Code plugin. It doesn't care about your editor. It cares about your body.
What if I switch machines?
Your data lives in ~/.claude/clawdbod -- copy that folder over and your history and settings come with you. Or run /clawdbod:export json first for a portable backup.
Does this website track me?
This site uses Google Analytics for basic visit counts. The plugin itself has no analytics or telemetry -- that's a promise about the plugin, which is the thing you install.
Is it really free?
MIT licensed. Free forever. The only cost is 15 push-ups.