Skip to content
Lattis Lattis

Remote Control

The Lattis web app can connect to a desktop where Lattis is running. This lets you check work and take a few useful actions from another computer or a phone.

The work still runs on the desktop. The web app is a remote view and control surface. It does not provide hosted coding agents, and it cannot do anything while the desktop is offline.

What you can do

Section titled “What you can do”

From Devices, open a connected desktop to see its projects and branches. Depending on the desktop version and its current state, you can:

  • read ahead, behind, uncommitted, and pull request status
  • start an installed agent on an existing branch
  • start a new branch with an agent and an optional prompt
  • open a plain terminal on the desktop
  • attach to a running agent session
  • watch a terminal in the browser or switch to Drive mode and type
  • view changed files and request a file diff
  • pull, commit, push, open, and manage pull requests
  • update and restart the desktop app

The web app shows the desktop version and disables controls that need a newer build. Update the desktop when a control is not available.

Connect a desktop

Section titled “Connect a desktop”
  1. Sign in to the Lattis web app.
  2. Install and open Lattis on the machine that owns the project.
  3. Sign in to the desktop with the same account.
  4. Open Devices in the web app.
  5. Select the desktop, then open one of its projects.

The desktop needs an internet connection. You do not need to expose its local daemon port or set up port forwarding. The desktop connects out to Lattis, and the browser uses that connection to reach it.

If the desktop is not listed, open the desktop and check that it is signed in and that remote control is enabled. A desktop that is asleep, offline, or still starting may show old information until it checks in again.

When the app is closed

Section titled “When the app is closed”

The Lattis service keeps running on the desktop after you close the app. While the service runs, the web app can still start, stop, and resume agent sessions on an existing branch, and you can watch and drive them in the browser. Stop a session from the Stop button next to it on the branch’s Overview. The device page tells you when the app is closed. Other actions, such as a push or a new branch, wait until you open the app again.

When you open the app, it shows the sessions that started while it was closed. The branch list on the web is the last one the app sent, so a new worktree appears only after the app opens. If the service restarted while the app was closed, a session you start still runs, but the web cannot list it until you open the app.

Use the browser terminal

Section titled “Use the browser terminal”

Open a running session and choose Watch or Drive. Watch is read-only. Drive sends keyboard input to the session on the desktop.

On a phone or tablet, the terminal starts in Watch mode. This is intentional. Switch to Drive when you want to type. The browser also provides keys that are hard to enter on a soft keyboard.

The terminal can reconnect after a short network interruption. If the session has ended, the browser cannot restart that same session. Start another session from the branch’s New session menu.

What it does not do yet

Section titled “What it does not do yet”

Remote control is still under active development. The web app does not yet provide the full desktop workspace. In particular, it does not offer the desktop’s tiled panes, Files editor, Review and Assist views, or every desktop action.

The remote terminal is also a practical first version. It is best for checking a session or answering a short task while away from the desktop. It is not meant to replace the desktop for long coding sessions.

The available controls can change as the desktop and web app move at different speeds. If a control is missing, update Lattis on the device first. If something still looks wrong, the Troubleshooting page has the usual connection checks.

Section titled “Related pages”