The Swif AI Agent Activity Monitoring Policy records the sessions and tool activity of AI coding agents on managed macOS, Windows, and Linux devices, so admins can review what each agent did.

This policy was previously called the Swif ADR Sensor Policy.

It uses the open-source Uber Agentic Detection and Response (ADR) Sensor. The sensor reads the local logs that supported AI agents write, converts the activity into a common format, and uploads it to Swif. Use it to:

Important: This policy collects sensitive data. Session records can include prompts, responses, project paths, tool arguments and results, usernames, and hostnames. Review Privacy and security considerations below and inform affected users before you turn it on.

Activity monitoring itself doesn't block anything. With Agent Access set to block, the policy also blocks agents and tools you don't allow, in Claude Code, Codex, and Cursor. To block destructive commands, use the Swif AI Agent Command Protection Policy.

If you turn on Enabled and keep the other defaults, the device collects from all supported agents every 15 minutes, includes up to 14 days of history, and uploads it to Swif. Risk detection stays off.

Agents that aren't available on a device's operating system are skipped. Hermes needs a Swif agent version with the new activity monitoring runtime, and isn't yet supported on Windows.

Leaving Monitored Agents empty collects from every supported agent. It also includes opencode, which isn't available as a separate option. To limit collection, list only the agents your organization has approved.

Collection timing depends on the agent version:

On any version, a policy change can take up to 20 minutes to reach the device.

What's collected depends on the AI agent, its version, and what it records locally. It can include:

The sensor only reads what the agent already logged. It can't collect activity the agent didn't record, or sessions the agent or user has deleted.

When Risk Detection Enabled is on, Swif analyzes each uploaded session for:

Each analyzed session gets a finding:

Risk detection sends full sessions to an external AI provider. To score a session, Swif sends the full session, including prompts, responses, and tool inputs and outputs, to an approved external LLM provider. Analysis runs on Swif's servers, never on the device. Findings contain only the verdict, summary, and reasons, not transcripts or tool output, and paths and secrets are redacted from the summary.

Shadow AI is AI agents or tools that employees use without your organization's approval. They can read code, run commands, and send data to outside services, with no oversight. Agent Access lets you decide which AI agents, and which of their tools, may be used on your devices.

Start with report. Review what your teams use, adjust your lists, then switch to block.

Up to 32 agents. Use these values:

Allowlist or denylist?

Allow or deny specific built-in tools, for one agent, or for every agent. Each rule has:

You can add up to 32 tool rules: one per agent, plus one * rule for all other agents. A policy can't have two rules for the same agent, or two * rules.

Swif checks the policy when you save it. If something is invalid, such as an unsupported tool name, the save fails, and the error names the field.

Codex web search isn't visible to Swif, so it can't be reported or blocked.

Each shadow AI event records the device, its operating system, and the user. It also records the agent and tool, whether the use was blocked or reported, the reason (agent not allowed, or tool not allowed), how it was detected (hook, session, or inventory), the session ID, and the policy version that applied.

You can filter events by device, user, agent, tool, decision, reason, detection source, and date range, and group them into reports by any of these, or by day. Events are kept for 90 days.

Each agent on a device also has its own state: enforcing, reporting, report only, hook missing, or not installed.

Expand to more devices after the pilot and your privacy, security, and legal reviews are complete.

An explicit agent list and a 7-day window keep collection small, while giving enough recent activity to validate the policy.

Activity is collected but stays on the device. Use this during a technical or privacy evaluation. Sessions won't appear in Swif until you turn on upload.

Collect the most history as often as possible. Return to the default interval and a shorter window when the investigation ends.

Every other agent your teams use is reported as shadow AI, so you can see what's in use before you block anything.

Only Claude Code and Codex may be used. Other agents are blocked where possible, and reported otherwise. Neither approved agent can use web fetch or web search, except Codex web search, which Swif can't see.

Use a test session that contains no credentials, customer data, or proprietary code.

If the policy is active but no sessions have been collected yet, the list is empty.

Click a session to open its details.

Chat History (shown first) lists the messages between the user and the AI agent, labeled User and Assistant.

Tool Usage lists the tools, commands, arguments, times, and results from the session.

Each tab can show:

The policy doesn't change the AI agents' own logging or privacy settings. Review each agent's storage, cloud processing, and retention separately.

The ADR Sensor is open source under the Apache License 2.0. Review its source code and release history as part of your software supply-chain process.

Turning off the policy doesn't delete:

Follow your retention and deletion procedures for each location.

Increase History Window (Days), up to 30. Also check that the AI agent still has the session locally. The sensor can't collect a session after its records are deleted.

If the device was offline, wait for it to reconnect and complete another collection.

The device runs Swif agent 1.27.0 or earlier, where intervals under 20 minutes effectively run every 20 minutes. Update the agent to 1.28.0 or later.

The agent, or one of its tools, isn't allowed by Agent Access. If it should be allowed, add it to your allowlist, or remove it from your denylist.

Agent Access sees these agents only through the agent inventory. Check that the Swif Agent Inventory Policy is assigned to the same device, enabled, and has the agent in its Agents list.

This is expected. Hermes session monitoring isn't yet supported on Windows.

This is expected. They run on Cursor's servers, so Swif can only report them.

This is expected. Swif can't see Codex web search, so it can't report or block it.

Swif

Uber ADR