Ask a teammate’s agent
Open the thread’s Access → Agents. Choose an agent and the affected phase, then send a suggestion, request a change or pause shared work. GRID records your identity separately from the agent’s owner. Owner instructions have priority; requests that need approval wait for that owner.
Find live and earlier work
An Agent work control appears beside a Flowboard or Flowdoc while an agent is active there. Open it to see its task, exchange messages and locate the work. Guests do not receive agent controls. Use Agent Monitor → Work for live tasks and Recorded work for earlier activity. Removing a connection preserves captured records, subject to your current project and phase access.
Review a change
An owner notification opens Agent Monitor → Work → Pending approvals. Compare Before and After, then approve or reject the specific proposal. Changes to its target, access or instructions can invalidate approval. Legacy text proposals replace one plain-text span at a time. Native document actions, when enabled, can update complete formatted content through the same editor checks used for human changes. Unsupported edits are rejected before review. Frozen evidence cannot be edited; duplicate it using the normal workspace controls to continue.
Captured activity and original inputs
Open Captured activity → Agent activity. Search or filter by date, then open a record to see the available original changes, errors, outputs and timestamps. Original inputs load only when opened. If no excerpts were supplied, GRID cannot display code or output that was never sent. There is no separate Review tab in Agent Monitor; consequential decisions remain under Work → Pending approvals.
The same evidence policy
Captured reports and applied edits have a fixed six-hour review window from server receipt. They lock and enter the existing processing schedule automatically. Exclude unwanted activity before the deadline, or choose Lock now to finish review early. Locking never restarts the clock.
What the record proves
GRID-applied changes are marked Recorded by GRID. External execution reports are marked Reported by agent; the connector does not independently prove a test passed. Expand Original activity for available changes, errors, outputs and timestamps. Unsupported local capture is not silently invented.
People, presence and questions
On a permitted board, an agent can see who is in a Flow Room. It can address a clarification to that person in its permitted shared work task, and the person can reply or interrupt beside the artifact or through Agent Monitor. Presence does not grant new project access, room entry or private messaging, and does not guarantee a response. The external agent decides when to ask; GRID supplies the tools, identity and communication rules.
Assets and project context
Agents are not limited to workflow steps. With delegated read permission they can discover accessible board assets by category, including images, text, code, groups, links and documents, and read the corresponding permitted source. Supported uploads, copies and edits also require the relevant rights and source checks. An asset reference never grants access to an unrelated board, private phase or document. GRID does not run the external agent or charge a model call just to list these tools.
Flowboards and Flowdocs
Native tools use current artifact permissions and editor checks. Stale edits must be reconciled rather than overwrite newer work; a card being edited by a person can temporarily reject a conflicting agent edit. Agent-created content has an agent mark under its responsible person. Verified human changes can make authorship mixed; instructions and approvals alone do not convert agent execution into human execution. Personal boards and documents move to the recoverable Bin where permitted. Card/connector recovery is limited and is not full seven-day board version history.
Work understanding
Eligible records feed work understanding, contributor explanations, phase summaries and thread summaries. The responsible person, executing agent and verified human requests remain separate. Approval alone does not prove substantive technical review. Skills are not assessed or suggested.
Disconnects and pending work
Committed changes survive a disconnect. The downloaded local bridge durably queues supported outgoing mutations across restarts; keep its private outbox and configuration. Remote HTTP clients need their own retry/receipt handling. Retrying an uncertain operation uses the same operation ID; changed content requires a new one. Revocation still blocks replay. Stale edits are rejected and human drafts are preserved for reconciliation. Budget limits, access changes or unavailable processing can delay understanding without deleting the underlying evidence.
Waiting is different from completed
An assistant can finish its current chat turn while a shared task is still waiting for owner review. Current pending or approved-but-unsaved proposals keep the task from completing. Old revision approvals cannot save changed work. Review the refreshed proposal and invoke the assistant again when your client is not running in the background.
Supported work and current limits
Connected agents can read permitted context and existing phase-linked text/code cards and Flowdocs. They can propose text-span changes and create, move or connect text/code cards inside an existing group. These are the legacy proposal tools. With native work enabled and explicit owner permission, agents can also create/update threads and phases, boards, formatted documents, cards, comments, resources and posts, and move recoverable work to Bin. Sharing and major changes require exact approval. Agents cannot delete a thread or phase, permanently purge, delete a repository, enter Flow Rooms or access Circle. Agents can see who is present on a permitted board, but cannot read room chat or media. Questions use the shared task beside the work, not the room conversation. PCLink is not enabled. Multiple agents may exchange scoped suggestions only when both owners allow it. External reports remain reports; GRID does not certify an unobserved test.