# Devices
The **Devices** page provides an inventory of all developer machines where the Dev Machine Guard script has been deployed and executed.
Each device represents a unique developer machine and serves as the entry point for understanding local development environment activity.
### Device List
At the top of the page, summary chips show:
* **Active**: total number of devices currently reporting
* Per-OS counts for **macOS**, **Windows**, and **Linux**
You can filter the list using:
* **Search devices**: free-text search by device name
* **All users**: filter by associated user
* **All agent versions**: filter by the version of the Dev Machine Guard agent installed on the device
The device table shows the following columns:
| Column | Description |
| ------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Device** | Device hostname, associated user, and OS version. Below the name, inline counts summarize detected assets: IDE extensions, npm packages, AI agents, MCP servers, and system packages. |
| **Status** | Current device status (for example, `Active`). |
| **Last Scan** | The result of the most recent script execution (`Succeeded` or `Failed`) and how long ago it ran. |
| **Assets** | Total number of assets detected on the device across all categories. |
| **Last Seen** | When the device last reported telemetry to StepSecurity. |
This view helps you quickly understand which machines are actively reporting data, what they have installed, and how recently they were scanned.
### Device Details
Selecting a device opens a detailed view with system and agent information for that machine.
The **Device Information** block shows:
* **Device ID**: unique identifier assigned by Dev Machine Guard
* **User**: the user associated with the device
* **Platform**: the OS platform (for example, `darwin`, `linux`, `windows`)
* **OS Version**: the specific OS version reported by the device
* **Agent Version**: the version of the Dev Machine Guard script installed on the device
* **Status**: current device status
* **Last Scan**: timestamp of the most recent successful scan
* **Scan Frequency**: how often the script is configured to run (for example, `Every 4 hours`). Scan frequency is set globally for your organization and applies uniformly to all devices.
* **npm Packages**: total and unique npm package counts detected on the device
* **First Seen** / **Last Seen**: when the device first reported and most recently reported telemetry
Below the information block, the side panel includes collapsible sections for the assets detected on the device.
#### **IDE Extensions**
The IDE Extensions section provides a consolidated view of all extensions detected across the [supported IDEs](broken://pages/GtCKhaNSPZKc2Y1ZVtKW#supported-ides) on the device.
The section header shows the total number of extensions installed. Expanding the section displays the per-extension breakdown, including the IDE each extension belongs to.
This view helps you:
* Identify the overall extension footprint on the device
* Detect duplicate or overlapping extensions
* Spot potentially risky or unexpected extensions
* Understand extension usage across different IDEs
By consolidating extension data across IDEs, this section provides a unified view of the developer tooling surface area on the machine.
#### **AI Agents**
The AI Agents section displays all AI-powered development tools detected on the device.
The section header shows the total number of agents installed. Expanding the section reveals per-agent details:
* Agent name
* Vendor or provider (for example, Anthropic, OpenAI, Google)
* Agent type (`CLI Tool`, `Agent`, or `Framework`)
* Installed version
* Executable or command name where applicable
This provides visibility into AI tools installed via CLI, IDE integrations, or standalone agents, and helps you:
* Identify which AI tools are installed on developer machines
* Track versions for governance and upgrade management
* Detect unapproved or unexpected AI tools
* Understand whether agents are CLI-based, general-purpose, or framework runtimes
#### **MCP Servers**
The MCP Servers section shows all Model Context Protocol (MCP) servers configured on the device.
The section header shows the total number of MCP servers configured. Expanding the section displays per-server details:
* Server name
* Transport type (for example, `local`)
* Config source (the tool that registered the server, for example `cursor`, `antigravity`, `windsurf`)
This helps you:
* Identify external integrations accessible to AI agents on the device
* Detect duplicate or redundant MCP configurations
* Validate that only approved MCP servers are configured
* Reduce the risk of unintended data exposure through AI tool extensions
#### Recent script executions
The **Recent Script Executions** section shows logs from recent runs of the Dev Machine Guard script on the device.
This is primarily intended for debugging and operational visibility, and lets you confirm that the script is running on schedule and reporting telemetry as expected.
---
# Agent Instructions: Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter:
```
GET https://docs.stepsecurity.io/developer-machines/devices.md?ask=
```
The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.