Introducing Agent Servers on Layerbase

Open your browser. Connect your repository. Give your coding agent the next task.

Layerbase Agent Servers put your development environment on a private machine you can come back to. Your code, dependencies, and terminal session live there, so moving to another computer does not mean rebuilding your setup. Close the tab and reconnect to the same session while the server keeps running.

The browser terminal is only the beginning. Browse files beside your agent, drop in a screenshot to explain a change, and give supported agents shared project instructions. Use SSH and your own remote editor whenever you want a different way in.

Agent Servers are available in beta through the Agent Servers dashboard. Each server has its own monthly subscription, separate from agent usage and from Layerbase's free managed database tier. You do not need a server to create a free database.

Bring the session to your phone

Bring your agents out with you. A critical outage at dinner can start with Claude Code or Codex investigating your prepared repository from your phone, then a reviewed fix through your usual workflow. A quick feature can follow the same path.

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.

See a complete coding session

Our browser coding walkthrough follows a task from a connected GitHub repository to reviewed changes: set the branch workflow, share a design, run the agent, and return to the terminal later.

A machine you can make your own

A server is a Linux VM with its own filesystem and an Ubuntu user with sudo access. You can install project dependencies, run Docker, clone repositories, and use the command-line tools your project needs.

That matters when the environment is part of the work. A project might need a particular runtime, a local service, and a build tool that takes a while to configure. Those changes stay on your server between connections. You do not need to recreate them every time you open a browser tab.

The starting workflow is straightforward:

Create a server and choose its size.
Review the monthly price and complete checkout.
Wait for setup to finish.
Open the terminal, clone your repository, and work.

Choose enough memory for the project, not just the terminal. A small command-line task and a large application build have very different requirements.

Bring your existing coding tools

The dashboard provides installation and sign-in controls for supported coding agents. Installing a tool and authenticating it are separate steps: the machine needs the software, and the software needs your account.

For example, you can install Claude Code and complete its account sign-in from your browser. The subscription walkthrough covers that flow, including how to avoid accidentally selecting API billing.

Your server subscription pays for the machine. Agent subscriptions and API usage remain separate, with the provider's own limits and account requirements. Moving a tool to a remote machine does not give it a new usage allowance.

You can also use ordinary development tools directly. Agent Servers do not require every command to go through an agent.

Close the tab and reconnect

The web terminal opens a shell on your workspace. Its session uses tmux, so disconnecting from the browser leaves the terminal session on the machine. Reopen the terminal to return to it.

That is useful when you start a task at your desk and check it from another computer. The remote machine keeps running independently of your laptop.

There are practical limits. A program can finish, fail, or pause for input. A reboot or a stopped server ends running processes. A persistent terminal makes disconnection convenient; it does not make a job immune to interruption. Save important output to files and push your code to your repository.

The terminal also supports file uploads, which is useful for handing a screenshot or sample file to a tool. See the terminal documentation for supported files and upload limits.

How it fits with Layerbase databases

Agent Servers and managed databases solve different parts of development. A server runs your code and tools. A managed database provides a database service your application connects to.

You can connect an application on your server to a Layerbase database using its connection details. You can also run development services on the VM yourself. In that case, you are responsible for their configuration and data; installing a database on a server does not turn it into a managed database service.

Keep development credentials scoped to the resources the project needs. A remote development environment should not need unrestricted production access just to run a test suite.

Monthly billing and beta expectations

Each server has a monthly price shown before checkout. Applicable taxes are calculated during checkout. Stopping the machine does not pause the subscription; use the renewal controls when you want to stop renewing it.

Export your files before paid access ends. Do not depend on a recovery window after expiry or keep the only copy of important work on the machine.

During beta, expect rough edges in provisioning, tool installation, and connection flows. Keep code in version control, keep backups of data that cannot be recreated, and use a separate production hosting environment for applications that need production availability guarantees. Review the terms and acceptable-use policy before purchasing.

Give your next project a place to stay. Explore server sizes, connect a repository, and start with one task. When you come back, start with the work.