Work From Anywhere With the Layerbase PWA

You do not always need to sit down for a full coding session. Sometimes you need to answer an agent's question, check a test run, or get a small fix ready before you return to your desk.

Layerbase AI VM Workspaces puts your coding environment on a full Linux VM you can reach from your phone. The agent gets its own computer with your chosen GitHub repositories, dependencies, and command-line tools. You open the browser terminal and continue working.

A home-screen app, through the web

Layerbase is a progressive web app, or PWA. You can add it to your home screen from a supported browser. There is no native iOS or Android app. We are continuing to make the web experience more mobile friendly during beta.

On iPhone, open Layerbase in Safari and use Share > Add to Home Screen. On Android, look for Install app or Add to Home screen in your browser's menu. The exact wording depends on the browser. Sign in, open AI VM Workspaces, and select your machine.

The terminal needs internet access. Installing the PWA does not download the VM or make a disconnected terminal work offline. Your processes live on the remote machine and can keep running when you close the browser, as long as that machine stays running.

Do the first setup at your desk

First-time setup is easier on a computer: connect GitHub, select repositories, install your agents, and sign in to the subscriptions or API accounts you intend to use. Start a named terminal session and verify a small task before switching devices.

Once that is done, your phone opens the same workspace. Select the existing session from Sessions to return to your work. For the full walkthrough, see Claude Code and Codex on mobile.

The browser feels like your local terminal because you are using the same shell tools and interactive agent CLIs. Phone keyboards and screen sizes still differ; extra terminal keys help, and SSH or your remote editor remain available when you want a larger workspace.

When a phone is enough

A critical outage interrupts dinner. You can ask Claude Code or Codex to inspect the repository, reproduce the regression, and prepare a fix. With the required diagnostic access already configured, you can work toward resolving it from your phone. Keep your normal review and deployment checks; an agent's confident summary is not a substitute for the test results.

Or perhaps you have ten minutes between appointments. Describe a small feature, ask for a branch and tests, and review the result later. The useful part is having the environment ready, so you can spend that time on the task.

Your tools and accounts come with you

Use Claude Code, Codex, Cursor CLI, Devin CLI, Gemini CLI, or Grok Build. Other compatible Linux CLI tools can be installed through the shell. If you know Windsurf, its editor is now Devin Desktop; the terminal workflow uses Devin CLI.

If you do not have an agent subscription, install OpenCode and choose from its currently available free models. Availability and limits change. Workspace billing covers the machine, while any paid agent usage is separate.

For work and personal subscriptions, keep a separate VM for each context, signed in to the appropriate agent accounts and connected only to the intended repositories. Separate browser tabs on one VM do not isolate credentials. This gives you a clear choice of environment when you reach for your phone.

Bring the work home again

When you return to your computer, reopen the same workspace and session. Your tools and project files are already there. A reboot, stopped VM, or failed process can interrupt a job, so keep important work committed and pushed.

Explore AI VM Workspaces. Set up at your desk, then take your terminal with you.