Back to Syllabi
AIWork-Life BalanceWeek 2 Corporate Experiences

OOO: The Next Casualty of AI

8 min read

Get posts like this in your inbox weekly

Subscribe Free

I'm on vacation this week.

I should be completely unplugged. Instead, I'm scrolling X between pool time and putting my daughter to bed, watching announcements roll in about autonomous agent loops, lifecycle hooks, and background task orchestration. Nobody asked me to pay attention. I'm not managing any of this right now. But I can't stop thinking: is this the last vacation where being "off" even feels like an option?

That thought is what this article is about.

Remember Snow Days?

Growing up, there was no better feeling than waking up, looking out the window, and seeing everything covered in white. You'd flip on the TV or huddle around the radio waiting for your school's name to scroll across the screen. And when it hit? Pure magic. The entire day opened up. No schedule. No obligations. Just you, a sled, and the kind of unstructured freedom that only exists when the world collectively decides to stop for a day.

Snow days weren't just days off. They were proof that sometimes, everything could pause.

COVID took that from us. Not the snow -- the pause. Once companies figured out Zoom and Slack and VPNs, the concept of "we can't work today" evaporated. If you could work from your kitchen table during a pandemic, you could work from it during a nor'easter. The technology that gave us flexibility also gave our employers permanence. The snow still fell. The day off didn't.

That was the first domino. Sitting here on vacation, watching agent tooling evolve in real time, I think PTO might be the next one to fall.

The New Infrastructure of Always-On

Over the last few months, the tooling around AI agents has quietly crossed a threshold. Claude Code now ships with a /loop command that runs autonomous agent loops for hours. Hooks fire callbacks at every stage of an agent's lifecycle, from session start to task completion. Background agents monitor logs and errors while you work on something else. There's even a hook event called TeammateIdle that fires when an agent runs out of work, so tasks can be redistributed automatically.

Read that last one again. The system has a built-in assumption that idle time should be detected and eliminated.

This isn't just developer tooling. It's a philosophy. And it maps directly onto how leaner organizations are thinking about headcount. If your team went from twelve to eight over the last two years, and the remaining eight are now expected to supervise agents that run around the clock, someone needs to be paying attention when those agents finish, fail, or drift. The question isn't whether the agents are capable. It's who's watching them at 9pm on a Tuesday. Or checking their output from a hotel room.

The Research Says This Is Already Happening

A UC Berkeley study published in Harvard Business Review earlier this year tracked what happened when a 200-person tech company genuinely embraced AI tools. Nobody was forced. Nobody had new targets. People just started doing more because the tools made more feel possible. Work bled into lunch breaks and late evenings. To-do lists expanded to fill every hour AI freed up, and then kept going. The researchers called it "workload creep."

One engineer in the study summed it up: you thought being more productive with AI meant you could work less. But you don't work less. You work the same amount or more.

A separate BCG study from March 2026, also in HBR, found that supervising multiple AI agents created what participants described as a cognitive "buzzing" -- a fog that left workers exhausted and struggling to concentrate. The researchers named it "AI brain fry": mental fatigue from overseeing AI tools beyond your cognitive capacity. As CNN reported, the exhaustion wasn't coming from the work itself. It was coming from managing the work. One AI company CEO described ending each day drained from juggling open worktrees and half-finished features, not from building anything, but from trying to keep track of everything that was building itself.

Meanwhile, DHR Global's 2026 Workforce Trends Report surveyed 1,500 professionals and found employee engagement dropped from 88% to 64% in a single year. 83% report some degree of burnout. And 52% say that burnout is dragging down their engagement, up from 34% the year prior. The top two drivers? Overwhelming workloads and too many hours. Not layoff anxiety. Not return-to-office mandates. Just too much work and not enough time to recover from it.

Same Hours, Fewer Humans

Here's what nobody in a keynote is going to tell you: the pitch for AI at work was never "you'll work less." It was "we'll need fewer of you." Leaner teams don't mean lighter workloads. They mean the same surface area covered by fewer people, with agents picking up the tasks that used to belong to the colleagues who aren't there anymore.

And those agents don't take PTO. They don't have school pickup. They don't get sick. Which sounds great until you realize that someone still has to review what they produced, course-correct when they drift, and make the judgment calls they can't. That someone is you. And the agents don't stop running because you set an out-of-office reply.

The pattern from snow days is repeating. The technology that was supposed to give you flexibility became the reason flexibility disappeared. Remote work meant you could work from anywhere, which became you should work from everywhere. AI agents can handle tasks while you're away, which is becoming you should be available to supervise them while you're away.

Here's the uncomfortable truth though: unplugging completely isn't a viable strategy either. The person on your team who understands how these agents work, who knows what hooks and loops and background tasks actually do, who can set guardrails before they leave rather than firefight when they get back -- that person is more valuable. And if that person isn't you, someone else is building that case while you're offline.

This isn't about working on vacation. It's about what you do on the other 48 weeks.

Defend Your Territory Without Losing Your Mind

The Berkeley researchers recommended that companies develop what they called an "AI practice" -- intentional norms around when and how AI gets used. That's the organizational answer. But you can't wait for your company to figure that out. Here's the individual one.

Learn the infrastructure now so it doesn't own you later. Understanding how agent loops, hooks, and background tasks work isn't optional anymore. It's the same as learning Slack or Zoom in 2020. You didn't have a choice then. You don't have one now. But the person who understood Zoom on day one ran the meeting. The person who didn't sat on mute with their camera off. The equivalent today is knowing how to set an agent up with proper guardrails before you walk away, versus coming back to a mess you have to untangle.

Your domain knowledge is still your edge, but it has an expiration date. Right now, agents can execute tasks but they can't tell you which tasks matter. They can write code but they can't tell you whether the business logic behind it is correct. They can monitor systems but they can't tell you what a metric shift actually means for your customers. That judgment comes from years of knowing your field, understanding the context around a problem, and recognizing when something technically works but strategically misses. That's still yours. But the gap between what agents can do and what only you can do is closing. The time to leverage that advantage is now, while it still compounds. Wait too long and the person who paired their domain expertise with agent fluency will have already made your experience redundant.

Protect your time by being indispensable on your terms. The person who understands how to deploy agents effectively, set boundaries on what they can and can't do, and review their output efficiently doesn't need to be on call 24/7. They need to be excellent for the hours they're on. That's a different kind of value. And it's the kind that earns you the vacation where your phone stays in the bag.

The answer isn't to unplug and hope nobody notices. It's to plug in deliberately enough that unplugging becomes something you've earned, not something you're gambling on.

I'm on vacation this week. I'm not managing agents from a lounge chair. But I am paying attention to where this is all going, because the cost of ignoring it is higher than the cost of staying curious. The goal isn't to work on every vacation. It's to make sure there's always a next one.

Justin Grosz

Justin Grosz

Product Leader | Adjunct Professor, Northeastern