Latitude is a small local gateway that lets agents send useful details to an end user.
An agent can publish a page, screenshot, video, static site, live app preview, project diff, or terminal session into Latitude, then hand the user a private browser URL to review it. Latitude keeps the end-user surface simple while giving agents a consistent way to share work in progress.
- Sharing agent results without asking the user to inspect local files.
- Previewing generated pages, apps, images, videos, and reports.
- Giving the user a browser-based view of project status, diffs, and terminals.
- Serving local work through one authenticated public gateway.
- Creating deployment share links that can be open, password-protected, auto-expiring, or manually deleted.
copy latitude.example.json latitude.json
cargo run -- --config latitude.jsonOpen http://127.0.0.1:8080/ and sign in with the configured public password. The example config uses test; change it before exposing Latitude outside your machine.
Latitude stores projects, deployments, page content, and share links in the configured data directory. The config file contains boot settings such as listener binds, public password, desktop options, and data_dir.
Latitude can expose a root-level desktop viewer at /_desktop when desktop.enabled is set to true.
Use desktop.mode: "external" to bridge to an already-running VNC server. The default external target is 127.0.0.1:5900, view-only in the noVNC client, and non-loopback VNC hosts are rejected unless allow_non_loopback is explicitly enabled.
On Windows, run .\init-ultravnc.ps1 to prepare UltraVNC in portable mode under tools/ultravnc/. Run .\init-ultravnc.ps1 -Install from an elevated PowerShell session to install and start it as a loopback-only Windows service on 127.0.0.1:5900. Service mode can handle UAC-protected screens; application mode cannot.
UltraVNC is GPL software. Keep its license and source-offer materials with any redistributed helper bundle; Latitude's MIT source stays separate from the helper process.
Enable t3code in the boot config to add an Open in T3 Code action to every project. An authenticated click connects to the configured T3 Code server, registers the repository, creates a five-minute one-time pairing credential, and opens a new T3 Code draft for that project. Latitude only starts T3 Code when start_if_needed is explicitly enabled.
For access from another computer or a VM, configure gateway_bind (for example 0.0.0.0:5598) and set base_url to auto. Latitude then exposes the existing loopback T3 server through a separate password-protected HTTP/WebSocket listener. auto keeps the hostname used to reach Latitude and substitutes the gateway port, so the same config works through localhost, a LAN hostname, or a VM address. Expose or tunnel the gateway port alongside the main Latitude port. If TLS or port mapping changes the public gateway URL, set base_url to that explicit URL instead.
Agents can configure Latitude for you.
In normal use, you should not need to hand-write project, page, proxy, or static-site entries. Ask the agent to publish what it wants you to see, and it can use the Latitude CLI or local command API to create the right project and URL.
The command API is intended for local agent use. Keep it bound to localhost, and only expose the authenticated public gateway when sharing Latitude through a tunnel.
Share links expose one deployment without requiring the recipient to know the main project URL. They can be open, protected by a per-link password, expire automatically, and be deleted manually.
cargo run -- share create demo preview
cargo run -- share create demo preview --password "review-only" --expires-in 2h
cargo run -- share list
cargo run -- share delete <token>The generated URL uses /__latitude/share/<token>/. Deleting the token or reaching expires_at immediately disables that share path.