Blog · October 18, 2026 · 8 min read · by Vilva Athiban P B

Sitting Too Long as a Developer: The Posture Problems Coding Agents Made Worse, What the Research Says About Breaking Up Sitting, and How NotchFit Turns an Agent Run Into the Break

Coding agents changed the shape of a developer's day in a way nobody planned for. You used to stand up when a build ran, when you walked over to ask someone a question, when a test suite took four minutes. Now Claude Code or Codex runs the build, answers the question and writes the tests, and you sit there supervising a stream of output, waiting to approve the next tool call. The gaps that used to get you out of the chair are still there; they just do not move you any more. This post is about what sitting through those gaps does to your back, neck and wrists, what the research says about breaking them up, and how to turn an agent run into the movement break it already wants to be.

What a long sit actually does

The problems most developers notice are mechanical and arrive in a familiar order. Hip flexors shorten from hours at ninety degrees and start pulling the pelvis forward, which the lower back pays for. Shoulders round towards the screen and the head creeps forward of the spine, a few centimetres that add kilograms of load on the neck muscles holding it up. Wrists rest on the desk edge at a slight bend for the whole day. None of this is dramatic on any single afternoon, which is exactly why it accumulates into the stiff mornings and the dull ache between the shoulder blades that most people eventually accept as part of the job.

The less visible effects are metabolic. A frequently cited trial by Dunstan and colleagues, published in Diabetes Care in 2012, had nineteen overweight adults sit for five hours after a test meal on three separate days: once without a break, and twice with a two-minute walk, light on one day and moderate on the other, every twenty minutes. The walking breaks lowered the glucose and insulin responses to the meal, and the light walks did about as well as the moderate ones. The World Health Organization's 2020 guidelines on physical activity and sedentary behaviour draw the general conclusion: adults should limit the time they spend sedentary, and replacing sedentary time with activity of any intensity, including light activity, has health benefits. The research on one-minute vigorous bouts, which NotchFit's sets resemble more closely, is covered in the exercise snacks post; the point here is simpler. The break does not have to be a workout. It has to happen.

Why developers do not take the break

Everyone knows they should stand up more. The reasons they do not are worth naming, because the fix has to address them rather than the knowledge gap.

  • There is no natural pause. With an agent, the work is continuous from your side even when you are doing nothing. There is no compile to wait for, so there is no moment that feels like permission to leave.
  • Leaving means missing the prompt. If you walk away and the agent asks for permission thirty seconds later, you lose the whole gap to a stalled run. So you stay and watch.
  • Timers are the wrong shape. A reminder every thirty minutes fires in the middle of a thought as often as not, and gets dismissed, and the habit of dismissing it is learned in a week.
  • Nobody knows what to do. “Stand up and stretch” is vague enough to skip. A specific movement, with a rep count, is not.

The agent run is the break you were missing

Here is the reframe that NotchFit is built around. A coding agent working on a task is the modern build. It takes somewhere between thirty seconds and several minutes, you cannot usefully type while it runs, and it ends with an event you need to know about: the agent is done, or it needs permission. That is a near-perfect shape for a movement break, provided two things are true. You have to be told what to do in the gap without deciding, and you have to be told when the gap ends without watching.

NotchFit does both from the MacBook notch. When Claude Code or Codex starts a task, the notch expands into a panel: a guided animated exercise on the left, drawn from 239 moves (198 photo animations of real athletes and around forty illustrated ones), and the agent's live progress on the right. You tap Start set when you are ready; nothing begins on its own. A rep or time countdown ring runs the set, with Done, Skip and Pause. And when the agent finishes or needs permission, NotchFit notifies you, with one rule that matters more than any other for a movement break: a notification that arrives mid-set waits until the set ends. The reason that matters is in why mid-set notifications wait; the short version is that a break you can be yanked out of is a break you will stop taking.

Which movements to put in the gaps

For sitting-related stiffness specifically, the exercises worth putting into a weekly plan are the ones that reverse the chair. A reasonable split across a day looks like this; pick the closest moves from NotchFit's library, and the gentler versions are in desk exercises for programmers.

  1. Hips and lower back: bodyweight squats, glute bridges, a standing hip-flexor stretch. These undo the ninety-degree hip and are the highest-value minute of the day for most people who sit.
  2. Upper back and shoulders: wall slides, band or towel pull-aparts, doorway chest stretches. Anything that pulls the shoulder blades back and down.
  3. Neck: slow chin tucks and gentle side bends. Small ranges, no forcing, never through pain.
  4. Wrists and forearms: wrist circles, prayer and reverse-prayer stretches, finger extensions. Thirty seconds between agent runs is enough.

