This setup is about ongoing development from the couch, not only from the workstation. By using remote surfaces and coding agents together, I can keep work moving through review, direction, and bounded execution without needing to sit directly in front of the main machine the whole time. The point is not constant autonomy. The point is persistent progress through connected tools, clear instructions, and remote access to the work.
I do not need to be physically at the main development machine to keep the process alive. Remote surfaces let me supervise, redirect, and continue work from a lighter environment.
Remote development only stays productive when the coding agents receive scoped tasks, enough access to act, and context that survives between sessions.
The couch is just the symbol. The real idea is reducing friction so the work can continue through more surfaces without collapsing into loose improvisation.
Remote surfaces let me stay connected to the work without being tied to the local workstation, which matters when development stretches beyond one sitting.
The coding agents can keep handling bounded tasks while I supervise direction, review what changed, and step in only where judgment is needed.
The workflow does not reset just because I changed locations. Remotes help preserve continuity while the agents continue operating inside a prepared environment.
Set up the task with enough notes, constraints, and references that the agent can continue without asking basic questions.
Use the remote surface to check progress, steer priorities, and respond without reopening the entire environment locally.
Allow the coding agents to perform bounded repo work while the human stays available for approvals and course correction.
Come back through logs, diffs, checkpoints, or tags so the work remains inspectable and reversible when needed.
Remote operation is not a reason to become vague. The agents still need narrow objectives, clear edges, and an explicit definition of what counts as done.
Instructions, notes, reference material, and environment assumptions need to survive across remote sessions or the couch workflow falls apart.
Remote agents still need enough permissions to do meaningful work, but the access should match the job and the available recovery path.