Where Agent work runs
RunMat Agent can connect an AI coding client to different project and execution boundaries. Confirm the active boundary before granting tools or sharing sensitive context.
| Connection | Project files | Code execution | Runtime context |
|---|---|---|---|
| Desktop project | Local or cloud project open in Desktop | Runtime attached to Desktop, subject to capability and approval | Live workspace, figures, and history when enabled |
| Agent CLI / local MCP | Authorized local project scope | Local command or Runtime tools allowed by configuration | Tool-specific local context |
An AI model may be provided by a separate vendor even when tools run locally. Tool execution location and model-processing location are distinct data boundaries; review both providers' configuration and policy.
Use Desktop attachment when the task depends on a local folder, local hardware, or the live interactive session. Use local CLI integration for headless or editor-driven workflows where you control the process and filesystem scope.
Inspect the connection status and target shown by the client to confirm which project and runtime a tool call uses.