# Key concepts

Understand the few terms you need to connect apps, find information, and use tools.

## Vision and Indra

**Vision** is the public product name used in this handbook. **Indra** remains in executable names such as `indra.search` and the installed command `indra`. Use the exact names advertised by your installation; changing a product label does not rename its commands.

## Source, connector, and account

A **source** is an app, service, or local resource, identified by a value such as `gmail`, `google-drive`, or `computer-files`. A **connector** gives Vision access to that source. An **account or binding** identifies the actual login, profile, device, folder, or workspace being used.

These are different questions: “Is Gmail supported?”, “Is it connected?”, and “Which Gmail account am I reading?” [Accounts and scope](/docs/vision/connectors/accounts) explains how to resolve the last two before an operation.

## Live information and saved information

A **live read** asks a connected source for information now. It is bounded by that account's access and the requested page or filters. A **saved search** queries information already collected into the **Vault**, Vision's local store.

A successful live read does not necessarily save its payload. A saved row does not prove the source is still connected or that the row reflects the latest change. **Sync** imports supported source history and tracks progress; it is a separate operation. See [Tools](/docs/vision/tools) to choose the right path.

## Tool, action, and method

A **tool** is an operation exposed to an agent, such as `indra.search`. An **action** is an operation executed through `indra.action` or the terminal's `action` command. A connector's **method** is one specific operation in its catalog.

For example, `indra.actions` discovers what is available, while `indra.action` executes an operation. A catalog entry describes an opportunity to act; it is not evidence that the action has already succeeded. The [action guide](/docs/vision/tools/actions) shows the complete sequence.

## CLI and MCP

The **CLI** is the command-line interface: you type a command into a terminal. **MCP**, the Model Context Protocol, lets an agent host discover and call installed tools. Both reach the same underlying product capabilities, but a local and a remote connection can expose different tool sets.

A notation such as `indra.actions({})` in this handbook describes an MCP tool request. It is not a JavaScript SDK or a public HTTP endpoint. For direct use, the equivalent is a terminal command such as `zortex actions`. See [CLI & MCP](/docs/vision/reference).

## Host, session, and job

The **local host** is the running service on the computer with your sources and Vault. The **agent host** owns the conversation. A **browser session** owns a particular browser task; a **connection job** tracks a particular authorization attempt. These identities are not interchangeable.

Use the returned job ID or session ID to continue an existing operation. A closed conversation does not prove a background job stopped. An expired browser session does not erase a saved document. [Follow long-running work](/docs/vision/autopilot/long-running-tasks) explains where to inspect each kind of work.

## Result and completion

An operation can return a success, an empty result, an error, or information that work is still pending. Read the actual returned state. For a write, inspect the resulting object before declaring the task complete; for a search, inspect enough source material to support the answer.

The handbook describes the intended experience and marks relevant current limitations. Current tool schemas determine which arguments your installation accepts. Neither documentation nor an available tool grants access beyond the user's instructions and the source's permissions.
