[BUG] remember tool fails with "upper bound size missing" on VS Code Extension v0.825.0 #15

Bug Description

The remember tool (Agent Memories) fails on every invocation with the error "upper bound size missing", regardless of input content or length. The underlying Augment-Memories storage file exists and is healthy — the bug is in the tool's runtime validation layer, not the storage backend.

Environment

Steps to Reproduce

1. Open any workspace with Augment Agent enabled
2. Ask the agent to remember something (e.g., "remember that X uses Y")
3. Agent calls the remember tool with a valid memory string parameter
4. Tool returns error: "upper bound size missing"

This happens with inputs of any length — even a 3-word string like "Test memory persistence." fails.

Expected Behavior

The memory should be appended to the Augment-Memories file in workspace storage.

Actual Behavior

Tool returns "upper bound size missing" error. No write occurs.

Diagnostic Evidence

Storage file exists and is healthy

Path: %APPDATA%\Code\User\workspaceStorage\<hash>\Augment.vscode-augment\Augment-Memories
Size: 1140 bytes
Entries: 15 valid memory lines

The file was likely written by a prior extension version. The current version (v0.825.0) can read these memories but cannot write new ones via the tool.

Related fix in JetBrains

The Augment changelog for IntelliJ Plugin v0.428.9 (March 18, 2026) includes:

"Fixed memory settings not propagating to tool list"

This appears to be the same class of bug — the tool's schema/configuration (specifically the upper_bound / max_size constraint) is not being propagated from extension settings to the tool definition at registration time.

The VS Code Extension v0.814.0 (March 11, 2026) included a partial fix:

"Made memory settings reactive across webviews"

...but the tool-level registration bug appears to persist in v0.825.0.

Suggested Fix

Ensure the remember tool's JSON schema includes the required upper_bound size parameter when the tool is registered with the agent runtime, mirroring the fix applied in IntelliJ Plugin v0.428.9.

Labels

bug, vscode-extension, agent-memories