> For the complete documentation index, see [llms.txt](https://docs.stepsecurity.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.stepsecurity.io/developer-machines/devices.md).

# Devices

The **Devices** page provides an inventory of all developer machines where the Dev Machine Guard 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

<figure><img src="https://754495266-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FQJRZY4cfEeY3I7DXTOCp%2Fuploads%2FCwwTBsyJWAcYn7UHp4C7%2FScreenshot%202026-04-30%20at%2011.17.13.png?alt=media&amp;token=7fe9da8a-d5e3-4785-864c-35353903fa77" alt=""><figcaption></figcaption></figure>

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.

<figure><img src="https://754495266-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FQJRZY4cfEeY3I7DXTOCp%2Fuploads%2FRhe4Q2JDtVXNnz0Mu3b2%2FScreenshot%202026-04-30%20at%2011.17.38.png?alt=media&amp;token=53a5d0a0-9341-4456-b851-8d57d8b49d9a" alt=""><figcaption></figcaption></figure>

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 agent binary installed on the device
* **Status**: current device status
* **Last Scan**: timestamp of the most recent successful scan
* **Scan Frequency**: how often the device runs a full scan (for example, `Every 4 hours`). This is the organization-wide interval configured under [Settings](https://docs.stepsecurity.io/developer-machines/installation/settings.md). It applies to every device running agent 1.15.0 or later; devices on earlier agent versions ignore the interval and scan on every launch.
* **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](https://docs.stepsecurity.io/developer-machines/ide-and-ai-agents/ide-extensions.md#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 lists recent Dev Machine Guard agent activity on the device. Use it to confirm that the agent checks in on the schedule you expect, to review what each scan did, and to troubleshoot a device that is not reporting as expected.

<figure><img src="https://754495266-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FQJRZY4cfEeY3I7DXTOCp%2Fuploads%2FHWNDmxRPTCK2YUJmXJ09%2Fimage%20(159).png?alt=media&amp;token=0ed454ea-a30f-4937-9d79-16b5d3dd0944" alt=""><figcaption></figcaption></figure>

The section header shows the number of executions and a count of executions by result. Use the arrow on the right to expand or collapse the section.

The list contains two kinds of entries:

* **Scans:** the agent ran a full scan and reported telemetry to StepSecurity.
* **Gated check-ins:** the agent checked in with StepSecurity, found that a scan was not yet due, and exited without scanning.

#### **Gated check-ins**

Agents check in with StepSecurity each time they launch. How often that happens depends on the frequency you set in your MDM tool or scheduled task. At each check-in, the agent runs a full scan only when one is due under your organization's [Scan Schedule](https://docs.stepsecurity.io/developer-machines/installation/settings.md#scan-schedule).&#x20;

Each check-in that does not lead to a scan is recorded as a gated check-in, so you can see that the agent is running on the device between scans.

A gated check-in shows:

* The date and time of the check-in, with a `Skipped` status.
* **Reason:** why the agent did not scan. `not_due` means the scan interval has not yet elapsed since the device's last full scan.
* **next scan:** when the device becomes due for its next full scan.
* **Dev Machine Guard:** the agent version installed on the device.

Gated check-ins are hidden by default, so the list shows only scans. To include them, select **Show gated check-ins** at the top of the section. The button then changes to **Hide gated check-ins**, which you can select to return to the scans-only view.

{% hint style="info" %}
A gated check-in is recorded only when the agent reaches StepSecurity. If a device cannot reach StepSecurity, the agent uses the last scan interval it received and records no check-in until it reconnects. Agents older than **1.15.0** do not follow the Scan Schedule and scan on every launch, so they never record gated check-ins.&#x20;
{% endhint %}

#### **Scan details**

<figure><img src="https://754495266-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FQJRZY4cfEeY3I7DXTOCp%2Fuploads%2FtcWJG441arUzcKOOXVO0%2Fimage%20(158).png?alt=media&amp;token=0d687176-4c13-41da-85d5-e5fe88cfecd8" alt=""><figcaption></figcaption></figure>

A scan entry shows:

* The date and time of the scan, with its result (for example, `Succeeded`).
* How the scan was started (for example, `Manual`).
* **Duration:** how long the full scan took.
* **Dev Machine Guard:** the agent version that ran the scan.
* **Log Size:** the size of the execution log for the run.
* **Download Logs:** downloads the full execution log for the run.

Expand **phases completed** to see each phase of the scan. A phase is one stage of the scan, such as `device_info`, `extension_scan`, `ai_tools_scan`, `mcp_config_scan`, `python_scan`, or `node_scan`. Each phase shows its status and how long it took.

The phases a scan runs depend on the device's operating system and your organization's settings, so the number of phases can differ between devices.

Use the phase list to:

* Confirm that every part of the scan ran.
* Find the phase that failed or took the longest when a scan fails or runs slowly.
* Give StepSecurity support precise details, together with the downloaded log, when you raise an issue.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.stepsecurity.io/developer-machines/devices.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.
