Connect
Open Agent Monitor → Connect agent. Name the connection, choose permitted threads, then select View context or Work here. View context cannot change your work. On deployments with native work enabled, choose the agent’s read, edit, publish and recoverable-delete permissions and whether personal work is included. Routine permitted edits apply directly. Sharing and major changes still need exact owner approval. Older connections retain their proposal-only access until you explicitly change it. Connecting does not start the external assistant.
In another app
Copy the one-time configuration into a client that supports remote MCP with a bearer header. Keep the key private and out of shared project files. OAuth-only clients need a separate integration and are not supported by this connection method.
On this device
Choose On this device in the setup window. Download the local bridge, enter its full location and copy the generated local MCP configuration. Node.js 22 or newer and a network connection to GRID are required. The bridge does not install IDE capture or grant access to your local files.
Organization-owned work
The organization must enable connected agents in its own Settings first. Only its direct organization login can change that policy. Membership and individual agent permissions still apply; personal-owned work is unaffected.
Choose the phase
The agent reads authorized context. With native work enabled it can work in a permitted personal workspace, thread or phase, and create supported work without a required template. It can page through older permitted evidence and inspect explicitly linked text/code cards or Flowdocs. The connector omits unavailable private-phase history and blended profile/institution summaries; it reads currently permitted artifacts explicitly. Scope does not grant access to unrelated projects, Circles or Flow Room conversations/media. Presence alone is available on a permitted board.
Pause, reconnect or revoke
Pause access blocks GRID calls; it does not stop a process on another device. Reconnect replaces the key. Edit access changes delegated threads/actions and invalidates previous runs and approvals. Revocation prevents future GRID access; previously delivered context cannot be recalled. Remove hides the connection and revokes its access without removing recorded work or locked evidence. A revoked connection cannot reconnect using its old key.
Confirm the connection
Open or reload the assistant in its own app and ask it to check its GRID connection. Then refresh Agent Monitor. Last connected confirms that the client reached GRID; it does not prove a task is running or a result is correct. A missing key, unsupported transport or client tool-consent prompt can prevent this first connection.
Your first shared task
Start with an existing thread, phase and linked Flowboard or Flowdoc. A text/code card should be inside one group so its exact work can be preserved as evidence.
- Choose Work here when connecting if the assistant should contribute. Routine native edits use the explicit rights you delegate; consequential changes need exact approval. Keep only the intended thread selected.
- In Agent Monitor → Work, choose the thread, open Assign work, select your assistant and phase, and describe the result you want. You can also assign from Agent work beside a linked artifact.
- Invoke the assistant in its external app and ask it to check its GRID inbox. An on-demand chat app may need another message to continue; GRID does not make it always active.
- Watch the task beside the work. Queued means GRID saved a message; Received means the client acknowledged receipt. Neither proves it understood or finished.
- Open Work → Pending approvals, inspect the exact Before and After, then approve or reject. Ask the external assistant to continue if it is not already running. Revisions and changed instructions can require a fresh proposal.
Codex and other client formats
In the setup window choose MCP JSON for compatible JSON-based clients, or Codex (config.toml) for the Codex app/CLI. Save credentials only in your private client settings, not a shared repository or chat prompt. Reload the client after setup and allow its normal tool-consent prompt. Do not disable its security controls. The available connection is bearer-authenticated HTTP or the local stdio bridge, not OAuth-only browser sign-in. Codex was tested; other clients need their supported transport checked.