Is it actually a problem that your AI agent stops running when you close your laptop?
by•
I’ve noticed that many coding-agent workflows still depend on keeping a laptop awake and connected.
I’m curious how people here handle longer tasks:
Do you leave your computer running, use a remote machine, or rely on a cloud environment?
I’m also interested in collaboration. When several people are working on the same project with different agents, how do you avoid conflicts and keep visibility into what each agent is doing?
Is this a recurring problem in your workflow, or something you rarely think about?
35 views
Replies
i leave my laptop running more ofteb than i want to. it works but it feels like a temporay solution.
Murmell
@george_rosevear yes but how do you deal with travelling, meetings etc ?
i started a remote machine for longer tasks. it gives me pecae of mind when i need to step away.
Murmell
@akhilesh35602 hmm how do you handle security of this ?
for shorts task. i don't think about it much. for anything that takes more than 20-30 mintues it becomes annoying.
Murmell
@_harper_nicole yes but for things like live claude sessions watching production etc
It's definitely a real pain point once agent tasks take more than 2-3 minutes. Leaving a laptop awake with the battery draining—or waking up to a killed process because macOS went to sleep—is super frustrating.
For long-running agent tasks, offloading execution to cloud sandboxes or a cheap headless VPS is pretty much required. As for team collaboration, treating agents like human devs where each agent works on its own isolated Git branch is the only way to avoid merge conflicts.