Skip to content

GitHub Copilot CLI security on your Mac

Excellent for Mac is free to scan. It reads GitHub Copilot CLI's logs and shows what it did. With Pro, it checks each action before it runs.

Works with GitHub Copilot CLI

Trademarks belong to their owners; no endorsement implied.

What Excellent sees

Excellent reads GitHub Copilot CLI's session logs in ~/.copilot/session-state on your Mac, in the event format GitHub documents.

It shows what was done: your email sent to websites or typed into forms, keys sitting in logs, secrets files read, history overwritten, checks skipped. Each finding says which agent and where.

With Pro, while the app runs, it reads GitHub Copilot CLI's logs as they grow, and sends you a notification when something new needs you.

Its key finder checks Copilot CLI's settings for keys, and reports its sign-in file without changing it.

What it can stop Pro

This needs Excellent Pro. Free and Pro says what each does.

Turn on protection, and Excellent writes its own hook file, ~/.copilot/hooks/excellent.json, which Copilot CLI runs before each action. Excellent also knows Copilot CLI's requests through a repository's .claude/settings.json.

It blocks your email on its way to a website, an API key typed into a command, deleting a folder you marked never-delete, and switching Excellent off.

It asks you first before a force push to main, skipping git hooks, typing your email into a web form, or writing over a file you marked never-delete.

Two more rules are off until you turn them on: asking before reading keys and .env files, and asking before breaking a rule you wrote in CLAUDE.md or AGENTS.md.

You can stop a Copilot CLI session from Excellent's menu. Its actions are refused until you press Continue or End. End stops its process and the commands it was running.

Excellent can also pause a session by itself when it breaks one of four rules: sending your email to a website, deleting or moving a never-delete folder, reading a never-open file, or overwriting history on main. Setup asks about this, with all four ticked.

Tested in GitHub Copilot CLI 1.0.112 on a Mac: the check Turn On adds ran there, refused what it should, and let a harmless command through.

Your rules

Sharing works between Claude Code and Codex. GitHub Copilot CLI doesn't get your rules from it.

With Pro and Remind agents of my rules on, the check refuses an action that would break a rule you wrote in CLAUDE.md or AGENTS.md once, and quotes your rule. Reminders are off by default.

The sandbox Pro

Excellent's sandbox covers Claude Code and Codex. GitHub Copilot CLI gets the live check only.

What isn't covered

  • Excellent's sandbox doesn't cover Copilot CLI, so nothing backs the check up there.
  • The check reads what a command says. An agent set on getting around it sometimes can.
  • A script file run by an interpreter, like python3 cleanup.py, isn't read by the check.
  • With disableAllHooks set in Copilot's settings, the check doesn't run, and Excellent shows Copilot CLI as not protected, with the reason.
  • Copilot CLI stops every action when a hook it's told to run is missing. That keeps you safe, so take Excellent out with Remove Excellent in Settings, which removes its hook first.

Set it up

  • Get the Mac app. It needs an Apple silicon Mac and macOS 14 or later. Protection needs Pro.
  • With Pro, open it and press Protect My Agents. It lists what it will change first, then adds its check to ~/.copilot/hooks/excellent.json. Turn On in the menu does the same later.
  • To take Excellent out later, use Remove Excellent in Settings, so Copilot CLI's hook goes first.

Install the Mac appTurn on protectionStop or pause an agentRemove ExcellentThe agents it supports

The other agents

Protect GitHub Copilot CLI on your Mac

Get the Mac app