LoneAct Documentation Product surface

Cloud workbench

Connect to your authorised device from any browser to continue work remotely, while project data stays on that device.

What it is

The cloud workbench is LoneAct's remote entry point. After signing in, you can discover every remote-enabled device under the same account and every project folder on it; each device can own multiple Locations. Cross-account collaboration uses explicit, revocable Grants. It is not a second repository that copies your project to the cloud.

Cross-device

After leaving the computer that is running the project, you can still reach same-account or granted projects from a browser.

Connect to your device

The cloud only discovers and relays; tools execute on the device that owns the project.

Discovery and Grants

Same-account devices are discovered automatically; cross-account access is granted per Location and capability, can be revoked, and leaves a record.

Before you start

01

Your device is online

The computer that owns the project must be online and connected to your LoneAct account.

02

Confirm discovery and access

Same-account devices appear automatically; for cross-account work, create a Grant scoped to the Location and start with the narrowest scope.

03

Sign in to the cloud

Open the cloud workbench and confirm that your device is online, the project is visible, and the model list is available.

04

Continue or start a Conversation

Open an existing conversation to continue, or create a new one in an authorized project.

Cloud and data boundaries

The cloud account service stores accounts, device ownership, access grants, and necessary audit metadata. Project files, conversation content, tool results, and Agent memory stay on your device and are not copied into cloud business data because you use the cloud interface.

ScenarioWhere it runsWhere data lives
Open a local project remotelyThe device that owns the projectThat device
Multiple projects on one deviceEach project's owning deviceEach Location keeps its own conversations and run records
Temporary cloud chatThe cloud serviceFull chat history is not persisted; return to the project workbench when you need to keep it
Account and grant managementThe cloud account serviceAccount, device, access grant, and audit metadata

See Projects and devices for the full model of multiple projects, same-account discovery, and cross-account Grants.

The cloud is not an offline backup

When your device is offline, the cloud cannot execute local tools for you. Important projects and execution records should still follow your local backup and version control policy.

Boundaries and guidance

  • The cloud workbench is for continuing work remotely, not for bypassing the file and terminal scope on your own computer.
  • When sharing a project, grant read-only or limited scope per member; do not share personal accounts.
  • Revoke access you no longer need after a remote task, and check your device's online status.
  • When you need the full set of local tools and long-term project records, prefer Local Web or the IDE.