Skarn 0.34.0: Copilot in Code

Scanning Copilot in Code sessions

With no setting, skarn assess and skarn check scan the transcripts under %LOCALAPPDATA%\Microsoft\Copilot\User Data\CopilotCodingHome\, and under the app's MSIX path when it exists. The scan also reads each session's files, research and checkpoints folders, each profile's session-store.db session index, and the tool-output spill files a transcript names. It never opens the profile's data.db.

The recall commands list these sessions. Select them with --cli copilot-code:

Copilot in Code runs only on Windows. On macOS and Linux the source reads only the directory that tools.copilot-code.sessions_path in ~/.skarn.json names.

The guard, doctor and vet

skarn setup --agent copilot-code writes the guard hook into every Copilot in Code profile, and skarn doctor checks it. In enforce mode the guard answers a would-be ask with a deny on Copilot in Code.

skarn vet reads each profile's configuration, and now also the Copilot CLI's hook folders. skarn serve and the HTML report draw Copilot in Code in its own colour.

Measured on Copilot app 156.0.4314.58 with GitHub Copilot CLI 1.0.93.

Windows fixes

• A session whose recorded working directory is a drive path now reports its project. Before, the project was empty for Copilot CLI sessions and for every other assistant that records a working directory. A working directory on a network share still reports no project.
• A COPILOT_HOME that ends in a backslash no longer puts a mixed separator into reported session paths.
• skarn doctor no longer reports a healthy Copilot CLI, Copilot in Code, Gemini CLI or Grok Build hook as logging disabled and drifted, or a healthy Codex CLI hook as drifted.
• Re-running skarn setup no longer adds a second skarn hook for Copilot CLI, Codex CLI or Copilot in Code.
• skarn setup now installs the Claude Code and Cursor hooks on native Windows, where it used to stop with a verify failure, and warns that neither hook protects that machine; skarn doctor does not count either one as wired.
• The core unit tests and the Copilot integration cases now run on Windows in continuous integration.

Every hook event the guard gates on Copilot in Code is in the guard hook-event reference, and the store's path sits with the others in where AI coding assistants store sessions.