LIVENative hooks, nine events

An audit trail for GitHub Copilot CLI

Euthyne plugs into GitHub Copilot CLI through its own hooks. Every prompt, tool call, failed tool call and subagent in an enrolled repository becomes a signed receipt, in the same format as Claude Code and Codex.

What Euthyne records

What Euthyne records for GitHub Copilot CLI

Prompts and tool calls

Prompts, shell commands, file edits with the file they touch, failed tool calls, subagents and turns become signed receipts. Copilot CLI does not pass the model name to hooks, so receipts record it as unknown. Content stays on your machine as salted hashes.

MandatesNo

Each session's mandate carries a salted digest of your Copilot user settings, but Euthyne does not read Copilot's tool permissions yet, so checks read unknown. On Team and Company, your org's signed policy decides each tool call on your machine before it runs, offline. Enforced, fails open on timeout: Copilot CLI denies the call if the hook crashes, but runs it if the hook times out.

Tokens and costNo

Copilot CLI hooks carry no token counts or cost. Its OpenTelemetry export has token counts, which Euthyne does not read yet.

User-level install

--hooks user writes ~/.copilot/hooks/euthyne.json (or $COPILOT_HOME/hooks/) so the hooks run in every project. Copilot CLI loads hooks when it starts.

Repo-level install

--hooks repo writes .github/hooks/euthyne.json in the repository and keeps it out of git. Copilot CLI runs repository hooks only in a folder you trusted.

Content stays with you

Prompts, outputs, commands and file contents are committed as salted hashes before anything leaves your machine.

Hook events

The GitHub Copilot CLI hooks Euthyne uses

Sessions

sessionStart and sessionEnd open and close the record of each session.

Prompts

userPromptSubmitted records each prompt, with its text kept as a salted hash.

Policy decisions

preToolUse checks each tool call against your org's signed policy, when it has one, and signs the decision. An ask rule denies.

Tool calls

postToolUse and postToolUseFailure record shell commands, file edits and other tools, with their outcome and the file an edit touches.

Subagents

subagentStart and subagentStop record each subagent Copilot starts, and its tool calls carry its id.

Turns

agentStop records the end of each turn.

Install

From install to the first GitHub Copilot CLI receipt

  1. Install the CLI

    With curl or Homebrew, on macOS or Linux. The script checks the release against its checksums and installs to ~/.local/bin.

  2. euthyne init --agent copilot

    Read the consent text, sign in through your browser and enrol the repository. Init writes the Copilot CLI hooks. Nothing is recorded before you accept.

  3. Restart Copilot CLI

    Copilot CLI loads hooks when it starts. Start copilot again in the repository and trust the folder when it asks.

Install script
curl -fsSL https://euthyne.com/install | sh
Homebrew
brew install euthyne-labs/tap/euthyne
Set up GitHub Copilot CLI
euthyne init --agent copilot
FAQ

Common questions

Yes. Euthyne records GitHub Copilot CLI today, in the repositories you enrol.

Nine: sessionStart, userPromptSubmitted, preToolUse, postToolUse, postToolUseFailure, subagentStart, subagentStop, agentStop and sessionEnd. Each runs euthyne hook copilot with the event name. preToolUse only decides when your org has an enforced policy; otherwise it prints nothing.

Copilot CLI does not pass the model name, tokens or cost to hooks, so Euthyne cannot sign them. Everything else a receipt holds, from the repository and commit to the files an edit touches, is there.

No. Euthyne records Copilot CLI on your machine, where it can sign each receipt locally. GitHub runs hooks in the Copilot cloud agent inside a sandbox that is gone when the job ends.

Only if your org publishes an enforced policy, on Team and Company. A new policy starts in dry run: decisions are signed into receipts and nothing is blocked. Once enforced, a denied call is blocked through Copilot CLI's preToolUse deny, and Copilot is told the rule id and its reason, never the policy. Shell, file reads and writes, web and MCP calls are matched against the same rules as Claude Code, so a rule like Bash(git push:*) applies here too; other known tools are decided under their own names. Tools Euthyne does not know yet, and MCP calls that do not name an exact server and tool, are denied while a policy is enforced. Copilot CLI runs the call anyway if the hook times out, so we label it enforced, fails open on timeout.

Related

Where to go next

Facts about GitHub Copilot CLI checked 23 Oct 2026 against its documentation. Spot something out of date? Write to hello@euthyne.com.

GitHub and GitHub Copilot are trademarks of GitHub, Inc. Euthyne is not affiliated with, endorsed by or sponsored by GitHub.

Every action.
On the record.

Euthyne is in public beta. Leave your email and we'll reach out, or install the CLI and read the quickstart.

Install script
curl -fsSL https://euthyne.com/install | sh
Homebrew
brew install euthyne-labs/tap/euthyne
Read the quickstart
Euthyne
EuthyneBordeaux