Integration: Continue.dev

Coverage status

Path	Status	Notes
MCP server	✅ Supported	`contextProviders` in config.json
Harness	✅ Supported	Custom LLM base URL
Browser extension	✅ Supported	For web-based Continue sessions

Confidence: High. Continue.dev has first-class MCP context provider support. All three paths are validated. Most users should use MCP — it’s the most direct integration.

Setup: MCP context provider (recommended)

1. Start the MemStrata MCP server

memstrata serve --port 8080

2. Add MemStrata to Continue’s config

Edit ~/.continue/config.json (or your project’s .continuerc.json):

{
  "models": [
    {
      "title": "Claude 3.7 Sonnet",
      "provider": "anthropic",
      "model": "claude-3-7-sonnet-20250219",
      "apiKey": "YOUR_KEY"
    }
  ],
  "contextProviders": [
    {
      "name": "memstrata",
      "params": {
        "endpoint": "http://localhost:8080/mcp",
        "autoInject": true
      }
    }
  ]
}

With autoInject: true, MemStrata automatically provides compressed context for every Continue chat turn — no need to type @memstrata each time.

3. Verify

Open the Continue panel in VS Code → ask any question. You should see “memstrata” in the context sources listed below the chat input. Token count will be lower than without MemStrata.

Setup: Harness proxy

1. Start the harness

memstrata serve --port 8080

2. Configure Continue’s LLM to use the harness

In config.json, point the model at the harness:

{
  "models": [
    {
      "title": "Claude (via MemStrata)",
      "provider": "openai",
      "model": "claude-3-7-sonnet-20250219",
      "apiBase": "http://localhost:8080/anthropic",
      "apiKey": "YOUR_ANTHROPIC_KEY"
    }
  ]
}

What’s captured

Signal	Captured?	Notes
Continue chat turns	✅ Yes	Via MCP context provider
Inline completions (`Tab`)	✅ Yes	Via harness proxy
`@codebase` queries	✅ Yes	MemStrata and Continue’s own codebase index both run; MemStrata’s compressed slice supplements
Edit mode (Ctrl+I)	✅ Yes	Harness path captures edits
Continue.dev slash commands	✅ Yes	Custom commands pass through the MCP context provider

Troubleshooting

autoInject not working
Verify the harness is running and the endpoint URL is correct. Check Continue’s output panel for MCP errors.

Double context — MemStrata + @codebase
Both MemStrata and Continue’s built-in @codebase can provide context simultaneously. To avoid overlap, either disable @codebase in config or set autoInject: false and use @memstrata explicitly.