Working on Vacation With AI Agents (Without Your Family Noticing)

Every August, freelancers and small agencies face the same bad choice.

Close the shop for three weeks and come back to a cold pipeline, a stalled project and a client who quietly found someone else. Or bring the laptop, and become the person who opens it at the beach club while everyone else is in the water.

Both options cost something. The first costs money and momentum. The second costs the vacation itself, and it is the one that gets negotiated at dinner.

There is now a third option, and it is not a productivity trick. Execution no longer needs you in the room.

What eats your vacation is presence, not work

The part of your day that genuinely requires you is smaller than it looks. Deciding what gets built. Deciding whether what was built is correct. Answering the one question nobody else can answer.

Everything between those points is execution, and execution is exactly what a coding agent does unsupervised: reading the codebase, writing the change, running the tests, fixing what fails.

Add up the decisions on a normal project week and they fit in twenty to forty minutes a day. The rest is presence. Presence is what your family sees, and presence is what you are actually trying to protect in August.

So the goal is not to work less on vacation. The goal is to keep the twenty minutes and delete the presence.

Fill the queue before you leave

The setup happens in the two weeks before departure, when you still have full context.

Every time you think "I should do X", it becomes a ticket instead of a mental note: a title, two lines of context, the files involved, and the agent role that should take it. A Frontend Developer for the component, a Security Engineer for the auth cleanup, a Technical Writer for the docs nobody has updated since March.

That queue is not a to-do list you will read on the beach. It is a set of pre-loaded orders. On the backlog task board, dragging a card from TODO to In Progress spawns an agent on that task, with the role you chose and the description as its brief. No terminal to open, no prompt to write, no context to reconstruct three weeks later with sand in your keyboard.

Which means the operation you actually perform on vacation is: drag one card. Ten seconds. Then you put the phone down and go swimming.

Ten minutes with a coffee, then the day is yours

The ritual is the whole point, and it happens before anyone else is awake.

You read what finished overnight. Each task card shows the status of its agent, so you know what is done, what is still running and what is stuck without opening a single terminal. You answer the one or two agents that are blocked on a decision, which is usually a sentence: yes migrate the column, no keep the old endpoint, ship it behind a flag.

Then you start one or two new cards, and you are done. The phone goes back in the bag. Nobody at the table noticed anything, because there was nothing to notice.

This is the part people underestimate. Working from vacation is not miserable because of the work. It is miserable because of the posture: the laptop open on a table, the half-attention, the "give me five minutes" that turns into an hour. Ten minutes on a phone at 7am is a different activity entirely.

If you want the mechanics of driving agents from a phone rather than the vacation version of it, we covered that separately in driving your coding agents from your phone.

The work that does not need you at all

Some of what happens during your absence should not involve you even for ten seconds.

Scheduled tasks turn recurring work into standing orders that fire on their own: review the pull requests that landed overnight, scan production logs every morning, check whether a dependency shipped a security patch, write a progress summary every Friday. You set them up once, before leaving, and they run on their schedule with their own role and prompt.

For the vacation case the value is not automation for its own sake. It is that your absence stops being visible from the outside. A client who receives a Friday summary during your two weeks off does not experience an absence at all, and that single habit protects more revenue than any amount of laptop time at the beach club.

The same logic applies to the hours you are asleep. Agents that run overnight are the night shift version of the same idea, and on vacation the night shift and the beach shift are the same shift.

Being reachable without being available

The failure mode of working from vacation is a phone that buzzes at random and pulls you out of the moment eleven times a day.

The fix is to make the flow pull, not push. Configure notifications so only two events reach you: an agent blocked on a decision, and something a client flagged as urgent. Everything else waits for the morning pass. An agent that finished a task successfully does not need to interrupt your lunch to tell you so.

Done properly, your phone is quiet for six days and rings twice. That is the difference between being reachable and being available, and it is the whole negotiation you are having with the people you are on holiday with.

