Cloud

Beyond running on this machine, LanMate can hand tasks to a cloud sandbox provisioned by your organization. Cloud and local are two parallel “run locations”, each with its own configuration, projects, sessions, and files — fully isolated from each other. Cloud is a Beta capability and only appears after an organization admin enables it.

Enabling Cloud

Settings → Cloud:

Flip on the “Cloud” switch and LanMate automatically completes, in order: start the cloud sandbox → obtain access tickets → connect to the cloud host
The first sandbox start is a cold start, usually taking tens of seconds to a few minutes; progress is shown on the page
When cloud is unavailable (e.g., the sandbox hasn’t been started), related entries will first prompt you to start the sandbox and continue once it succeeds

Turning cloud off pops a confirmation: after turning it off, this machine disconnects from the cloud host and the running cloud sandbox is stopped (environment and cloud-disk data are preserved), interrupting cloud tasks. The remote sandbox is only actually stopped after you confirm.

Running Tasks in the Cloud

New task: the settings bar of a new task has a “Run Location” selector; when no project is selected, you can switch between “Local / Cloud”
New project: pick the run location when creating a project; it is locked after creation, and every task under that project follows it
The run location cannot be changed after a session is created; a cloud session reports an explicit error when the cloud goes offline, never silently falling back to local

Artifacts and files from cloud sessions live in the cloud workspace and can be retrieved via “Download to this machine”; attachments are automatically uploaded to the cloud when sent (entire folders are packed and uploaded automatically).

Local and Cloud Are Fully Independent

Dimension	Description
Configuration	Model, approval, Git policy, and other settings are stored separately for local and cloud; the settings page lets you switch the write target; machine preferences like language and appearance always apply only to this computer
Projects & sessions	Each side keeps its own project list and session list; cloud sessions and projects carry a “Cloud” badge
Data pages	Extensions, Experts, Scheduled Tasks, Taskboard, My Files, and other pages offer a “Local / Cloud” switch at their top right, browsing their respective data

How to switch: the settings page has a “Local / Cloud” toggle at the top; data pages switch at their top right. Settings that are local-only are grayed out in the cloud position with an explanation.

Cloud Sandbox Management

Settings → Cloud is where you view and manage the cloud sandbox:

Sandbox status: not started / running, with Start / Restart / Stop buttons on the right
Connection status: connected / connecting / connection failed, with a “Reconnect” action
On connection failure, a failure card appears at the bottom right with three actions — “Retry Start / Check Settings / Turn Cloud Off” — plus a plain-language failure reason (e.g., service temporarily unavailable, client version too old, disabled by the organization)

When the sandbox version doesn’t match your local client, you’ll be prompted to rebuild the sandbox (rebuilding destroys the current sandbox; cloud-disk data is preserved).

Capability Boundaries in the Cloud

The following capabilities are local-only and unavailable in cloud sessions:

Computer use: it controls this computer’s desktop — unrelated to the cloud
Built-in browser: the browser panel is available only in local sessions
Plugins: plugins run locally and are not loaded in cloud sessions
Channels & mobile remote control: channel inboxes such as Lansenger, and mobile remote control, mirror this machine

Office document generation and reading work in the cloud (handled by the cloud’s built-in Python toolchain); document interaction is mainly generate, read, and download.

Permissions & Security

Cloud requires signing in with Lansenger; it is unavailable in anonymous mode
Enabled by organization admins in the admin console at the org → department → user levels; the cloud entry doesn’t show until enabled
The cloud sandbox runs on your organization’s private servers; task data leaves this machine and enters your organization’s cloud environment — follow your organization’s data-security requirements

New Task & Conversation: choosing a run location
Settings Overview: local / cloud configuration switching
Three-Tier Policies: enabling the cloud sandbox from the admin console