Tracing for GitHub Copilot records each Copilot Chat prompt as a trace, with the tools it invoked nested beneath it. Copilot differs from every other supported tool in one important way: its hook config lives in the repository, not in your home directory.

​
Copilot is configured per repository

Every other supported tool registers its hooks once per user. Copilot registers them in .github/hooks/hooks.json, which is inside the repository you run the installer from.
Run the installer from the root of the repository you want traced. Because the config file is part of the repository, tracing applies to that project only, and you need to run the installer again in every other repository you want covered.
This also means the file can be committed. Decide deliberately which you want:
  • Commit it so everyone working on the repository gets tracing automatically. Your license key is not in this file, so committing it does not expose a credential.
  • Ignore it by adding .github/hooks/hooks.json to .gitignore if tracing should stay per developer.

​
Install

Change into the repository you want traced, then run the installer. On macOS or Linux:
On Windows:
The installer prompts for your license key and project name, stores them in ~/.atatus/harness/config.json, and writes the hooks to .github/hooks/hooks.json in the current directory. Add --with-skills to also link the manage-copilot-tracing skill into the current directory.
Your credentials still live in ~/.atatus/harness/config.json, shared with your other tools. Only the hook registration is per repository, so you enter your license key once no matter how many repositories you trace.

​
What gets captured

​
Where things live

Six hook events are registered: SessionStart, UserPromptSubmit, PreToolUse, PostToolUse, Stop, and SubagentStop.

​
Trace several repositories

Because the config is per repository, run the installer in each one. The second and later runs reuse the license key and project name you already entered, so you are not prompted again. If you want each repository reported separately, override the project name for that run:

​
Uninstall

Run this from the repository whose tracing you want to remove:
This removes the hook entries from that repository’s .github/hooks/hooks.json. Repositories you traced separately keep their own configuration until you uninstall in each one. See Uninstall for the full-wipe option.