For agencies: the August rotation that is not one

Agencies have a harder version of this problem. Five client projects, staggered holidays, one person on duty, and that person spends the month doing nothing but context switching between codebases they did not touch last week.

The shift is that the person on duty stops executing and starts triaging. Each project keeps its own queue, its own agents and its own history, so several projects can run side by side without merging into one mental soup. A client reports a bug on Tuesday: the ticket goes into that project's board, the right agent role picks it up, and the person on duty reviews a prepared diff instead of reconstructing an unfamiliar codebase from scratch.

And because the whole cockpit is reachable from a phone, the duty rotation stops meaning "stay near a laptop". It means "be able to read a diff and answer a question", which is a thing you can do from a train.

What you should not do from a beach

This is where honest advice matters more than the pitch, because the failure cases are predictable.

No production deploy you cannot roll back from a phone. If reverting requires SSH, a migration and a clear head, it waits.

No merge on the sensitive surfaces. Authentication, payments, permissions, personal data, database migrations, deletion paths. Those need a real review on a real screen, whatever the agent claims about its own work. We wrote about how much review a change actually deserves and none of it gets easier in flip-flops.

No new architecture. Vacation is for the queue you already understood before you left. Anything requiring you to hold a new mental model is exactly the thing you came here to stop doing.

No unbounded pile-up. Twenty unreviewed branches waiting for you is not two weeks of progress, it is a debt with your name on it and a very unpleasant first Monday back.

The rule of thumb: work started on vacation should be easy to reject. Small, independent, reversible tasks. A branch you drop costs nothing. A half-understood change merged from a phone costs your entire first week back.

A setup that actually holds for two weeks

The point is not to work more

Everything above can be twisted into "now you can work on vacation too", which would be a bad outcome and a worse product.

The actual point is different. Before agents, staying in the game during August meant being present: hours at a keyboard, visibly, while other people waited for you. Now the same continuity costs ten minutes and no visible absence from the table. The choice between three lost weeks and a ruined vacation was a false one, and it was never about how hard freelancers work.

Use the time you get back. The queue does not care what you do with it.

AgentsRoom is the command center this setup runs on: a backlog board where dragging a card starts an agent, recurring scheduled runs, live status on every agent across every project, and a mobile app that gives you the same cockpit from anywhere. It works with Claude Code, Codex and the other CLI agents you already use.

Download AgentsRoom before you pack.

Frequently asked questions

Can AI coding agents really keep a project moving while I am on vacation?

For execution work that was already scoped, yes. An agent reads the codebase, writes the change, runs the tests and fixes what fails without supervision. What it cannot do is decide what should be built, or accept its own work on anything risky. The realistic model is not zero involvement, it is ten to twenty minutes a day of decisions instead of six hours of presence.

How much time does this actually take per day on vacation?

Ten to twenty minutes, if the queue was written before you left. The morning pass is: read what finished, answer the one or two agents blocked on a question, start one or two new tasks. The thing that eats a vacation is not the decisions, it is sitting at a desk waiting for execution to happen.

What should you never let an agent ship while you are away?

Anything expensive to undo from a phone. Production deploys without a rollback, and merges touching authentication, payments, permissions, personal data or database migrations. Those need a real review on a real screen. Vacation work should produce branches that are cheap to reject, not changes that are hard to reverse.

How do freelancers avoid losing clients during the summer without working through it?

By making the absence invisible rather than by being available. A recurring agent run that sends a Friday progress summary, plus a queue that keeps producing reviewable work, means the client experiences continuity. What damages a freelance relationship in August is silence, not the fact that you are away.

Is it safe to run coding agents unattended for two weeks?

It is safe if the tasks are small, independent and reversible, and if nothing merges automatically. Isolate each task so agents cannot overwrite each other, cap how much unreviewed work can pile up, and treat every result as a proposal waiting for a human. The risk is never the agent running, it is the unreviewed diff that gets merged in a hurry.