The easiest way to get that mix without planning it is to let the agent write the plan. Run /notchfit:plan in Claude Code or $notchfit-plan in Codex; it asks about your age, height, weight, fitness level, goal, equipment, days per week, minutes per day and injuries, and writes a weekly plan using only exercises the notch can animate. Tell it your goal is posture and that you sit all day, and the plan skews towards the list above. There is also an offline quick-plan generator in the app if you would rather not involve the agent, and the plan post goes through what a good one looks like.

Fixing the chair as well

Movement breaks are not a substitute for a desk that fits you, and NotchFit would be the wrong tool if it let you avoid that conversation. The usual checklist still applies: screen top at or just below eye level so the head is not tilted; elbows at roughly ninety degrees with the keyboard low enough that the shoulders drop; feet flat; the chair supporting the lower back rather than the chair being leaned away from. If you work on a laptop, an external keyboard and a stand are the cheapest posture change available. If a standing desk is in reach, use it for part of the day rather than all of it; standing still for eight hours has its own problems, and the aim is variety, not a different fixed position.

And an honest caveat: NotchFit is a workout guide, not medical advice, and a set of squats between tool calls will not fix a back that already hurts. Persistent pain, numbness or tingling in the hands is a reason to see a physiotherapist or doctor, not to download an app.

Making it stick

The thing that turns a few good days into a habit is being able to see it. NotchFit keeps a streak and a history heatmap, and finishes a set or a workout with confetti in the notch, which is faintly ridiculous and works. The streaks post covers how to set a target you will actually hold. If you want the notch purely as an agent status panel on a day you cannot move, the Hide workout toggle does that without breaking anything.

NotchFit runs on macOS 14 or later, Apple Silicon or Intel, works best on MacBooks with a notch and shows a top-centre pill on Macs without one. It runs locally over localhost with no account, no telemetry and no microphone, integrates with Claude Code through a plugin and with Codex through skills and hooks that run asynchronously, and costs $20 once, sold on Whop as a signed and notarized DMG. None of that changes the physiology. Sitting still through every agent run is the default, and the default is bad for you. The run is the break. Take it.

Keep reading

Desk Exercises for Programmers: 15 Moves to Do While Your AI Agent Codes

7 min read

Exercise While Coding: Turn Claude Code Wait Time Into Micro-Workouts

7 min read

Claude Code Notch Notifications on Mac: See When Claude Is Done Without Watching the Terminal

7 min read

Claude Code Tips and Tricks: 12 Ways to Use Claude Code Effectively

8 min read

Claude Code Multiple Sessions: How to Run Agents in Parallel Without Losing Track

6 min read

A Claude Code Workflow That Doesn't Involve Watching the Terminal

5 min read

Claude Code Hooks: A Practical Guide to Automating Your Agent Workflow

7 min read

Claude Code Auto Mode: Fewer Permission Prompts Without Living Dangerously

7 min read

Claude Code Subagents: How to Delegate Work to Specialized Agents

7 min read

Claude Code Context Management: Treat the Context Window Like a Budget

6 min read

Per-Subagent Model Selection: Route the Grunt Work Down, Keep the Judgment Up Top

7 min read

Skills and Plugins: How to Teach Claude Code Your Way of Working

7 min read

Claude Code Background Tasks: Run Long Commands Without Blocking Your Session

6 min read

Codex CLI Notifications: How to Get a Ding When Codex Is Done or Needs Input

7 min read

Cursor Notification When Done: Every Way to Get Notified When Cursor Finishes

6 min read

Claude Code Notifications: How to Get Notified When Claude Code Finishes or Needs Your Input

6 min read

Want to Be Notified When Claude Responds? How Claude Notifications Work on Web, Desktop, and Mobile

5 min read

Claude Code Notification Scripts: Copy-Paste Recipes for Every Platform

6 min read

Get a Ding the Moment Codex Needs Your Response

6 min read

Get Notified the Moment Claude Code Is Waiting for Your Input

6 min read

“Notifications Are Turned Off for Claude” — Here Is the Fix

6 min read

Codex Sound When Done: Make Codex CLI Play a Sound When It Finishes

6 min read

terminal-notifier + Claude Code: Native macOS Alerts When Your Agent Finishes

6 min read

Gemini CLI Notifications: How to Get a Sound or Alert When Gemini Finishes

