> 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/ide-and-ai-agents/coding-tools.md).

# Coding Tools

The Coding Tools page provides a centralized, organization-wide view of all AI agents detected across developer machines.\
This page helps security and platform teams understand which AI tools are being used, who is using them, and how widely they are deployed.

<figure><img src="https://754495266-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FQJRZY4cfEeY3I7DXTOCp%2Fuploads%2FtCiKqGRcAo6JowOOZvsk%2FScreenshot%202026-08-26%20at%2023.26.46.png?alt=media&amp;token=a8b4ff57-c4ff-4156-ae74-9dac30706345" alt=""><figcaption></figcaption></figure>

Filter chips let you scope the list by agent category:

* **CLI Tools**: command-line AI coding assistants (for example, Claude Code, Codex)
* **Frameworks**: local AI runtimes and inference frameworks (for example, Ollama)
* **Agents**: general-purpose and IDE-integrated AI agents

Each chip shows the number of unique items detected in that category.

You can search the list by agent name or vendor, and use **Export CSV** to download the full agent inventory.

The agent table shows the following columns:

* **Agent**: the agent name and a category badge (`CLI Tool`, `Agent`, or `Framework`)
* **Vendor**: the publisher or origin (for example, Anthropic, OpenAI, Google, Cursor, OpenSource)
* **Devices**: the number of devices where the agent is installed

### Supported AI Agents

StepSecurity Dev Machine Guard automatically detects the following AI agents and tools installed on developer machines.

#### **IDE & Desktop Apps**

| Agent                  | Vendor             |
| ---------------------- | ------------------ |
| Visual Studio Code     | Microsoft          |
| Cursor                 | Cursor             |
| Windsurf               | Codeium            |
| Antigravity            | Google             |
| Kiro                   | Amazon             |
| Zed                    | Zed                |
| Claude Desktop         | Anthropic          |
| Microsoft Copilot      | Microsoft          |
| IntelliJ IDEA Ultimate | JetBrains          |
| IntelliJ IDEA CE       | JetBrains          |
| PyCharm Professional   | JetBrains          |
| PyCharm CE             | JetBrains          |
| WebStorm               | JetBrains          |
| GoLand                 | JetBrains          |
| PhpStorm               | JetBrains          |
| CLion                  | JetBrains          |
| Rider                  | JetBrains          |
| RubyMine               | JetBrains          |
| DataGrip               | JetBrains          |
| Fleet                  | JetBrains          |
| Android Studio         | Google             |
| Eclipse IDE            | Eclipse Foundation |

Kiro is detected at its standard install location on each platform: `/Applications/Kiro.app` on macOS, `%LOCALAPPDATA%\Programs\Kiro` on Windows, and `/usr/share/kiro` on Linux.

#### **AI CLI Tools**

| Agent               | Vendor        |
| ------------------- | ------------- |
| Claude Code         | Anthropic     |
| Codex               | OpenAI        |
| Gemini CLI          | Google        |
| Amazon Q / Kiro CLI | Amazon        |
| GitHub Copilot CLI  | Microsoft     |
| Microsoft AI Shell  | Microsoft     |
| Aider               | Open Source   |
| OpenCode            | Open Source   |
| Cursor Agent        | Cursor        |
| Pi                  | Earendil      |
| Factory Droid       | Factory       |
| Amp                 | Sourcegraph   |
| Grok Build          | xAI           |
| Kimi Code           | Moonshot      |
| Muse Code           | Meta          |
| Hermes Agent        | Nous Research |
| Oh My Pi            | Stencil       |

{% hint style="info" %}
Pi, Factory Droid, Amp, Grok Build, Kimi Code, Muse Code, Hermes Agent, and Oh My Pi share their command names with unrelated tools, so a matching binary on the `PATH` is not enough. Each is confirmed from on-disk installation evidence, such as a package manifest or the vendor's install directory, before it is reported. None of these tools is launched to read its version, and their configuration, authentication, session, and log files are never read.
{% endhint %}

#### General-Purpose AI Agents

| Agent         | Vendor      |
| ------------- | ----------- |
| OpenClaw      | Open Source |
| ClawdBot      | Open Source |
| MoltBot       | Open Source |
| MoldBot       | Open Source |
| GPT-Engineer  | Open Source |
| Claude Cowork | Anthropic   |

{% hint style="info" %}
**Note:** Claude Cowork is detected as a mode within Claude Desktop (v0.7.0+).
{% endhint %}

#### AI Frameworks & Runtimes

| Agent                 | Vendor      |
| --------------------- | ----------- |
| Ollama                | Open Source |
| LocalAI               | Open Source |
| LM Studio             | LM Studio   |
| Text Generation WebUI | Open Source |

### Expanding an Agent

Each agent row can be expanded to view device-level details.

When expanded, you can see:

* **Device ID**: the unique identifier of the developer machine
* **Agent Version**: the installed version on that device

This allows you to:

* Identify which machines are running a specific AI agent
* Compare versions across devices
* Detect outdated or inconsistent deployments
* Investigate usage patterns


---

# 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/ide-and-ai-agents/coding-tools.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.
