feat: Agentage VS Code extension v0.0.1 - connect your editor's AI to your memory over MCP#1
Merged
Merged
Conversation
Connect VS Code to your Agentage Memory in the cloud and search it over MCP. - One command (Agentage: Search Memory): live search-as-you-type over memory.agentage.io/mcp (Streamable HTTP), opens the hit read-only. - OAuth 2.1 + PKCE + DCR sign-in; token in SecretStorage; loopback callback. - Gear (settings) + sign-out buttons in the search box; agentage.mcpUrl setting. - esbuild bundle, vitest unit tests, dual-registry (Marketplace + Open VSX) CI. - Official agentage rocket-A icon.
- Rename to Agentage (displayName + id 'agentage.agentage'); memory is the current scope, room to grow. - Add 'Agentage: Connect Memory to this editor': registers the MCP server with the host editor's AI (VS Code install deeplink; Cursor/Windsurf config files, merged not clobbered). VS Code/Cursor/Windsurf detection via env.uriScheme. - Remove the in-process Search Memory command + its client/auth/doc stack and the @modelcontextprotocol/sdk dependency (host editor handles MCP + OAuth). - Bundle 280KB -> 6.3KB; README/CHANGELOG/CONTRIBUTING rewritten.
vreshch
changed the title
… + temp HOME Asserts the real command writes the correct mcp.json per host (Cursor url, Windsurf serverUrl, merge-preserving), opens the VS Code mcp/install deeplink, handles unknown hosts, and honors agentage.mcpUrl.
- P0: mergeServer now throws ConfigParseError on an unparseable/odd-shaped existing config; connectEditor refuses to write and offers Open/Copy instead (no data loss). - P1: stripJsonc handles trailing commas string-aware (no more corrupting values containing ',}'); array/non-object guards. - P1: fold VSCodium into the mcp/install deeplink; actionable manual fallback with Setup guide + recovery buttons; relabel Open-config button to the file name. - P1: engines.vscode ^1.99.0 (was ^1.85.0) + README note that one-click needs 1.101+. - P2: publish.yml tag<->version assert; ci.yml vsce-package gate. - Tests: 13 core + 7 integration (clobber-safety, comma round-trip, VSCodium deeplink).
…-matcher, gh release on publish, drop stale vsce flag
- VS Code: native MCP provider (contributes.mcpServerDefinitionProviders + registerMcpServerDefinitionProvider, stable since 1.99) registered at activation (onStartupFinished) - the server appears in the MCP list automatically; VS Code runs OAuth on first use (one-time trust + sign-in; auth'd servers don't auto-start). - Cursor/Windsurf: autoConnectForks writes their config silently + idempotently on activation (hasServerEntry skip; never clobbers; errors swallowed). - Manual command kept for re-connect / unknown forks. engines stays ^1.99.0. - Tests: 15 core + 3 provider + 10 connect-editor = 28. README/CHANGELOG/CONTRIBUTING updated.
Real-VS-Code smoke proving the packaged extension activates, registers agentage.connectEditor, and contributes the default mcpUrl - the gap the vitest unit tests (logic-only, mocked vscode) can't cover. Wired into CI behind Xvfb; uploads the .vsix artifact for the e2e vscode project.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Initial release of the Agentage extension. One command connects your editor's AI agent - GitHub Copilot, Cursor, or Windsurf - to your Agentage memory over MCP, so it can read and answer from the same memory every AI you use shares.
Named Agentage (not "Agentage Memory") - memory is the current scope, with room to grow.
What it does
Agentage: Connect Memory to this editorregisters the remote MCP server (memory.agentage.io/mcp, Streamable HTTP) with the host editor's agent:mcp/installdeeplink (host-managed, global).~/.cursor/mcp.json(mcpServers+url).~/.codeium/windsurf/mcp_config.json(mcpServers+serverUrl).env.uriScheme.agentage.mcpUrlsetting to target a different stack.Design
@modelcontextprotocol/sdkdependency is gone and the bundle is 6.3 KB (.vsix31 KB).connect-core.tsare vitest-tested (10 tests); thevscode-facing glue is inconnect-editor.ts.capabilities.untrustedWorkspaces,extensionKind), dual-registry publish CI onv*tags, demo GIF.Verification
npm run check-typesclean,npm test10/10,vsce packageclean (6 files), bundle smoke-loads.mcp/installdeeplink + Cursor/Windsurf config pickup, and the host-side OAuth againstauth.agentage.io- needs a real F5 run in each editor. Confirm the AS allows VS Code's redirect (http://127.0.0.1:33418,https://vscode.dev/redirect).Notes
agentage(Marketplace) + an Open VSX namespace, and theVS_MARKETPLACE_TOKEN/OPEN_VSX_TOKENsecrets, then av0.0.1tag.