unbound discover scans a device for installed AI coding tools and reports findings to Unbound. This powers the AI Tools inventory and fleet visibility in the dashboard.
Tools detected: Cursor, Claude Code, Gemini CLI, Codex, Windsurf, Roo Code, Cline, GitHub Copilot, Augment Code, JetBrains, and more.
Prerequisites
Python 3 must be available on the device — the installer acceptspython3, python, or py -3 on Windows. It downloads its files with Git when Git is available; the fallback needs curl and tar on macOS and Linux, and nothing extra on Windows.
Which key you pass to --api-key depends on the scan’s scope:
- Single-user scan (no
sudo) — use your own user API key. - All-users scan (with
sudo) — use your admin API key. The device is attributed to its owner automatically (resolved from the hardware serial); no separate discovery key is needed.
Run a scan
Schedule recurring scans
Keep the device’s inventory current without re-running scans by hand:discover status reads launchctl state, so it only works on macOS. On other platforms it exits with an error naming the equivalent command:- Linux —
systemctl --user status unbound-scheduled.timer - Windows —
Get-ScheduledTask -TaskName "ai.getunbound.scheduled"
One-step user onboarding
unbound onboard combines tool setup and discovery into a single command — useful for scripting new user enrollment:
sudo the bundle is Cursor, Claude Code hooks, Codex hooks, Copilot hooks and Augment hooks; with sudo it additionally includes Gemini CLI.
Onboard flags
MDM device onboarding (admin, requires root)
For fleet-wide enrollment from an MDM system:unbound onboard with sudo configures every user on the device (MDM/org scope), while without sudo it sets up just the current user. Either way the command finishes with a device scan: under sudo it scans every user on the device, without sudo just the current user.
See MDM Integrations for deployment guides and MDM-specific configuration.
Supported AI coding tools
Unbound gives security teams visibility into the AI coding tools your developers use — the agents themselves, the MCP servers they connect to, the rules files that steer them, and the skills they’ve installed. The matrix below summarizes coverage across the most common tools in the ecosystem today.Coverage continues to evolve alongside the AI tooling ecosystem. Specific feature behavior may vary by tool version and deployment configuration. Discovery supports macOS, Windows, and Linux.
Agents — Detect installations of the AI coding tool.
MCP Servers — Surface the MCP server connections each tool has configured.
Rules — Capture the custom instruction and rules files each tool loads (e.g.
.cursorrules, CLAUDE.md, GEMINI.md, .windsurfrules).
Skills — A SKILL.md file of instructions that an agent adds to its toolkit and uses when relevant to extend what it can do.
MDM Integrations
Connect your MDM provider and deploy AI tools at scale
Analytics
View discovered tools and fleet activity in the dashboard

