Skip to content

Fix MCP transparent fallback mode#1019

Merged
wbugitlab1 merged 4 commits into
mainfrom
issue/273-transparent-fallback-mode
Jun 19, 2026
Merged

Fix MCP transparent fallback mode#1019
wbugitlab1 merged 4 commits into
mainfrom
issue/273-transparent-fallback-mode

Conversation

@wbugitlab1

Copy link
Copy Markdown
Owner

Summary

  • Add storage_mode: "local" | "remote" to successful JSON text responses for the seven fallback-capable standalone MCP shim tools.
  • Add AGENTMEMORY_NO_FALLBACK=1 as a strict/no-local-fallback alias alongside the existing strict flags.
  • Update README/package/config docs and regenerated config-skill reference.

This addresses the transparent fallback and strict alias parts of #273. Sync-on-reconnect remains intentionally out of scope.

Verification

  • corepack pnpm run skills:gen
  • corepack pnpm run skills:check
  • corepack pnpm run lint
  • corepack pnpm run build
  • corepack pnpm test
  • git diff --check
  • semgrep scan --config p/default --error --metrics=off .
  • gitleaks protect --staged --redact
  • gitleaks detect --source . --redact --log-opts origin/main..HEAD

Notes:

  • Full test suite passed after the latest origin/main merge: 207 files, 2833 tests.
  • PR-range Gitleaks passed. A separate full-history scan surfaced historical baseline findings outside this PR commit range.

@wbugitlab1 wbugitlab1 merged commit 37e9921 into main Jun 19, 2026
2 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant