Vision works within the selected provider account, resource, local operating-system access, and the task you requested. These boundaries are independent. A connected account does not make an unavailable OS permission appear, and a broad provider grant does not expand a read-only task.
Enable or disable one source
Find the installed source plugin:
indra --root "/absolute/path/to/your/Vault" manage --json '{"what":"plugins","about":"gmail","limit":25,"offset":0}'
Use its actual returned indra-source-... ID:
indra --root "/absolute/path/to/your/Vault" manage --json '{"what":"plugin.set-enabled","id":"<returned-source-plugin-id>","enabled":false}'
Set enabled:true to enable it again. Inspect source status afterward. This control applies to source providers, not foundational product components.
Disabling retains collected data. It is different from erasing the Vault or removing the provider's account grant.
Control automatic startup and collection
| Setting | Effect on processes launched with it |
|---|---|
ZORTEX_AUTO_CONNECT=0 |
Opts out of the automatic connection pass. |
ZORTEX_AUTO_SYNC=0 |
Disables automatic full sync; explicit sync remains available. |
ZORTEX_OPEN_HELP=0 |
Prints the local help link without automatically opening a browser. |
ZORTEX_UPDATES=0 |
Disables update discovery and application. |
For example, to start a host with automatic full sync disabled, first stop its current owner. Then set the variable in the shell that will launch it.
macOS or another POSIX shell:
export ZORTEX_AUTO_SYNC=0
indra --root "/absolute/path/to/your/Vault" host start
Windows PowerShell:
$env:ZORTEX_AUTO_SYNC = '0'
indra --root "C:/absolute/path/to/your/Vault" host start
These settings do not change a process already running. Apply the same choice to any separately launched MCP or web process.
A generated Codex catalog or login launcher can retain its saved environment. Do not assume reinstalling overwrites it. Verify the actual catalog binding when changing modes, and recreate or refresh it through the supported MCP setup procedure. Re-enable login startup from the intended environment when changing its launch settings.
Control login startup separately
indra --root "/absolute/path/to/your/Vault" host disable
indra --root "/absolute/path/to/your/Vault" host stop
The first removes login startup; the second stops the current host. Neither deletes data. To run now without login startup, use host start alone. To register startup, use host enable.
Change provider access
Use connection help to check or reauthorize the intended account. Some providers distinguish read access from write Actions; inspect the requested consent and current method effect.
For provider-wide revocation, use that provider's account-security or connected-app controls. The fixed connector.disconnect Action is not a universal revoke command. After revoking, check the source state before another task. Retained history can remain searchable even when live access has ended.
Native access is controlled by the operating system and the source's selected folders, profiles, or service. Repair the specific permission reported by the source; repeated web sign-in cannot grant local filesystem or accessibility access.
Revoke a remote client
Use host local-cloud grants and host local-cloud revoke <returned-grant-id> on the original computer. Remote access includes the complete procedure.
Revocation cannot reverse an external operation that already completed, and deleting or changing local information does not remove a previously published static share.