Docs

Gemini CLI

Google's terminal AI tool. Fully covered for Block. Ask falls through to Gemini's own confirmation.

What ZYBE can do

Block, on every rule. Gemini CLI has no "ask the developer" in its built-in check, so a rule set to Ask records the attempt, shows ZYBE's reason in the terminal, and Gemini's own confirmation prompt takes over.

With Cover the conversation on, Gemini CLI also sends its requests to Google through ZYBE on the laptop when it signs in with a Gemini API key, so a pasted key is stopped before it leaves and injected text in a tool result is caught as it goes to the model.

What you do

Install the sensor. Restart Gemini CLI if it was running.

Check it's working

  1. Run gemini and ask it for any command.
  2. In the console, open the laptop from Inventory, Endpoints, click Sensor. Gemini CLI shows Blocking.

What the developer sees when blocked

Tool execution blocked: Blocked by your organisation: ...

If ZYBE isn't connected

ZYBE reads Gemini's own session records after the fact. The console shows it as Recording.

For IT

ZYBE's connection is in ~/.gemini/settings.json, merged in next to everything else there.