Skip to main content

ApplicationsPreview

Applications

A workspace runs local processes, Docker services, and hosted Linux GUI processes declared in agent-up.json.

Console, metrics, and the database explorer belong to the selected application.

HTTP applications render in a browser view; desktopApplications use a ticketed streamed viewer.

  1. Declare the application in agent-up.json

  2. Start the workspace so ports are allocated

  3. Open the application surface

Key

ports[].variable

Where it differs

Desktop

Selecting an application opens Console, Metrics, Diagnostics, and, when database is true, a Postgres explorer. HTTP ports keep a native view. desktopApplications use a ticketed streamed viewer.

Mobile

Apps shows workspace start/stop and live health above the application list, then opens each application as an inner page. HTTP UIs load through the Server proxy. desktopApplications use the streamed viewer.

Application tabs​

Selecting an application opens Console, Metrics, Diagnostics, and, when database is true, a Postgres explorer.

The Server owns port allocation and injects the workspace's full allocated port map into each launched local process. Applications should read the relevant environment variables instead of assuming fixed localhost ports.

Docker containers can call host-run applications in the same workspace through host.agent-up when the host-run application listens on an address reachable from Docker's host gateway. A process bound only to 127.0.0.1 is not reachable from containers through this alias. Inline Docker environment values may reference allocated workspace ports with ${VARIABLE}, such as BACKEND_URL=http://host.agent-up:${API_PORT}.

Hosted Linux GUI processes​

desktopApplications are Linux graphical applications hosted on Server-owned virtual displays and streamed to Desktop and Mobile. Existing HTTP application tabs continue to connect directly to their allocated ports and do not use the streaming path.

Console and metrics​

Application output is a selectable console surface. Prefix install output with [install]. Metrics are declared on a port in agent-up.json (ports[].metrics) and shown as summary cards and time-series charts.

Next in this slice

Configuration

The JSON that declares applications.