# Continue work

Save the task state a person or another agent needs, then resume from current observations.

To continue a task later, preserve its goal and the evidence of what has happened. A conversation summary is useful, but it is not proof that a live browser session or background operation still exists.

The agent host owns conversation persistence. Indra's browser sessions and source jobs have their own lifetimes. Do not assume that every host automatically remembers the task or restores it after a restart.

## Save a small, actionable handoff

Ask the current agent:

> Save a handoff for this task with the goal, selected account and destination, verified work, active job IDs, unresolved questions, and the next step. Identify where you saved it so I can give it to the next agent.

Use a persistence location actually supported by your host or a file you control, then open it to confirm it was saved. The handoff should contain:

```text
Goal and completion criterion:
Account, source, project, and destination:
Constraints and exclusions:
Verified completed work and output references:
Pending job/session IDs and last observed state:
Uncertainty or exact blocker:
Next action and the evidence needed to finish:
Relevant handbook page:
```

Record completed writes and their object identities so the next agent does not repeat them. Keep passwords, tokens, retained secret values, and signed authorization URLs out of ordinary summaries. A protected reference or the transaction ID is usually sufficient.

## Resume the task

Give the new agent the handoff and accessible outputs. Ask it to verify the current state before continuing. If you are continuing yourself, use the corresponding task guide and check the existing operation.

For a connection job:

```sh
indra --root "$indra_root" action --json '{"name":"connector.job","params":{"id":"<recorded-job-id>"}}'
```

For a still-live browser session:

```sh
indra --root "$indra_root" action --json '{"name":"browser.observe","params":{"sessionId":"<recorded-sessionId>"}}'
```

Set `$indra_root` to your existing Vault path using [CLI setup](/docs/vision/reference/cli#section-select-the-existing-vault). If the session is missing, follow [Browser sessions and profiles](/docs/vision/browser-computer/sessions); do not replay a saved control object. For a changed app record, read the current object before deciding whether another write is needed.

## Incorporate a correction

A new instruction can refine the account, scope, destination, or output. Update that part of the task and preserve useful completed work that still applies. If the correction invalidates an earlier change, make the required reconciliation explicit.

A status question does not automatically cancel the task. The agent should report what is known, identify the next meaningful check, and continue useful work unless you asked it to stop.

## Recover missing context

If the handoff is incomplete:

1. Inspect the saved output, current object, or returned job receipt.
2. Read relevant authorized project sources for decisions and constraints.
3. Recover the exact account and destination before consequential actions.
4. Ask only for information that cannot be recovered and materially changes the result.

Do not infer permission for a new source or account from the desire to keep moving. Preserve disabled sources and earlier exclusions.

## Keep one owner for ongoing work

An Indra background job may still be running after the previous caller stopped. Continue it through its existing ID. When agents divide a task, assign distinct scopes and one owner for shared edits or transactions.

A later agent should finish the remaining work, verify the result, and update the handoff's outcome. If a necessary device or credential remains unavailable, retain the verified partial result and name that exact next step.
