Skip to main content

Changelog

Follow new updates and improvements to Swif.ai.

New: Monitor ChatGPT Desktop, Kilo Code, and OpenCode, with Full Session Details

Release Date: November 16, 2026
Category: Agentic Security

Swif's AI agent activity monitoring now covers three more AI agents: ChatGPT Desktop, Kilo Code, and OpenCode. For every AI agent session, you can now see what was asked, what the agent answered, and which tools it used.

What's New

Three More AI Agents

  • ChatGPT Desktop: chats and other work in the ChatGPT desktop app, on macOS and Windows. Coding work, in the app's project mode, the Codex command-line tool, or an IDE, is still reported as Codex, so you can tell the two apart.

  • Kilo Code: as a command-line tool, or as an extension in VS Code or Cursor, on macOS, Windows, and Linux.

  • OpenCode: versions 1.x and 2.3 or later, on macOS, Windows, and Linux. You can now choose it in the policy.

They join Claude Code, Codex, Cursor, Claude Desktop, Cline, Warp, and Hermes.

See Everything in a Session

Open a session to see:

  • Overview: the session ID, user, AI model, device, the project it worked in, and where its log is stored on the device.

  • Chat History: the messages between the user and the AI agent.

  • Tool Usage: each tool the agent used, such as shell commands, with what it did, and when.

Control the New Agents

  • Block ChatGPT Desktop separately from Codex. Allow one, and block the other.

  • Block Kilo Code, or only some of its tools, such as shell commands, through settings users can't change.

  • Blocking stays on. If a user removes the settings Swif uses to block an agent, Swif puts them back within a minute, and reports it.

Good to Know

  • Only the ChatGPT desktop app is monitored. Chats on chatgpt.com, or in the mobile app, aren't recorded.

  • Some tool details aren't available for ChatGPT Desktop sessions.

  • Requires Swif Agentic Security agent 1.51.0 or later.

Getting Started

  1. Open your Swif AI Agent Activity Monitoring Policy, and add chatgpt_desktop, kilo_code, or opencode to Monitored Agents. Or leave the list empty, to monitor every supported agent.

  2. To see sessions, go to Agentic Security > Devices, open a device, and go to Activity > AI Agent Sessions.

  3. Click a session for its details.

Learn More:


New

New: See and Control MCP Servers Across Your Fleet

Release Date: November 16, 2026
Category: Agentic Security

AI coding agents, such as Claude Code, Cursor, Codex, and Hermes, connect to tools and data through MCP servers. Each one an employee adds can run commands, or reach company data, and until now, you couldn't see which ones were in use. The new MCP Security page shows every MCP server on your devices, and lets you approve or block them in one click.

What's New

Every MCP Server, in One Place

  • New MCP Security page, under Agentic Security, with every MCP server found on your Macs, Windows, and Linux devices.

  • See who uses each one: its agents, how many devices and people have it, when it was last seen, and what your policy decides.

  • Filter by agent, or by decision.

Approve or Block in One Click

  • Approve or Block a server right from the list. Remote servers are added to your policy as hosts, and local ones as packages.

  • More than one policy? Choose which to change. The device's own policy is selected for you.

  • Devices pick up the change at their next check-in.

Find What Your Policy Would Block

  • New Violations tab: every server your policy blocked, or would block, for the last 30 days, or any dates you choose.

  • Click a violation to see the server, with the device already open.

Each Device's MCP Servers, and How They Changed

  • New MCP Servers tab on each device, under Activity: its policy, its agents, and any problems reading its settings.

  • Change History: when each server was added, changed, or removed, and by which agent.

Built to Keep Secrets Safe

  • Environment variables and headers show names only. Their values, such as API keys, are never collected or shown.

Good to Know

  • Not enforceable: Swif reports MCP servers in Claude Desktop and Codex, but can't block them. In block mode, they show as Not enforceable.

  • Managed in Claude: claude.ai connectors, such as Gmail or Notion, are set up in your Claude account, not on the device. They show as Managed in Claude, and never count as violations.

Getting Started

  1. If you haven't yet, create a Swif MCP Security Policy, and assign it to your devices.

  2. Go to Agentic Security > MCP Security. Devices report their MCP servers every 15 minutes.

  3. Review the Servers and Violations tabs, and approve or block servers as needed.

Learn More:


New

New: See Your Chromebooks in Swif

Release Date: November 17, 2026
Category: Device Management

Chromebooks are now part of your Swif device inventory. Connect your Google Workspace once, and Swif adds the Chromebooks from your Google Admin console, alongside your Macs, Windows, and Linux devices. Nothing to install on the Chromebooks.

What's New

Connect Once, Through Google Workspace

  • No app to install: Swif reads your Chromebooks from Google Workspace, using read-only access.

  • Connect from where you are: in Settings > Integrations, in Get Swif App, or in Device Inventory > Add Devices.

  • Guided setup: four steps walk you through connecting, and show Chromebook Integration Connected when you're done.

Every Device in One Inventory

  • Chromebooks in Device Inventory, with their serial number, name, and status.

  • Filter by ChromeOS, on its own, or with other operating systems.

  • Search by serial number, device name, or the user assigned in Google Admin.

The Details That Matter for Chromebooks

  • Who's using it: recent users, and how long it was used today.

  • Where it belongs: its organizational unit in Google Admin, and the notes, location, and asset ID your admins added there.

  • When it stops getting updates: its support end date, and license details.

  • Its health: boot mode, ChromeOS version, and firmware.

Good to Know

  • Read-only: Swif shows your Chromebooks, but doesn't change their settings. Keep using the Google Admin console to manage them, such as restarting, wiping, or updating ChromeOS.

  • More to come: more Chromebook details, and compliance rules for Chromebooks, are on the way.

Getting Started

  1. In Swif, go to Settings > Integrations, and open Chromebook.

  2. Click Connect, and sign in with your Google Workspace admin account.

  3. Allow read-only access to your ChromeOS devices.

  4. Find your Chromebooks in Device Inventory > Computers.

Learn More:


New

Earlier updates