# Background host and reliability

Start and stop the existing host, inspect ongoing work, and recover without duplicate operations.

The background host keeps the installation's ongoing services available. The agent conversation, a web page, and a short terminal call are clients of that work. A client closing or returning does not always mean the underlying operation ended.

## Start or inspect the host

Use the same existing Vault for each command:

```sh
indra --root "/absolute/path/to/your/Vault" host status
indra --root "/absolute/path/to/your/Vault" host start
```

Repeated starts reuse a running owner. Inspect the actual status instead of launching several independent processes to make a slow operation progress.

Status can report current stage, heartbeat, last cycle, and relevant source or remote-link state. Missing or failed status is an unknown state; it does not prove the host is absent.

## Control login startup

```sh
indra --root "/absolute/path/to/your/Vault" host enable
indra --root "/absolute/path/to/your/Vault" host disable
```

`enable` registers login startup. `disable` removes that registration. Neither command is a substitute for starting or stopping the current process.

An authorized onboarding run can register startup after its pass, even while some sources still need setup. Apply your intended [launch settings](/docs/vision/settings/permissions) before onboarding or registering a launcher.

## Stop the current owner

```sh
indra --root "/absolute/path/to/your/Vault" host stop
```

Read its result. A recorded process exit with `cleanupAcknowledged:false` differs from a confirmed clean shutdown. A reachable owner whose status or protocol cannot be read may still be alive.

To prevent automatic restart at login and stop now, run `host disable`, then `host stop`. These controls keep the Vault and its completed work.

## Follow ongoing operations

Use the identity returned by the operation:

| Work | Follow-up |
| --- | --- |
| Connector authorization | `connector.job` with the returned job ID, while continuing its live provider page |
| Resident startup attempt | `indra.manage {"what":"startup"}` or the returned `fleet.receipt` ID |
| Current readiness across sources | `indra.manage {"what":"onboarding"}` |
| Full collection | Galaxy **Apps → source → Full sync**, current status, and its returned execution receipt |
| Owned browser task | Its returned session ID and current snapshot |

Poll the existing work at a cadence appropriate to its response. A caller timeout does not justify a second dispatch. A pending write needs readback before retrying because its external effect may already exist.

## Recover after interruption

1. Inspect the host and the affected source or job.
2. Preserve completed peers and the selected account.
3. Resume an available continuation or saved cursor.
4. If ownership or cleanup is unresolved, establish the old operation's state before retry.
5. Verify the task's original result after recovery.

A stopped host can be restarted with the same root. A browser session may expire and require a new observation; it is not a durable general task record. An agent should retain the task goal, completed work, and remaining steps in its own supported context.

## Upgrade a running owner

Keep the old entrypoint until it has confirmed shutdown. If a newer CLI reports incompatible IPC, use the previous installation's CLI to control that owner. A reinstall or new executable cannot by itself prove the old one stopped.

After updating, restart with the intended environment and check the loaded version and one representative source operation. See [Updates](/docs/vision/settings/updates).

There is no general Vision task scheduler or universal pause/resume/cancel API implied by these host commands. [Autopilot](/docs/vision/autopilot) describes how an agent should continue user work using the actual available operations.
