KoalaFix
Sign in Get early access
Menu

Connect GitHub Copilot to KoalaFix.

Help · Connect your tools · updated 29 October 2026

Connect your tools

One plugin, koalafix-copilot, brings KoalaFix to Copilot CLI, VS Code’s Copilot agent and the GitHub Copilot app. It carries the KoalaFix server and its tools, the session routine, and the hooks that make memory automatic.

Copilot CLI

copilot plugin marketplace add KoalaFix/koalafix-connect
copilot plugin install koalafix-copilot@koalafix-connect

Inside a session, the same works as /plugin marketplace add KoalaFix/koalafix-connect, then /plugin install koalafix-copilot@koalafix-connect. Start a new session afterwards.

VS Code

In a Copilot chat session, type:

/plugin marketplace add KoalaFix/koalafix-connect
/plugin install koalafix-copilot@koalafix-connect

VS Code asks you to trust the marketplace the first time. A plugin you installed with Copilot CLI shows up in VS Code by itself. Hooks are a preview feature in VS Code.

GitHub Copilot app

Open Customize, then Plugins. Add the marketplace KoalaFix/koalafix-connect with the icon next to the marketplace list, then install koalafix-copilot.

Sign in

The KoalaFix server signs you in with OAuth. In Copilot CLI, run /mcp auth koalafix in a session if the browser doesn’t open by itself.

The hooks sign in on their own: on first use, the agent shows you a link and a code. Approve it once in your browser and the hooks turn on. Both sign-ins use the same KoalaFix account.

A session started with copilot -p can’t sign in, so it skips KoalaFix’s tools until you’ve signed in once in a normal session.

What the hooks do

  • Session start: the team’s brief, its facts and open items, goes in front of the session.
  • Each prompt: one search of team memory about what you asked, added after your prompt where the model reads it. The prompt you see in the timeline doesn’t change.

The hooks need Node.js 22 or later. They send KoalaFix your prompt’s text for the search, up to 2,000 characters with anything shaped like a token or key taken out, and never file contents or attachments. The full list is in the plugin’s README.

With a token

When a browser sign-in can’t run, on a server or under a company policy that blocks it, use a personal token from your dashboard’s Account page. Turn off the plugin’s server and add one that sends the token, under its own name:

copilot mcp disable koalafix
copilot mcp add --transport http --header "Authorization: Bearer <your token>" koalafix-token https://mcp.koalafix.com/mcp

This writes the token into ~/.copilot/mcp-config.json, never into a project.

Copilot cloud agent, JetBrains and Visual Studio

  • Copilot cloud agent: it runs hooks only from files committed to the repository and has no KoalaFix sign-in, so connect it with a token. Your dashboard’s Integrations page has the repository MCP configuration.
  • JetBrains and Visual Studio: Copilot there runs no hooks. Add the KoalaFix server from your dashboard’s Integrations page.

If it doesn’t work

  • No brief in Copilot CLI with the session sandbox on. The sandbox lets a plugin’s hooks read only their own folder, so they can’t reach your KoalaFix sign-in and stay off for that session; the tools still work. GitHub’s documentation describes allowing a folder: add your ~/.kalibrate folder to sandbox.userPolicy in ~/.copilot/settings.json.
  • No search results after your prompt. Copilot keeps only the last rewrite of a prompt, so another plugin that also rewrites prompts can replace KoalaFix’s.
  • A hook error in Copilot’s log. Without Node.js 22 or later the hooks do nothing, and Copilot logs one hook error.

Still stuck? Email support@koalafix.com from the address you sign in with. Support says what to include and when we reply.