Local graph memory for coding agents using MCP.

Waggle gives VS Code agents persistent repo memory without a cloud account or API key.

This extension is the one-click onboarding path for Waggle in VS Code. It installs the Waggle CLI when needed, writes the MCP config for the current workspace after confirmation, runs doctor, and leaves the workspace ready to use the underlying MCP server.

What it does

Detects whether waggle-mcp is installed
Offers a consented one-click setup flow
Installs Waggle with pipx when needed
Safely creates or updates .vscode/mcp.json
Preserves non-Waggle MCP servers already configured in the workspace
Runs waggle-mcp doctor and shows output in a dedicated output channel
Launches Graph Studio locally
Exports local memory to .abhi

What it is for

Use Waggle when you want coding agents in VS Code to remember:

architecture decisions
repo-specific constraints
user preferences and corrections
contradictions and superseded context
session handoff context across chats

Requirements

VS Code 1.96+
pipx available on PATH for one-click install
Python 3.11+ for the Waggle CLI

Quick start

Install the extension
Run Waggle: Enable for this Workspace
Confirm the install/configure flow
Reload VS Code if your MCP consumer requires it
Waggle runs doctor as part of setup

Commands

Waggle: Enable for this Workspace
Waggle: Install Waggle
Waggle: Run Doctor
Waggle: Open Graph Studio
Waggle: Show Status
Waggle: Export Memory
Waggle: Open Install Docs

Development

npm install
npm run compile

Packaging

npm run package

Privacy

Local by default
No cloud account required
No API key required
Memory stored in WAGGLE_DB_PATH, defaulting to ~/.waggle/waggle.db

Marketplace notes

This extension is meant to behave like MCP-style one-click setup for VS Code users. Users can also install the generated .vsix manually before Marketplace publication.