Docs
AI tools ZYBE covers
Every AI tool ZYBE knows, what it can do on each, and what you have to do to get there. Usually nothing beyond installing the sensor.
The table
| AI tool | What ZYBE can do | What you do |
|---|---|---|
| Claude Code | Block | Install the sensor |
| Cursor | Block | Install the sensor |
| Codex CLI | Block | Install the sensor. On a just-me install, approve ZYBE once inside Codex. |
| VS Code with Copilot Chat | Block | Install the sensor. Push the VS Code policy for the part a developer can't undo. |
| Copilot CLI | Block | Install the sensor |
| Gemini CLI | Block | Install the sensor |
| Devin Desktop, formerly Windsurf | Block | Install the sensor |
| Antigravity | Block | Install the sensor |
| Hermes Agent | Block | Install the sensor |
| OpenClaw | Block | Install the sensor. Restart OpenClaw's gateway once. |
| Claude Desktop | Block its MCP servers | Install the sensor, restart Claude Desktop |
| Cline and Roo Code | Block their MCP servers | Install the sensor, restart the editor |
| Continue, Kilo Code, Augment | See that it's installed, or refuse it outright | Install the sensor. To refuse it, name it under Rules. |
| ChatGPT Desktop, Comet, Grok | See that it's installed, or refuse it outright | Install the sensor. To refuse it, name it under Rules. |
"Block" means every rule on the Rules page that can be set to Block holds on that tool: credential reads, dangerous commands, contained MCP servers and packages, action after prompt injection, your own rules, all of it. "Block its MCP servers" means the same, for everything the app does through MCP servers, which is how those apps touch the machine.
How you know it's working
Open a laptop from Inventory, Endpoints, and click Sensor. Each AI tool has one word next to it.
| Word | Meaning |
|---|---|
| Blocking | ZYBE can stop its actions. |
| Recording | ZYBE sees its actions but can't stop them. |
| Seen | ZYBE knows it's there, nothing more. |
| Silent | ZYBE is connected but the tool has run without reporting. Restart the tool. |
| Not allowed | The company refused the product and the laptop has taken away its permission to run. |
ZYBE only says Blocking once it has actually checked an action from that tool on that machine. A settings file being in place isn't enough.
Ask versus Block
Claude Code, Cursor, Codex CLI, VS Code, Copilot CLI, Antigravity, Hermes and OpenClaw can pause and ask the developer. Gemini CLI and Devin Desktop can't; on those, an Ask rule records the attempt and the tool's own confirmation prompt takes over. Block works on every tool in the table.
The tools that can only be Seen
Continue, Kilo Code, Augment, ChatGPT Desktop, Comet and Grok give ZYBE no way to check their actions one at a time. ZYBE lists them and raises the issue Agent that can't be blocked once per tool, so you decide. If the answer is no, name the product under Rules, Refused products, and every laptop takes away its permission to run. It then shows Not allowed. See Refuse an AI app.