Ball says remote coding is solved because you are not coding
Responding to a podcast debate with Armin Ronacher and Ben Vinegar, Thorsten Ball argues agents removed the editor-shaped reasons to stay local.
Thorsten Ball says the problems of remote coding are solved, and his reason is that you are not the one typing anymore. He was responding to episode 12 of Ben Vinegar's State of Agentic Coding podcast with Armin Ronacher, which asked whether local desktop software is dead and debated Ball's own write-up on how he works with agents.
For one, you're no longer coding :) No need anymore to get LSPs or other editor-centric tooling running. Or an editor!
put your code on a remote box, headless, ask an agent to run through it end to end
Ball's argument is narrow and worth separating from the usual remote dev pitch. The old blocker was tooling that assumed a human at a keyboard. Getting LSPs working over a remote box, getting an editor to behave, all of that was, in his words, a huge pain in the ass. With an agent doing the editing, none of it has to exist.
What he says he actually runs
The second half of the reply is a direct factual disagreement. Ball questions the claim that you cannot run Postgres or MySQL inside Claude Code and Cursor, and says his team runs multiple dev servers and services, Postgres, Redis and Docker inside orbs. He also says the parts of remote environment setup that used to hurt, configuring services, making headless browsers work, making headless anything work, are now easy because the agent does the configuring.
His closing suggestion is a test rather than a position. Put your code on a remote box, headless, and ask an agent to run through it end to end. He adds that it sounds like Armin and Ben have not tried it.
For working engineers
This is one practitioner's report, not a benchmark, and the people on the other side of it are experienced engineers who reached a different conclusion on the same question. The useful distinction is that Ball is not claiming remote development got nicer. He is claiming the specific friction people stayed local to avoid was editor friction, and that an agent workflow deletes the category rather than improving it. If your reasons for staying on a laptop are editor-shaped, that claim is testable in an afternoon. If they are something else, latency, data, a GPU, a policy, Ball's argument does not touch them.
Ball has been making adjacent arguments for a while, including that teams should push straight to main and let agents handle the chores. The remote claim follows the same logic. Workflow conventions built around a human editing files stop paying rent once a human is not editing files.
Have the good opinion, not the loud one
One email a day. Under three minutes. What working engineers found out about coding with AI.