Claude Code started running tasks on the web in October 2025. The browser mattered more to me than another editor integration because it turned coding into delegated work: connect GitHub, hand off a task, and come back to the result.
Three Interfaces, Different Tradeoffs
Web ran tasks on Anthropic’s cloud and let me start several independently. I could check progress, steer a task, and resume it later.
CLI runs locally with direct filesystem access and is single-threaded. You control the environment, but pay-as-you-go pricing stacks up when you’re hammering it.
iOS is for monitoring and light tasks: checking progress, providing feedback, triggering simple refactors. Anthropic admits it needs refinement.
All three connect to GitHub the same way. Install the GitHub app, authorize access (contents, issues, PRs), add the Claude Dispatch workflow. Claude gets sandboxed with network and filesystem restrictions. A secure proxy handles git operations — it can’t touch repos you didn’t authorize.
The Maintenance Machine
Refactoring, test generation, dependency upgrades, and bug fixing are not glamorous, but that is what fills sprints. React project needs upgrading? Claude analyzes the codebase, identifies breaking changes, runs migrations across files.
Type annotations on JavaScript files. Unit tests for new functions. Database migrations from schema changes. The time savings pile up on repetitive work that eats days, not on architectural decisions.
The web interface shifts the psychology. You’re delegating, not augmenting your editor. That changes how you scope the work.
A Browser Tab Lowers the Commitment
Claude Code used to live inside Cursor or a VS Code plugin. You had to seek it out.
In the browser, I could try one delegated task without moving my editor setup. That smaller commitment was the product change I cared about.
One quick signal
Did this earn your time?
Thanks. That gives me something concrete to check.


