Treat an assistant connection as delegated authority
Supported assistant integrations can use LeapTerm through MCP, a standard way for an assistant to request tools. The important user decision is not the protocol name: it is which files, devices and actions you authorize.
Use only an assistant and connection entry you recognize. Permission to read project files is different from permission to edit them or run commands. Keeping access beyond the current interaction is another deliberate choice.
Review a connection
- Sign in to the intended account and follow the supported assistant connection flow.
- Check the requesting assistant's identity, selected projects, requested permissions and expiry before authorizing it.
- Open Settings → Account & Sync → Connected assistants and choose View connected assistants where available.
- Confirm that the listed assistant, project count, permission labels and expiry match your intention.
- Refresh the list when checking a recent change.
Permissions can include View devices, Read files and Git state, Edit files and Git state, Run commands and tests, and Keep access until expiry or revocation. Grant only what the task needs. Do not assume a read permission also authorizes a write, or that closing a chat necessarily revokes persistent access.
Use interactive views and file results
Some integrations offer interactive file previews, settings, work results, plans or continuation controls. Your assistant host must support LeapTerm's separately hosted views and connect them to its authenticated tools. Hosts that require an inline view document from the API need a compatible integration before they can render these views. Check the supported integration instructions; a successful tool connection alone does not confirm interactive-view compatibility.
Opening a view's static link by itself does not connect its controls to your assistant. When a tool returns a downloadable file or result, use the supported integration's separate authenticated delivery link. Retrieval still requires the current assistant connection, project access and relevant permissions. Treat file and result links as private.
In-app browser tool access with MCP
Where the browser helper and an explicit browser agent grant are configured, omniterm-browser-mcp lets an assistant inspect and operate the granted live pages. The browser grant determines the pages, allowed actions and expiry; an account assistant connection or a copied page reference alone does not authorize browser control.
The tools include browser_console_and_network for bounded diagnostics, browser_take_snapshot for page text and controls, browser_take_screenshot for an image, and browser_click and browser_type for interaction. browser_resume_page resumes the exact authorized live page without reloading it. If the page or runtime has disappeared, open a new page explicitly; a saved URL does not restore the old page's state.
For protected saved pages, Continue from here requires the original trusted customer agent, an independently enrolled installed client and unlocked custody. A browser workspace can display saved page metadata, but that metadata does not grant protected continuation through a cloud Gateway.
Review assistant tool invocations and verify sensitive URLs before automated interactions. During AI browser activity, the browser surface offers Pause, Stop and Take over control; Resume explicitly permits AI activity again. These controls block subsequent agent operations while paused, stopped or taken over, and do not undo work already completed.
Disconnect when finished
Use the assistant's disconnect control and check the result. If the app reports that revocation is not confirmed, treat access as unresolved until you can verify it. A failed refresh does not prove the connection no longer exists.
Revocation affects future authorized access; it cannot retract files already read, erase provider copies, or undo prior commands. Review the assistant provider's handling of the material you allow it to receive.
Read agents and tasks for supervising execution, and account security for reviewing signed-in devices separately from assistant permissions.