Skip to the content

Watch what agents can capture

See which agents can capture your Mac's screen, and alert, pause or end a task when a password manager or other sensitive app comes to the front.

Built, not yet claimed preview: this guide describes a package that has not passed its release gate.

Know which of your agents can capture the screen, by the computer-use posture or by a Screen Recording grant, and choose what happens when a password manager, Keychain Access, System Settings or an app you name comes to the front while one runs: an alert, a pause until the app leaves, or the end of the task. macOS only.

1. Know what the monitor can and can't see

The capture monitor knows which tasks can capture the screen, never whether one is capturing: macOS shows no other process's capture, and AgentGarm never reads a frame. A task can capture when it runs in the computer-use posture, or when the agent, or the terminal or editor it runs in, holds the Screen Recording grant. AgentGarm learns of grants from its Endpoint Security client, which reads the system's privacy database; an install without it, such as a tarball install, knows only the first kind.

A launched agent left contained cannot capture at all, which the sandbox enforces (B). Everything the monitor does after that rates C: it reacts to a change after it happens, so its fail mode is fail_open_alert. Built for macOS only, and not yet claimed; no CI walk runs these steps.

See also

Govern computer-use agents

Let an agent drive your Mac's mouse and keyboard while AgentGarm's airbag drops its input on password managers, settings and other protected targets.

2. See which agents hold a grant

Every change to a governed task's Screen Recording, Accessibility, input-monitoring or input-posting grant is recorded for the task and shown as an alert in the dashboard. A grant to the terminal or editor an agent runs in counts as the agent's, since what it runs inherits it. If AgentGarm cannot read the privacy database (no Full Disk Access for its Endpoint Security client, or a layout it does not know), it reports no grants rather than guessing, and logs that once.

agentgarm ui --open

3. Name your sensitive apps

The catalog names Keychain Access, Passwords, System Settings and Bitwarden. Add your own with extra_sensitive, by bundle id, under security_boundaries.desktop.capture. While a task that can capture runs, the airbag tells agentgarmd only when an app on this list comes to the front or leaves it, and never names any other app. A sensitive website in a browser is not an app, so it is not covered. Restart agentgarmd after editing the policy: it reads policies only when it starts.

security_boundaries:
  desktop:
    posture: computer_use
    capture:
      # When a sensitive app comes to the front while this agent can capture:
      # alert (the default: record it), pause (stop the task until the app
      # leaves) or kill (end the task). pause and kill need `agentgarm run`.
      on_sensitive_frontmost: pause
      # Your own sensitive apps, on top of the catalog's.
      extra_sensitive: [com.example.payroll, com.example.hr-portal]

See also

Govern computer-use agents

Let an agent drive your Mac's mouse and keyboard while AgentGarm's airbag drops its input on password managers, settings and other protected targets.

4. Choose alert, pause or kill

on_sensitive_frontmost applies once each time a sensitive app comes to the front. alert (the default) records it. pause stops the task, its processes and everything they started, until the app leaves the front, and denies whatever it asks for meanwhile; the task runs again only if nothing else holds it. kill ends the task.

pause and kill need a task launched with agentgarm run; for a hooks-only agent they stay alert. In mode: audit both only record. The pause comes after the change, so a frame taken in that moment is not stopped.

A paused task shows its sensitive_frontmost hold in agentgarm status. Root can remove it by hand with sudo agentgarm task resume, the task's id and --hold sensitive_frontmost; the task runs again only once no other hold, such as a kill order's, is left. Resume is not built on Windows yet.

agentgarm status
An agent that can record the screen, flagged and paused while a password manager is in front, with the notice that says so

See also

Find out why your agent stopped

Tell whether your agent was suspended, killed, locked out by a kill order or stopped by its budget, get your work back, and find out who can lift it.

5. Read a capture alert

In the dashboard, a capture alert is titled by what happened, such as "Sensitive app in front during capture: task paused", with the app as its detail and the task it belongs to. With the presence menu or agentgarm notices running, it also arrives as a notification that names what happened but not the app. Under the non_monitoring compliance profile the app is left out of the record too.

agentgarm ui --open
agentgarm notices

See also

Prepare a works-council or DPIA pack

Generate templates that describe what your deployment collects, keeps and sends, and switch the fleet to the non-monitoring profile during talks.

6. Limit grants in System Settings, or with an MDM

The surest control is fewer grants. In System Settings, Privacy & Security, Screen & System Audio Recording, turn off every app that does not need it, terminals and editors that run agents first, since an agent inherits their grant. On a managed Mac, a privacy preferences (PPPC) profile from your MDM can deny Screen Recording to an app; macOS lets no profile grant it without the person allowing it.

7. Know what still leaves the machine

A computer-use agent sends its screenshots to its model provider, as images in its requests, whatever this monitor does. AgentGarm's redaction finds secrets in text, not in pictures, so anything on screen while the agent takes a screenshot may reach the provider. Keep sensitive apps closed, or use pause, while such an agent runs.

See also

Keep secrets and card numbers out of prompts

See which credentials your agent sends its model provider, have the proxy replace them with cache-safe placeholders, and deny tool calls that carry one.