Note
June 5, 2026
2 min read
When Closing the Laptop Stops the Agent
By Cristiano Pierry
Agentic coding needs persistent workspaces that can pause, resume, and carry context beyond the laptop that started the work.
I had to fly to Brazil unexpectedly this week and ran into a new workflow problem.
I was working with OpenAI Codex across three projects. None was complete. Code paths were being explored, changes tested, and ideas refined.
Then I had to catch a flight.
Before unplugging, I did something that felt oddly new. I gave the LLMs a heads up.
I told them, essentially: I’m going to disconnect. Find a good place to stop. Record the session. Capture the state of the work, the decisions made, open questions, files touched, next steps, and anything else we need to resume later.
Then I closed my laptop.
Everything effectively stopped.
For many of us, the laptop is the default development environment. The code, dependencies, tools, terminal history, and fragile intermediate state all accumulate there. That arrangement becomes a constraint when an agent is expected to make progress over a longer period or across several projects.
The laptop is a great interface. It is a poor place to anchor long-running, agentic work.
The development environment needs to persist when the laptop disconnects. It should preserve branches, dependencies, logs, tests, prompts, notes, and intermediate decisions. It should also make pausing and resuming explicit.
The agent needs to know where it stopped. I need to be able to inspect that state. The system should reconstruct the work without depending on my memory, a terminal buffer, or a hurried note written before boarding.
Cloud desktops, remote development containers, virtual machines, or purpose-built agent workspaces could all contribute to the answer. The product requirement is more important than the specific implementation: work should survive the interface that started it, and both the human and agent should be able to resume from a trustworthy record.
As coding tools become agents that can work while we are away, closing a laptop should pause access when necessary. It should not erase the working state.
This writing reflects my personal perspectives on product management, AI, and content discovery. It does not represent the official position of my employer or any affiliated organization.