Treat an assistant connection as delegated authority
Supported assistant integrations can use OmniTerm 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 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.
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.