# Install and open Vision

Install the command-line tools, reuse your data directory, and open the local connection and status pages.

You can use Vision from a terminal or connect it to an agent. Installation gives you the `zortex` and `indra` commands. **Local connection help** handles account setup; **Galaxy** shows source and synchronization status.

## Install the published package

Use the command on the [installation page](/install), which owns the public distribution channel. It currently specifies Node.js 24 or newer and:

```sh
npm install -g @zortexhq/indra-v2@next
```

The `next` channel can contain prereleases. The installation page also describes `latest` for the stable channel. After installation, open a new terminal and check the commands actually installed:

```sh
zortex --version
indra --help
```

The handbook does not pin a package version. Some source and older installations use a different package identifier. Do not switch package names to work around an unavailable release or assume a source change is already in the registry. If npm cannot provide the selected release, retain any working installation and use the reported error to resolve availability.

## Use the existing Vault

The Vault is Vision's local data directory. The `zortex` wrapper resolves an explicit `--root`, then `ZORTEX_ROOT`, an existing supported agent binding, or the platform default. The defaults are `%LOCALAPPDATA%\Zortex\Indra` on Windows and `~/.zortex/indra-v2` on Unix-like systems.

Prefer `zortex` when the installation already knows the directory. For explicit `indra` examples in this handbook, set the variable to your **existing absolute directory**:

**macOS or Linux shell**

```sh
indra_root="$HOME/.zortex/indra-v2"
indra --root "$indra_root" manage --json '{"what":"vault"}'
```

**PowerShell**

```powershell
$indra_root = Join-Path $env:LOCALAPPDATA 'Zortex\Indra'
indra --root "$indra_root" manage --json '{"what":"vault"}'
```

Replace the default path if your installation uses another directory. Check the result before continuing. A different Vault can have different connections, records, and state. [Local data and Vault](/docs/vision/settings/vault) explains the storage controls.

## Open connection help

```sh
zortex help
```

Or, with an explicit directory:

```sh
indra --root "$indra_root" help
```

The command opens **Local connection help** and prints the current local URL. Keep the terminal process running. Use the URL it returns; do not bookmark a signed URL as a permanent entry point. When a help session expires, run the command again.

There is a deliberate difference between `indra --help`, which prints command help, and `indra --root "$indra_root" help`, which opens the live page. `zortex --help` prints help; `zortex help` opens the page with its resolved directory.

To start or resume the automatic setup flow, use `zortex onboard`. To open recovery without beginning a new automatic pass, use `zortex recover`. Setup may work on several enabled sources; for one app, use [Connect a service](/docs/vision/connectors/connect).

## Open the local app

```sh
zortex web
```

Or:

```sh
indra web --root "$indra_root"
```

Open the signed loopback URL printed by the command and keep its process running. The port can change if the default is occupied. In **Apps**, find a source, open its details, and inspect connection state, local record counts, and **Full sync** information. Refresh to see current state.

Galaxy is a status view. Its current adapter does not provide working in-app chat, source connection switches, marketplace installation, or cloud-link provisioning. Use connection help for setup, terminal tools for reads and actions, and [Remote access](/docs/vision/reference/remote-access) for a supported remote connection.

## Start a task or connect an agent

Follow [Get started](/docs/vision/quickstart) for a complete read. To use the same capabilities in an agent host, follow [Connect an agent through MCP](/docs/vision/reference/mcp-setup). Opening Galaxy alone does not connect an agent or complete an app authorization.

If the local page stops loading, first check that its owning terminal or host is still running. Reopen it from the command rather than retrying an expired URL. See [Troubleshooting](/docs/vision/settings/troubleshooting) for command, connection, and host failures.
