Skip to main content
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, JetBrains, and more.

​
Prerequisites

Python 3 and curl must be available on the device. The --api-key used here is a discovery key — separate from your login credentials. Get it from Connect → AI Coding Tools in the Unbound dashboard.

​
Run a scan

# Scan the current user only:
unbound discover --api-key <DISCOVERY_KEY>

# Scan all users on the device (requires root):
sudo unbound discover --api-key <DISCOVERY_KEY>

# Scan against a custom backend:
sudo unbound discover --api-key <DISCOVERY_KEY> --domain https://backend.acme.com

​
Schedule recurring scans (macOS)

Set up a LaunchAgent that runs a scan every 12 hours: 
unbound discover schedule --api-key <DISCOVERY_KEY>
Check schedule status and log paths: 
unbound discover status
Remove the schedule: 
unbound discover unschedule

​
One-step user onboarding

unbound onboard combines tool setup and discovery into a single command — useful for scripting new user enrollment: 
unbound onboard --api-key <USER_KEY> --discovery-key <DISCOVERY_KEY>
This runs setup --all (Cursor + Claude Code hooks + Codex hooks + Copilot hooks) and then performs a device scan.

​
MDM device onboarding (admin, requires root)

For fleet-wide enrollment from an MDM system: 
sudo unbound onboard --api-key <ADMIN_KEY> --discovery-key <DISCOVERY_KEY>
Scope is automatic: running unbound onboard with sudo configures every user on the device (MDM/org scope), while without sudo it sets up just the current user. Running with sudo also performs a full device scan (via sudo unbound setup --all) after enrolling all users.
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 currently supports macOS and Windows.
ToolPlatformAgentsMCP ServersRulesSkills
CursorWindows, macOS✅✅✅✅
Cursor CLIWindows, macOS✅✅✅—
Claude Code CLIWindows, macOS✅✅✅✅
Claude CoworkWindows, macOS✅——✅
GitHub CopilotWindows, macOS✅✅✅—
Gemini CLIWindows, macOS✅✅✅—
CodexWindows, macOS✅✅✅—
JetBrains IDEs (IntelliJ, PyCharm)Windows, macOS✅✅✅—
Junie (JetBrains)macOS✅✅✅—
Roo CodeWindows, macOS✅✅✅—
ClineWindows, macOS✅✅✅✅
WindsurfWindows, macOS✅✅✅—
Google AntigravityWindows, macOS✅✅✅—
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