There is a quiet shift happening in how engineers work. The laptop is no longer the only device that can ship production code. Codeforless's pay-per-session AI Coding sandbox runs entirely in a browser — and that means it runs on a phone, on a tablet, on a locked-down work-issued Chromebook, on whatever device an engineer happens to have in front of them. No setup. No commitment. Open a tab, code, ship.
This post is about what that actually unlocks, and why "code from anywhere" stops being a marketing slogan and starts being a real workflow once the friction of a local dev environment is gone.
The premise
A Codeforless session is a full Linux dev container. VS Code in the browser, a real terminal, a real filesystem, Node and Python and Docker and git already installed, an AI Coding agent (Claude Code) wired in. The only thing the engineer needs on their device is a browser.
The implication people miss the first time they hear about it: every modern phone has a perfectly functional browser. So does every tablet. So does every iPad. So does the Chromebook the engineer's company won't let them install anything on. So does the spare Windows laptop they keep at their parents' place.
A workflow that lives entirely in the browser is a workflow that lives anywhere the engineer is.
Real workflows that get unlocked
Five concrete situations where the "browser is enough" model changes what the engineer can do.
1. The airport / train / commute scenario
The engineer is travelling. The laptop is in checked baggage, or low on battery, or just heavy. The phone is in their hand. A Codeforless session opens in mobile Safari or Chrome. Claude Code drives the heavy lifting; the engineer reads the diff, says yes or no, asks for changes. Code is committed and pushed to the engineer's git remote before the boarding announcement.
This is not about typing a thousand lines on a phone. It is about being able to direct an AI Coding agent and review its work from a phone. Codeforless customers do this constantly during transit. The session is doing the typing.
2. The on-call without a laptop
Saturday night. The pager goes off. The engineer is at dinner, no laptop, just a phone. Open Codeforless on the phone. The AI Coding agent has tools, it can poke at logs and propose fixes; the engineer reviews and approves. The fix ships. The engineer goes back to dinner.
A laptop-only on-call rotation is a worse on-call rotation. Browser-based AI Coding shrinks the surface area of "I need to be home in front of my dev machine to be useful."
3. The locked-down work environment
Some engineers — contractors, employees of regulated industries, anyone whose company has strict device-management policies — cannot install development tools on their work laptop. They cannot run Docker. They cannot install a code editor that isn't approved. They certainly cannot install Claude Code locally.
A Codeforless session bypasses all of that. The work laptop's browser is the dev environment. Side projects, learning, experiments, freelance work — all live in a sandbox the company's MDM policy doesn't reach.
4. The "I'm in bed" weekend project
Weekend coding used to mean getting up, sitting at a desk, opening a laptop, and committing to a stretch of time. With a phone or tablet on the couch, the engineer can poke at a side project for fifteen minutes between innings of a baseball game. The AI Coding agent picks up where the previous session left off (the engineer's git repo persists; only the sandbox is ephemeral). The micro-sessions add up. Side projects ship that wouldn't have otherwise.
5. The borrowed-device scenario
The engineer's laptop dies on a Tuesday morning. They are at a co-working space. They borrow a teammate's spare Chromebook for the day. Two minutes later they're back at full productivity in a Codeforless session — same dev environment, same AI Coding agent, same git remote. The laptop replacement is a Friday-afternoon problem now, not a today problem.
What "no commitment" actually buys
Beyond the device flexibility, the no-commitment shape of pay-per-session is what makes "code from anywhere" tactical rather than aspirational.
If the engineer had to subscribe to a tool to use it from their phone, they wouldn't bother — the friction of "is this worth a recurring bill" stops the workflow before it starts. Pay-per-session takes that friction away. Booking one $4 Evening Owl session to fix one bug from a hotel room is not a financial decision the engineer has to commit to a relationship with. It is just a thing they did once.
The compounding effect of low-commitment pricing on a portable workflow is real. Codeforless customers report behaviours they never had with their laptop-only setup: a session booked specifically to triage a Slack thread, a session booked from a kitchen table to help a friend debug, a session booked from a phone at a conference to push a quick fix between talks.
What it isn't
Honest constraints. A phone is still a phone. The engineer is not going to build a Kubernetes operator on a 6-inch screen. They are also not going to do precision merge-conflict resolution with their thumbs. The sweet spot for phone-driven Codeforless work is directing an AI Coding agent and reviewing its output, not raw text editing.
The tablet experience is significantly better — an iPad with a keyboard is a credible portable dev workstation when the dev environment lives in the browser. The phone experience is read-and-direct, not type-everything.
The bottom line
A browser-based AI Coding sandbox + pay-per-session pricing is a different shape of dev tool than the industry has had before. It is not "use your phone instead of a laptop." It is "the laptop is no longer the gating constraint on when and where the engineer ships code."
The engineer who has internalised this stops thinking of dev environment setup as a thing. They open a browser. They book a session. They ship.
Codeforless sessions start at $0.38 per hour for a 1-hour Dracula block. The phone or tablet you're reading this on is enough to start one.