Your Next Coding Session Starts in a Browser

The useful part of a coding session is the work: explaining the change, trying an approach, reading the diff. Reinstalling dependencies on another computer is rarely the part you were looking forward to.

Layerbase Agent Servers give your project a place to stay. Your repositories, coding tools, and terminal live on a private Linux machine. You open your browser to work with them. When you change computers, you reconnect to that machine instead of assembling the environment again.

Here is a small workflow to try: give an agent a design for a password reset screen, let it implement the change on a feature branch, and review the result. The example repository below is fictional; use a development project of your own.

Set up once, then start with the task

Create a server from the dashboard, choose its size and location, and review the monthly price before checkout. Setup usually takes 5 to 8 minutes. Agent Servers are currently in beta under the early adopter terms.

When the server is ready, connect the Layerbase GitHub App and select your repository. Choose a supported coding agent in the dashboard, install it, and complete its sign-in flow. Installation puts the tool on the machine; sign-in connects your provider account.

Your server subscription covers the machine. You bring your own agent subscription or API key, and the provider's usage limits and charges still apply. The server page lists current sizes and prices.

Open Terminal. You now have a shell on the server without configuring a local terminal or adding an SSH key. Node.js, pnpm, Docker, and Git are already available; install any additional dependencies your project needs.

Give the agent a branch and some ground rules

On the Repositories tab, set the project's production branch and, if you use one, its staging branch. These settings tell supported agents where feature work starts and where pull requests should go. Add shared server instructions for the conventions you want them to use.

For our example project, a useful task would be:

In acme/web, create a feature worktree for the password reset screen.
Read the project instructions and existing authentication flow first.
Use the attached design, add the missing form states, and run the relevant tests.
Show me the diff before opening a pull request.

A separate worktree gives the task its own working directory. That is helpful when another session is working on a different branch. Shared services and the repository's history still need coordination, so keep tasks scoped and review changes before merging.

Put the design next to the work

Drag a screenshot onto the browser terminal, or paste an image. The terminal uploads it to the server and inserts its path, so you can point your agent at the actual file. The terminal guide lists supported file types and limits.

Open the file explorer alongside the terminal to browse the repository, preview an image, or read a file the agent changed. You can make a quick text edit there too. For a larger review, push the branch and use your normal pull request tools, or connect your remote editor over SSH.

That makes a browser session useful beyond typing prompts. You can bring in context, see the files, run commands, and check the result in one place.

Close the tab. Come back to the session.

The terminal session lives on the workspace. Closing your browser or disconnecting your laptop does not stop it while the machine keeps running. Open the server from another computer and reconnect to the session.

The important distinction is that the environment persists, not that the agent can work forever without you. It may finish, fail, reach a provider limit, or wait for permission. Rebooting or stopping the server interrupts running processes. Check the output when you return, and keep important work committed and pushed.

For a second task, open another terminal session and use a separate worktree. Name sessions after their tasks so you know where to return.

Bring the session to your phone

The next browser can be on your phone. Ask Claude Code or Codex to investigate an outage from dinner or prepare a small feature while you are away from your desk, using the repository and diagnostic access you configured.

First-time setup is easier on a computer while you connect GitHub, select repositories, and sign in to your agent subscriptions. Afterward, open Agent Servers on your phone and select the existing session. Layerbase is a PWA you can add to your home screen, not a native mobile app. Terminal access needs internet; the mobile experience will keep improving during beta. The browser uses the actual CLI interface, with a familiar terminal workflow and extra keys for phone keyboards.

You can also use Cursor CLI, Devin CLI, Gemini CLI, Grok Build, or other compatible Linux CLI tools. Devin Desktop is the editor formerly called Windsurf; this workflow uses Devin CLI. Without an agent subscription, install OpenCode and select an available free model, subject to changing availability and limits. VM charges and paid model usage remain separate.

For work and personal subscriptions, keep separate VMs signed in to the appropriate agent accounts, with the intended repositories selected for each. Terminal tabs on one VM share its user environment and do not isolate credentials. Follow the mobile setup walkthrough before you need it on the go.

Review, then ship through your normal workflow

Ask the agent to summarize its changes and show the tests it ran. Read the diff, try the relevant behavior, and open a pull request when you are satisfied. Agent Server branch instructions give the agent guidance; your review and repository protections still matter.

The server is your development machine. Deploy the application to the hosting environment you use for production. If the project needs a managed database, Layerbase databases have a free tier with no credit card required. Buying a server is optional and does not change that.

Keep backups of anything you cannot recreate. Agent Server billing renews monthly until you cancel, and stopping the machine does not pause it. Export files before paid access ends; server files may be permanently deleted afterward.

The next session is the payoff. Open the browser, return to your repository, and start with the next change. Your tools and project setup are already there.

Explore Agent Servers, or follow the getting-started guide to set up your first one.