Docs

What the developer sees

Exactly what a developer sees on their laptop when ZYBE records, asks, or refuses. Nothing more and nothing hidden.

Most of the time a developer never notices ZYBE. It runs inside the AI tool's own check, takes a few milliseconds, and says nothing. This page shows the moments it does speak, so you can tell your team what to expect before you roll it out.

When a rule is set to Report

Nothing. The tool runs the action as usual. ZYBE records that it happened, and the console shows it under Detections. The developer sees no message.

When a rule is set to Ask

The AI tool pauses and shows the developer a line like this, in its own confirmation box:

Your organisation's rule "Agent read a credential file" asks a person to confirm this (ZYBE). Ask for an exception: https://console.zybe.ai/exception?...

The developer can confirm and carry on, or click the link to ask for a standing exception. Claude Code, Cursor, Codex CLI, VS Code, Copilot CLI, Antigravity, Hermes and OpenClaw pause like this. Gemini CLI and Devin Desktop have no pause of their own, so there the line is shown and the tool's usual confirmation takes over.

When a rule is set to Block

The AI tool refuses the action and shows the developer why:

Blocked by your organisation's rule "Agent sent a secret off the laptop" (ZYBE). Ask for an exception: https://console.zybe.ai/exception?...

The agent sees the same words, so it can explain itself and try another way. The link opens a short page, Ask for an exception, where the developer writes one line about why they need it. The request lands in the console under Requests, and the developer gets a mail when it's decided.

When a contained item is used

If an admin has contained an MCP server, a skill, a package or a model, the tool shows:

This is blocked by your organisation. It matches an item that has been contained.

For a package or model that is held for approval rather than contained:

Held for review by your organisation: the package left-pad has not been approved. Ask for it: https://console.zybe.ai/request?...

The link opens Ask to install this, one line of reason, same flow as an exception.

When a secret is pasted into the prompt

With Pasted secrets set to Block, the message is stopped before it leaves the laptop:

ZYBE stopped this message: it contains an AWS key. Take it out and send again.

The words never leave the laptop. Set to Record, the message goes through and the console shows that a secret was pasted, without the secret.

When the conversation is covered

Nothing changes on screen. The tool talks to ZYBE on the laptop and ZYBE talks to the vendor. A pasted key is stopped with the same words as above. The developer's own sign-in and key stay theirs.

When a product is Not allowed

An app named under Refused products stops opening. On a Mac the developer sees the usual "can't be opened" message from the system; a command-line tool answers "permission denied". There's no ZYBE dialog, because the app never gets far enough to show one. The console shows the product as Not allowed on that laptop, and the permission comes back within a minute of the product being allowed again.

When ZYBE can't run its check

By default, the action goes through and the developer sees nothing. If your workspace has Refuse what ZYBE can't check on, the tool shows:

ZYBE could not check this action, and this workspace refuses what it cannot check. Try again in a moment; if it keeps happening, tell your admin.

What a developer can look at themselves

• Their own page in the console. The weekly note mailed to each person carries a link that signs them in as a member: their own laptops, their own findings, nobody else's.
• The free command line. npx zybe log shows what ZYBE recorded on this machine. There's no command that turns protection off on a managed install.

What a developer never sees

• The contents of their prompts, files or command output. Those are read on the laptop and never sent.
• A pop-up from ZYBE itself. Every message above is shown by the AI tool, inside its own interface.
• A slowdown. The check adds a few milliseconds to each action.