store_memory consistently fails with 'Unable to store memory' since ~Feb 13 #1751
Description
Bug: store_memory consistently returns "Unable to store memory"
Environment
- Copilot CLI version: 0.0.420
- OS: Windows 11
- Model: Claude Opus 4.6
Description
The store_memory tool consistently fails with: "Unable to store memory. You can continue with your task without storing this information."
Reading previously stored memories works fine - the <repository_memories> section loads 15+ facts at session start. Only writing new memories fails.
Timeline
| Timeframe | Result |
|---|---|
| Early Feb 2026 | Success (multiple repos) |
| Mid Feb 2026 | Last known success |
| Late Feb 2026 | Failed |
| Mar 1, 2026 | Failed (4+ attempts across 2 sessions) |
What I've verified
- No local config issue (no memory-related settings in
~/.copilot/config.json) - No local storage issue (memories are server-side, not in
session-store.db) - All other API-dependent tools work (gh CLI, task agents, SQL, LSP)
- Authentication is working
- CLI is current version (0.0.420)
Expected behavior
store_memory should persist facts to the repository-scoped memory store, returning a success confirmation.
Actual behavior
Every call returns "Unable to store memory. You can continue with your task without storing this information." with no additional error detail.
Impact
Without working memory storage, the agent cannot learn from mistakes across sessions. This means:
- Important conventions must be re-explained each session
- Bug patterns that should be remembered get forgotten
- User preferences don't persist unless manually added to instruction files
Related issues
- Subagent Tried to Call
store_memoryAnd Failed. Should They Have Had the Tool? #1108 - Subagent store_memory failures (similar symptom, different context)