Business data local, control plane in the cloud
LoneAct uses a local-first data boundary. Project files, conversations, runs, tasks, Agent teams, artifacts, checkpoints, and execution logs are stored on the computer that hosts that project folder. The cloud only handles the account data that makes multi-device collaboration possible, and does not copy business content into a second cloud repository.
Your project files, conversation history, Agent memory, and secrets stay on your machine or your private runtime. When you uninstall or clear data, the local runtime storage directory is the source of truth.
Where data lives
| Data | Local / private mode | Cloud account service |
|---|---|---|
| Project files and folders | Stored and accessed inside the project folder | Full file contents are not stored |
| Conversations and execution records | Stores conversations, tool calls, diffs, and results | Not stored as a business database |
| Agent Team and memory | Stores roles, instances, memory, and critical paths | Not copied into a separate team memory store |
| Secrets | Stored in host secure storage or a location only this machine can read | Plaintext values are never received |
| Accounts, devices, and grants | Keeps only the connection state this machine needs | Stores accounts, device ownership, access grants, and necessary audit metadata |
| Temporary Cloud Chat runs | Not applicable | Keeps only the state needed for the current run; full chat history is not persisted |
Model requests are another boundary
Local-first describes LoneAct's storage and control plane; it does not mean model requests never leave your machine. When an Agent executes, the current context is sent to the model service you selected, and that service's data handling depends on the provider agreement and your deployment.
- When choosing a model, confirm the provider, deployment region, and data processing terms at the same time.
- For sensitive projects, choose a privately deployed model or a provider approved by your organization.
- Never write secret values into a prompt; use Secrets references so LoneAct resolves them when tools execute.
- For fully offline work, use a local model service and confirm that neither the tools nor the Agent depend on the public internet.
Cloud Chat and the local Workbench
Local / private workbench
Projects, conversations, teams, and execution records are stored on your computer, which suits long-running projects and sensitive data.
Cloud Chat
For temporary conversations and remote assistance, where full chat history is not written as cloud business data. Continue in the local Workbench when you need a long-term project record.
Goals, decisions, changes, and test evidence worth keeping belong in a Project Conversation, not only in a temporary chat.
Backup and migration
Backup
Protect LoneAct storage, project repositories, and the Agent memory directories you need according to your organization's backup policy.
Migration
Move project folders and LoneAct storage when you change machines; do not hard-code paths in conversations or rules.
Cleanup
Confirm the impact before deleting a project or Agent; deleted local data usually cannot be restored from the cloud.