Request: a supported way to suppress one info line.
The problem
With "memory": false in ~/.copilot/settings.json, every new session prints one info line:
Memory is disabled. Use /memory on to re-enable.
No setting turns that line off. showTipsOnStartup controls startup tips, and notifications controls operating-system notifications. Neither one suppresses this notice. The documented settings include no general toggle for notices or hints.
Why I will not re-enable memory
I intentionally keep memory disabled and do not plan to re-enable it. The repeated suggestion is therefore not useful to me. The choice is settled for two reasons.
First, the current controls do not let me fully review and delete stored memories. Deletion is not exposed. Downvoting is the only control available, and it keeps entries rather than removing them. After enough entries accumulate, the memory settings page no longer lists every stored memory. Related: #2278, #1443, #1719.
Second, cross-session recall is itself what I want to avoid. The CLI describes the setting as "whether to enable agentic memory (cross-session fact recall)". Some facts hold only within one session: a path, a branch, a workaround, or a transient decision. Memory routinely carries them into unrelated later sessions. Related: #3945.
Why no workaround exists
In 1.0.77 the notice is emitted once per session. The set that suppresses repeats lives only for the current session, so the line returns in the next one. The setting itself is the only condition on the notice.
Minified source of the notice (1.0.77)
Identifiers below come from the shipped bundle, not from the original source names.
function wfn(t,e,n){ let r=useRef(new Set), o=useRef(n); o.current=n;
useEffect(()=>{
t.memory===false && (r.current.has(e) || (r.current.add(e),
o.current({type:"info", text:"Memory is disabled. Use /memory on to re-enable."})))
},[t.memory,e]) }
The call site is wfn(An, ae.sessionId, mi).
Requested outcome
The CLI should not repeat this notice in every session after a user has explicitly set memory to false. Any of these would achieve that:
- Do not emit the notice when
memory is explicitly false. A reminder is unnecessary after an explicit opt-out. It may still be useful when memory is off by default.
- Persist a one-shot flag.
appTipShown and initTipSuppressed already persist similar state.
- Accept a suppression setting. An adjacent notice already accepts
gt.suppressInitFolders.
Context
Request: a supported way to suppress one info line.
The problem
With
"memory": falsein~/.copilot/settings.json, every new session prints one info line:No setting turns that line off.
showTipsOnStartupcontrols startup tips, andnotificationscontrols operating-system notifications. Neither one suppresses this notice. The documented settings include no general toggle for notices or hints.Why I will not re-enable memory
I intentionally keep memory disabled and do not plan to re-enable it. The repeated suggestion is therefore not useful to me. The choice is settled for two reasons.
First, the current controls do not let me fully review and delete stored memories. Deletion is not exposed. Downvoting is the only control available, and it keeps entries rather than removing them. After enough entries accumulate, the memory settings page no longer lists every stored memory. Related: #2278, #1443, #1719.
Second, cross-session recall is itself what I want to avoid. The CLI describes the setting as "whether to enable agentic memory (cross-session fact recall)". Some facts hold only within one session: a path, a branch, a workaround, or a transient decision. Memory routinely carries them into unrelated later sessions. Related: #3945.
Why no workaround exists
In 1.0.77 the notice is emitted once per session. The set that suppresses repeats lives only for the current session, so the line returns in the next one. The setting itself is the only condition on the notice.
Minified source of the notice (1.0.77)
Identifiers below come from the shipped bundle, not from the original source names.
The call site is
wfn(An, ae.sessionId, mi).Requested outcome
The CLI should not repeat this notice in every session after a user has explicitly set
memorytofalse. Any of these would achieve that:memoryis explicitlyfalse. A reminder is unnecessary after an explicit opt-out. It may still be useful when memory is off by default.appTipShownandinitTipSuppressedalready persist similar state.gt.suppressInitFolders.Context
~/.copilot/settings.jsoncontains"memory": false/memoryoutput, not this notice.