Klarwolf for VS Code and Cursor

Your Klarwolf memory and projects in your editor. Paste one key and:

• Copilot's agent mode can use them. Klarwolf shows up as a tool server in Copilot Chat (agent mode) with nothing to edit by hand: Copilot can look up what Klarwolf knows about you, read a project's instructions and files, and save a preference when you ask it to.
• Ask Klarwolf without leaving the editor. Select some text, right-click: Remember this or What do you remember about…. Or use the Command Palette (⇧⌘P / Ctrl+Shift+P, type "Klarwolf"): connect, recall, remember, open a project. The answer opens beside your code.
• Cursor: Klarwolf: Copy setup for Cursor puts the setup on your clipboard for Cursor › Settings › MCP.

It calls no AI. Recall, remember and opening a project don't cost anything and don't use your plan's AI allowance.

A Wolfpack company: wolfpackfrontholding.com.

Getting started

1. In Klarwolf, open Settings › Your AIs (klarwolf.com/app#keys) and make an API key. It starts with cxa_ and is shown once.
2. In VS Code or Cursor: Command Palette → Klarwolf: Connect → paste the key.
3. In Copilot Chat, pick Agent mode. Klarwolf's tools are in the tools list.

Your key is kept in your computer's keychain (the editor's secret storage), never in settings or a file. Klarwolf: Disconnect removes it from this editor; deleting the key in Klarwolf › Settings › Your AIs stops it everywhere.

What Klarwolf won't keep: passwords, keys, contact details, and health, money, family or legal matters. Those are refused, the same as in the app. Everything the tools return is your own saved data, given to the AI as reference, not as instructions.

Needs: VS Code 1.101 or later for Copilot's agent mode. The commands work in any recent VS Code or Cursor.

For the team

Build the installable file: npm run package → klarwolf.vsix (install it with Extensions › … › Install from VSIX). CI (.github/workflows/klarwolf-vscode.yml) tests and packages every change and keeps the .vsix under the run's Artifacts.

Publishing (the VS Code Marketplace, and Open VSX, which is where Cursor installs from) runs from Run workflow on main with "publish" ticked, and publishes the version in package.json (raise it first: a store won't take the same version twice). Live since 28 Oct 2026: Marketplace, Open VSX.

• VS Code Marketplace: trusted publishing, no token. The publisher wolfpackfront (Marketplace › Manage › Wolfpack › Trusted Publishing) has a policy for donaldgrieb-lab/wolfpackfront-site, workflow klarwolf-vscode.yml; the job asks GitHub for an OIDC token (id-token: write) and runs vsce publish --oidc. Renaming the workflow file or the repo breaks it until the policy is recreated. A new policy stays inactive until its first successful publish, which must happen within about two days of creating it.
• Open VSX: the repository secret OVSX_PAT (open-vsx.org › Settings › Access Tokens, namespace wolfpackfront, publishing only). Open VSX's own trusted publishing needs a public repository and a verified namespace, so it isn't used. Without the secret that step says so and is skipped.

The old VSCE_PAT secret (an Azure DevOps token) isn't used any more; Azure DevOps stops honouring all-organization tokens on 1 Dec 2026. Delete it from the repository secrets.

The connector must be on (FLAG_cortexMcp). While it's off, Connect says "isn't switched on for your account yet".

Another product

Copy this folder, change extension.config.json, and in package.json change name, displayName, publisher, the klarwolf. prefix on the command ids and the setting, and the provider id. Replace media/icon.png. Nothing in src/ names Klarwolf. For publishing, create the product's own Marketplace trusted publishing policy and Open VSX token.