Memboots

Version: 1.0.0 | Publisher: memboots | Identifier: memboots.memboots

Identity: Memboots is the product and configuration surface. Historical/runtime OpenClaw naming is treated as a compatibility detail behind the Memboots Gateway, not a second provider, model list, or settings namespace.

Memboots is the VS Code-compatible extension shell for IDE agent memory and live Memboots telemetry. It observes chat and coding workflows, records memory, routes persona analysis through the Memboots Gateway (@tools/agent-ai), and exposes the Memboots activity bar/dashboard surfaces.

Release Targets

OpenCode release work must not be closed as a VSIX-compatible extension proof until the OpenCode host or adapter contract is captured in a workplan with passing protocol evidence.

2026-06-17 Automation Removal

Memboots no longer ships an auto-approve subsystem.

• Auto-clicking and approval-button automation code has been removed.
• Auto-continue chat injection is disabled.
• Auto-validation-on-save autonomous loops are disabled.
• Legacy retry/scroll bridge commands and PowerShell approval helpers are not packaged.

The runtime source of truth for the remaining automation lockdown is src/safety/automation-policy.ts.

What It Does

1. Multi-Agent Memboots Telemetry

Memboots runs telemetry personas through the bundled agent intelligence modules. The default model path is the Memboots Gateway at https://api.memboots.com with the public model alias memboots/default. Runtime compatibility details stay behind that Memboots surface so users do not have to configure a separate provider identity.

2. Persistent Memory Banks

Memboots captures important conversation turns, observations, decisions, and context to the MCP Memory Banks server backed by Qdrant.

• Auto-capture of significant conversations.
• Auto-retrieve of relevant memories for chat context.
• @memory chat participant.
• CodeLens and hover memory hints.

3. Native Agent Memory Tools

The extension registers memory store, retrieve, and observe tools with VS Code's Language Model API so compatible agent modes can store and retrieve memory without a separate mcp.json.

4. Activity Bar Dashboard

The Activity Bar view shows extension status, MCP Memory health, memory stats, Memboots Gateway status, and model/observer diagnostics.

Install

cd packages/extension
npm run compile
npm test
npm run package
powershell -File deploy-extension.ps1

The deploy script refuses to mutate VS Code-compatible extension folders while IDE windows are running. Close the target IDE first, then reopen only the target window after deploy. Do not use forced live CLI extension installs for local fleet/RDP installs.

Release Channels

Memboots ships one VSIX artifact, memboots-<version>.vsix, with channel metadata in release/channels.json.

Verify the release-channel contract before packaging:

cd packages/extension
npm run release:verify-channels

Antigravity side-load uses the same VSIX package, but local release proof must name the actual host path or CLI used. Do not claim Antigravity runtime acceptance from package creation alone.

OpenCode release proof must use opencode plugin or opencode mcp with a published Memboots package and a memory store/retrieve smoke.

Direct deploy is also supported:

cd packages/extension
powershell -File deploy-extension.ps1

Architecture

Historical package names such as packages/dashboard-agent, the legacy telemetry package, and packages/memboots-app are not current implementation targets.

Backend Services

Commands

Observer and Memory

Disabled Automation Diagnostics

There are no auto-approve settings, commands, keybindings, scripts, content scripts, or bridge shims in the manifest or package.

Configuration

{
  "mcpMemory.serverUrl": "https://mcp.memboots.com",
  "mcpMemory.localhostFirst": false,
  "mcpMemory.autoCapture": true,
  "mcpMemory.autoRetrieve": true,
  "memboots.apiUrl": "https://api.memboots.com",
  "memboots.model": "memboots/default",
  "memboots.apiKey": ""
}

Privacy and Marketplace Disclosure

Memboots can send observer telemetry and memory records to configured Memboots/MCP endpoints when those features are enabled. The v1.0.0 defaults use first-party memboots.com hosts, and approval-button automation is not shipped.

See docs/PRIVACY_AND_MARKETPLACE_DISCLOSURE.md before Marketplace submission.

Gateway Position

Memboots is the product surface. The extension should expose memboots.apiUrl, memboots.model, and memboots.apiKey, and should route through the Memboots Gateway provider by default. Compatible runtime details remain implementation details behind the Memboots name.

Testing

npm --prefix packages/extension run compile
npm --prefix packages/extension test
npm --prefix packages/extension run release:verify-channels

The package test script invokes the package-local Vitest binary.

Project History

v1.0.0 current line (2026-05-22 updates):

• Memboots MCP memory endpoint defaults to mcp.memboots.com; raw Qdrant is private behind MCP/API.
• Memboots docs and package metadata remove historical SpreadKnowledge routing from release paths.

v1.0.0 (2026-05-20):

• First public Memboots release target for the VS Code Marketplace and Memboots standalone product surface.
• Extension identity reset to memboots.memboots@1.0.0.
• app.memboots.com is live-API only; mock and seed observer routes are removed.
• Memboots endpoints now use first-party memboots.com hosts.

v1.0.0 hardening (2026-06-17):

• Auto-approve source, commands, settings, bridge shims, helper scripts, and content-script packaging removed.
• Auto-continue chat injection remains blocked before validation, delay, retry, clipboard, command-palette, or editor insertion paths.

v3.1.0 prelaunch extraction:

• VSIX packaging used the committed local VSCE path before marketplace release packaging was restored.
• Package artifact installed as agiledatasolutions.memboots@3.1.0 before the first marketplace release line was reset to 1.0.0.

v3.0.0:

• Moved the VS Code extension shell from the earlier memboots-api location to memboots/.
• Headless AI logic extracted to @tools/agent-ai.
• Replaced tsc plus node_modules bundling with an esbuild single-file bundle.

Built with: TypeScript, esbuild, VS Code Extension API, @tools/agent-ai, Memboots Gateway, MCP Memory Banks, Qdrant