Use this guide when an app connection has reached a sign-in page, account choice, consent step, or device challenge. For choosing a new service and its access scope, start with Connect a service.
Finish the connection yourself
Open the live connection-help page with your existing Vault:
indra --root "$indra_root" help
Set $indra_root to your existing Vault path as described in CLI commands. The command opens the page and prints its current URL. Keep the command running while you use it. If a browser did not open, open the printed URL yourself.
- Find the relevant app under Connect your apps or Review your connections.
- If an attempt already exists, use Continue connecting or Continue current authorization, as shown. Use Open authorization page when the card offers it.
- Complete the provider's account selection and sign-in. Check the account on that page; the helper does not have a universal account-picker control.
- Return to the connection-help page and inspect the result. Use Check again for a source that is already connected but still needs verification.
- Continue the original task once the source is usable. A successful empty read is a valid result; it does not require another sign-in.
If you know the source ID and want to open its supported sign-in flow directly, request the manual presentation. For an installed Gmail source:
indra --root "$indra_root" connect --source gmail --presentation open
Keep the command running while you finish the provider page and it checks the connection. The explicit presentation is useful when you are working without an agent; the automatic connection route can return browser work for an agent to continue. See Connect a service for other sources and setup requirements.
Some providers offer a QR-code page or a challenge on another device. Complete that specific step on the required device. The rest of your connected sources remain usable.
Understand what the page reports
| Observation | Meaning and next step |
|---|---|
| Actions are available; no action has run | The source exposes operations. Try the small read or operation needed for your task. |
| A read succeeded but no data is visible | The connection worked. Check account, scope, filters, and source coverage. |
| Settings saved; connection not verified | The setup information was stored. Complete the indicated check. |
| A sign-in or authorization step is active | Continue that transaction; do not start another in parallel. |
| Source unavailable or local setup required | Read the specific requirement and use connection recovery. |
The provider must verify access. An open browser, a completed consent click, or a sign-in success page alone does not prove that Indra can use the source.
Stop or return later
Cancel connection stops the active source transaction. Continue later closes the current help session; it does not erase completed connections. Read the page's resulting state before assuming a connection has stopped.
The help URL expires after 30 minutes or when its owner closes. If it has expired, run help again. Use the new returned URL rather than a bookmark from a finished transaction. recover also opens help without starting a new automatic setup pass:
indra --root "$indra_root" recover
Let your agent continue the sign-in
The agent should handle routine recoverable steps through available tools and preserve your account choice. It should ask for help only when a required step is unavailable to those tools, such as an inaccessible device challenge or missing credential.
The normal agent sequence is:
indra.manage({"what":"onboarding"})
indra.action({"name":"connector.connect","params":{"source":"<installed-source>","requestId":"<task-request-id>"}})
indra.action({"name":"connector.job","params":{"id":"<returned-job-id>"}})
Inspect the current state first. Continue a live existing job; do not create a second attempt merely because a wait ended. Keep the returned ID for subsequent connector.job calls.
If the result includes browserContinuation:
- Read
browserContinuation.sessionIdand observe that session withbrowser.observe. - Use the current controls for
browser.click,browser.type, andbrowser.scroll. Use a returnedinputNamewhen the value is already retained locally. - Continue checking the owning
connector.jobuntil provider verification settles. - Resume the original task with the verified connection.
These individual browser calls need no embedded-model API key. When a current recovery page is needed, connector.recover with params: {} returns it if assistance is required. Keep that MCP session alive while using the URL.
While a source has an active recovery transaction, direct source calls may be blocked. Continue through its existing owner and wait for it to settle. For the wider task's progress and cancellation boundaries, see Long-running work.