A cloud development environment in your pocket

Treena launches a cloud development environment that pairs a thin mobile client with a dedicated cloud machine, enabling full software work from a phone. The workspace holds the repo, terminal, and AI agents (Claude Code, Codex, Grok), while the phone only sends intent and renders results. The model leverages agents that make work steerable via phone-sized interactions and a persistent cloud workspace that runs tasks even when the screen is off.

A cloud development environment in your pocket Why a phone can drive real software work — the case for pairing a thin mobile client with a dedicated cloud dev machine that holds the repo, the terminal, and the agents. Treena Every "code on your phone" attempt before this generation failed the same way: it tried to make the phone do the computing. Cramped editors, emulated toolchains, dead batteries. The phone is a wonderful screen and a terrible workstation. So don't make it one. Thin client, real machine Treena's model is old wisdom with new hardware: the phone is the interface, and the work happens on a dedicated machine in the cloud. Your workspace — one machine, your own, with a persistent volume Your repo — cloned over GitHub sign-in; private repos included A full toolchain — shell, git, language runtimes, package managers Your agents — Claude Code, Codex, and Grok with your own accounts The phone sends intent and renders results. The machine does everything heavy: cloning, installing, compiling, testing. Your battery is spent on the screen, not on webpack. Why this suddenly matters Cloud dev environments existed for years as a desktop convenience. Two things changed the math: Agents made the work steerable. When most keystrokes are the agent's, the interface stops needing a full keyboard. Reading a plan, approving a diff, redirecting an approach — these are phone-sized interactions. The workspace became the agent's habitat. An agent needs tools: files to edit, commands to run, errors to read. A cloud machine gives it all of that in a place that keeps running whether your screen is on or not — start a task, lock the phone mid-run, come back to results. What survives the desk test The measure of a dev environment isn't where it runs. It's whether the output survives contact with your team's standards: - Branches and commits, not exported zip files - Diffs reviewed before merge, same as always - Tests run on a real machine, not "trust me" - Previews you can open to see the change live Everything flows through git, so nothing about your team's process changes. Colleagues see a normal PR. They don't need to know it was born on a train. Sync is a side effect Because the workspace is the source of truth, "sync" stops being a feature and becomes a property. Open the same repo from your laptop later — it's git, so the work is simply there. Phone-first never means phone-only. The best development machine is the one that's always on. The best interface is the one that's always with you. They were never supposed to be the same device. Join the waitlist / waitlist and carry your workspace everywhere.