Local Cloud lets an authorized remote client use supported Vision operations on the original computer. The Vault and execution stay on that computer. It must remain awake, online, and running its host.
Use this route only when your installed version offers host local-cloud. Connecting an account to the website or opening a Galaxy panel does not by itself provision a working remote link.
Enable and verify remote access
-
Enable the link on the original computer
Use the existing Vault:
Shell indra --root "/absolute/path/to/your/Vault" host local-cloud on indra --root "/absolute/path/to/your/Vault" host startIf the first command reports that the running host must restart, stop it and start it again:
Shell indra --root "/absolute/path/to/your/Vault" host stop indra --root "/absolute/path/to/your/Vault" host startInspect the returned Local Cloud state and current
/mcpURL. Enabling the setting alone does not prove the tunnel is online. First startup can need the supported tunnel component and network access; use the reported failure if provisioning does not finish. -
Connect your remote MCP client
Add the exact returned URL through that client's remote MCP connection interface. Complete the connection's authorization flow. Supported cloud clients use OAuth; supported bridge clients can use the device flow.
If the authorization asks for the local consent password, read it on the original computer:
Shell indra --root "/absolute/path/to/your/Vault" host local-cloud passwordEnter it only into that connection's authorization flow. Do not put it in a shared document, support screenshot, or public URL.
Temporary tunnel addresses can change when the host restarts. Use the new returned address and reconnect the client when necessary. A managed persistent route requires its own completed provisioning; this command does not establish that provisioned state.
-
Verify the intended capability
Inspect the remote tool list. A read grant exposes read operations; an action grant can expose source, browser, and computer operations available on the original machine. The remote connection does not install missing native drivers or grant OS access.
Call
indra.instruction, then inspect the relevant source. For a selected source page, remoteindra.readaccepts:JSON {"source":"gmail","request":{"limit":5}}It retains only that returned page for subsequent
indra.search. Ordinary local MCP instead offers the transientconnector.readAction. See MCP tools for the distinction.Finish a small representative task before relying on the connection. A discovered URL or successful login is not proof that a provider read or write worked.
Inspect and revoke access
List current connections:
indra --root "/absolute/path/to/your/Vault" host local-cloud grants
Revoke one using its returned grant ID:
indra --root "/absolute/path/to/your/Vault" host local-cloud revoke "<returned-grant-id>"
To close the current link and prevent the next host from reopening it:
indra --root "/absolute/path/to/your/Vault" host local-cloud off
indra --root "/absolute/path/to/your/Vault" host stop
Stopping the host closes its current link. Revocation prevents subsequent authorized use; it does not undo an external action that already took effect.
When the remote client cannot connect
Check host status on the original computer. Confirm that it is awake, the current link is online, the client uses the current URL, and the grant remains valid. A source-refresh failure can coexist with readable retained records; diagnose the route and the source separately.
On supported macOS hosts, host local-cloud keep-awake on requests an AC-only keep-awake setting for the resident. Restart the host after changing it. This does not guarantee closed-lid availability.
Do not create a new empty Vault on a cloud runner as a recovery step. Continue through the original host and connection recovery.