MemStrata Coder with VS Code, Cursor, Windsurf, and Terminal Agents
How Coder connects to VS Code, VS Code shims such as Cursor and Windsurf, JetBrains IDEs, and terminal agents including Claude Code, Codex CLI, Aider, and OpenCode via MCP, harness, or extension.
One local runtime, three connection paths
MemStrata Coder is a local context runtime. Editors and agents attach through MCP, an OpenAI-compatible harness, or the VS Code extension. You do not need all three. Pick the path your tool already speaks.
The VS Code extension also loads in VS Code shims: Cursor and Windsurf are VS Code forks, so the same extension and MCP server apply. Continue.dev and Cline sit in that family too.
IDEs versus terminal agents
IDEs: VS Code, JetBrains AI (IntelliJ, PyCharm, WebStorm, GoLand), and Zed.
VS Code shims: Cursor, Windsurf, Continue.dev, Cline, and GitHub Copilot Chat (chat participant; inline tab-complete is not captured).
Terminal: Claude Code, Codex CLI, Aider, OpenCode, and Claude Desktop.
Native Composer/Cmd+K in Cursor is partial. We label unsupported native shortcuts instead of implying they are routed.
What to measure after you connect
Coder counts each visible user prompt once, even if the client makes several model calls. A controlled four-turn E2E test showed 81.4% input-token avoidance against a one-time full-repository session-start counterfactual. That is not a median and not a guarantee. See the methodology.
Install from PyPI on Linux x86_64, then open the Coder product page for the live coverage grid.