6 min read

Get Claude Code Notifications on Your Phone

6 min read

Claude Code Remote Control, Explained

7 min read

preferredNotifChannel: Claude Code's Built-In Notification Setting

6 min read

Claude Code Notifications in tmux and Over SSH

7 min read

Claude Code Effort Levels: Why Your Setting Keeps Getting Ignored

8 min read

Codex vs Claude Code Notifications: How Each One Tells You It Is Done

8 min read

Claude Code Notifications Not Working: A Diagnostic Checklist

10 min read

Claude Code Notifications Inside Your Editor's Terminal

7 min read

CLAUDE_CODE_DISABLE_BACKGROUND_TASKS Explained

7 min read

CLAUDE_CODE_DISABLE_BG_SHELL_PRESSURE_REAP Explained

8 min read

Cursor Alerts Explained: Every Alert Cursor Raises, and How to Control Them

7 min read

Claude Code Environment Variables: The Groups That Actually Matter

10 min read

Claude Code Notifications on WSL and Windows

9 min read

Claude Code Checkpoints and /rewind

8 min read

Claude Remote Control: How It Works, Turning It Off, and Auto Mode

7 min read

Claude Code /loop: Poll a Deploy, Babysit a PR, and Get Told When It's Done

8 min read

Setting Up NotchFit With OpenAI Codex CLI: Hooks, $notchfit-plan, and the Daily Flow

7 min read

Claude Mods Explained: What the New Plugin Layer Can Do, and How to Turn On 'You Should Know'

9 min read

NotchFit vs Mac Break Reminder Apps: A Clock or a Signal From Your Coding Agent?

8 min read

Claude Code Headless Mode: Running claude -p in Scripts and CI, and the Three Signals That It Finished

10 min read

Building a Movement Habit at a Desk: Use the Agent Run as the Cue, One Set as the Unit, and Streaks Carefully

8 min read

Claude Code MCP Servers Explained: Adding Servers, Choosing a Scope, Handling Secrets, and Why Long Tool Calls Go to the Background

10 min read

/notchfit:plan Explained: How Claude Code or Codex Writes a Weekly Workout Plan the Notch Can Actually Run

8 min read

Claude Code Spinner Verbs Explained: What “Pondering” and “Brewing” Mean, How to Change Them, and Why You Should Stop Watching the Spinner

7 min read

Why NotchFit's Done and Permission Alerts Wait Until Your Set Ends, When That Costs You, and How to Turn the Workout Off

7 min read

How to Resume a Claude Code Session: --continue vs --resume, Naming Sessions, the Session Picker, Branching, and What Comes Back

9 min read

NotchFit on a Mac Without a Notch: How Pill Mode Works on Mac mini, iMac, Mac Studio and a MacBook With the Lid Closed

6 min read

How to Run a Claude Code Session in the Background: /background, claude --bg, Agent View, and Getting Back to It

9 min read

What a Notch App Can See: NotchFit's Local-First Design, What the Claude Code and Codex Hooks Send, and What Stays on Your Mac

7 min read

Why Codex CLI Asks for Permission Every Time, and How to Tune the Sandbox and Approval Policy Without Going Full Access

8 min read

What to Do While Claude Code or Codex Works: A Simple Protocol for the Two-to-Twenty-Minute Gap in Every Agent Run

7 min read

Is It Possible to Get a Notification When Claude Code or Codex Hits a Reset? Yes for Claude Code: the quota_auto_resume Hooks, Explained

8 min read

What a MacBook Notch App Can Actually Do: The Five Kinds of Notch Utility, Their Trade-offs, and Where NotchFit Fits

7 min read

How to Make MCP Servers Not Take Up as Much Context in Claude Code: Tool Search, alwaysLoad, Scopes and Output Caps

8 min read

The notchfit Command Line: Drive Your Workout, Read Status as JSON, Validate Plans and Test the Notch Without Leaving the Terminal

7 min read

How to Audit MCP Tool Calls Made by Claude Code: A Five-Minute Hook Audit Log, OpenTelemetry Tool Events, and the Transcript for Investigations

9 min read

Exercise Snacks: What the Research Actually Says About One-Minute Vigorous Breaks, What It Does Not, and How NotchFit's Agent-Run Sets Compare

8 min read

How Long Until a Claude Code MCP Tool Call Times Out? The Four Timers (Startup, Two-Minute Backgrounding, Idle, Wall-Clock), Their Defaults, and Which One to Change

8 min read