Answer: In interactive Copilot CLI sessions, depending on your permission settings, Copilot can prompt you to approve storing a memory or rating an existing memory's usefulness. You can approve the update once, reject it with optional feedback, or choose to allow future memory updates without asking. Status: Confirmed Entry: tool/github-copilot/memory-and-context/approve-memory-updates-cli Revision: 3 Digest: sha256:792b9bf11f258a9f (changes whenever the content changes) Timeline: Created: 2026-11-13T03:30:57Z Last changed: 2026-11-18T13:07:52Z (approval scope: The approval option states whether it applies to the current repository, directory, or session → whether it applies to the current repository, directory, or session) Last verified: 2026-11-20T13:12:08Z Next check: 2026-11-21T13:12:08Z Check interval: Daily Expected change: No fixed schedule Data: Field | Value | Source | As of approval options | approve the update once, reject it with optional feedback, or choose to allow future memory updates without asking | [1] | 2026-11-20 when prompted | In interactive sessions, depending on your permission settings | [1] | 2026-11-20 prompt contents | The prompt shows the memory and whether it applies to you or is shared with repository collaborators | [1] | 2026-11-20 approval scope | whether it applies to the current repository, directory, or session | [1] | 2026-11-20 Sources: [1] GitHub. "Manually creating memories for GitHub Copilot - GitHub Docs". https://docs.github.com/en/copilot/how-tos/use-copilot-agents/copilot-memory/create-memories Role: primary. Accessed: 2026-11-20T13:12:08Z Quote: "You can approve the update once, reject it with optional feedback, or choose to allow future memory updates without asking." (Supports: approval options) Quote: "In interactive sessions, depending on your permission settings, Copilot can ask you to approve storing a memory or rating an existing memory's usefulness." (Supports: when prompted) Quote: "The prompt shows the memory and whether it applies to you or is shared with repository collaborators." (Supports: prompt contents) Quote: "The approval option states whether it applies to the current repository, directory, or session." (Supports: approval scope) Snapshot SHA-256: 3c2e8fa7cfb23f00224d6b4caf6bb8d1d264e2d24416fdea8ef991ec8a9582f2 (captured 2026-11-18T13:07:51Z) Verification: Method: Automated extraction from [1] with deepseek-flash (JSON output, thinking disabled). Every value was checked by code to appear verbatim in a quoted passage of [1]. On this check the text of [1] was unchanged since 2026-11-18T13:07:52Z, so the values verified then were kept. Cross-check: not-available at 2026-11-20T13:12:08Z. No independent second source is configured for this entry Last successful check: 2026-11-20T13:12:08Z Last attempt: 2026-11-20T13:12:08Z Notes and limitations: Extracted automatically from a single official source (section "Approving memory updates in Copilot CLI"). Related: https://latestn.com/tool/github-copilot/memory-and-context/ask-copilot-to-remember-fact How do I ask GitHub Copilot to remember a fact or preference? https://latestn.com/tool/github-copilot/memory-and-context/attach-repository-in-chat How do I attach a repository in GitHub Copilot Chat to give it repository context? https://latestn.com/tool/github-copilot/memory-and-context/check-context-usage How do I check my context usage in GitHub Copilot? https://latestn.com/tool/github-copilot/memory-and-context/add-repository-custom-instructions How do I add repository custom instructions for GitHub Copilot in my IDE? https://latestn.com/tool/github-copilot/memory-and-context/add-repository-custom-instructions-2 How do I add repository custom instructions for GitHub Copilot? https://latestn.com/tool/github-copilot/memory-and-context/apply-custom-instructions-agent How do I apply my repository's custom instructions to a custom agent in GitHub Copilot CLI? https://latestn.com/tool/ All entries in AI tools Change log: Time | Event | Change | Source 2026-11-18T13:07:52Z | changed | approval scope: The approval option states whether it applies to the current repository, directory, or session → whether it applies to the current repository, directory, or session | [1] 2026-11-16T12:56:13Z | changed | approval scope: — → The approval option states whether it applies to the current repository, directory, or session | [1] 2026-11-16T12:56:13Z | changed | prompt contents: — → The prompt shows the memory and whether it applies to you or is shared with repository collaborators | [1] 2026-11-16T12:56:13Z | changed | when prompted: — → In interactive sessions, depending on your permission settings | [1] 2026-11-16T12:56:13Z | changed | approval options: — → approve the update once, reject it with optional feedback, or choose to allow future memory updates without asking | [1] 2026-11-16T12:56:13Z | changed | Approval scope: The approval option states whether it applies to the current repository, directory, or session. → — | [1] 2026-11-16T12:56:13Z | changed | Prompt contents: The prompt shows the memory and whether it applies to you or is shared with repository collaborators. → — | [1] 2026-11-16T12:56:13Z | changed | When prompted: In interactive sessions, depending on your permission settings → — | [1] 2026-11-16T12:56:13Z | changed | Approval options: approve the update once, reject it with optional feedback, or choose to allow future memory updates without asking → — | [1] 2026-11-13T03:30:57Z | added | Entry created | — Changes for this entry as a feed: https://latestn.com/tool/github-copilot/memory-and-context/approve-memory-updates-cli/latest Challenge this entry: Open challenges: None How: If a value here is wrong or out of date, send what is wrong and a link to evidence. Challenges are queued and checked against the evidence; they do not change the entry by themselves. If the entry changes as a result, the change log says so. Form: https://latestn.com/dispute/tool/github-copilot/memory-and-context/approve-memory-updates-cli POST: https://latestn.com/dispute/tool/github-copilot/memory-and-context/approve-memory-updates-cli with claim, evidence_url, and optionally field and contact (form-encoded or JSON) GET: https://latestn.com/dispute/tool/github-copilot/memory-and-context/approve-memory-updates-cli?claim={what is wrong}&evidence_url={link} How to cite: LatestN. (2026). How do I approve memory updates in GitHub Copilot CLI? Revision 3, last verified 2026-11-20T13:12:08Z. https://latestn.com/tool/github-copilot/memory-and-context/approve-memory-updates-cli (accessed 2026-11-21T09:53:04Z). @misc{LatestN_tool_github_copilot_memory_and_context_approve_memory_updates_cli_r3, title = {How do I approve memory updates in GitHub Copilot CLI?}, author = {{LatestN}}, year = {2026}, howpublished = {\url{https://latestn.com/tool/github-copilot/memory-and-context/approve-memory-updates-cli}}, note = {Revision 3; digest sha256:792b9bf11f258a9f; last verified 2026-11-20T13:12:08Z; accessed 2026-11-21T09:53:04Z} } Reuse: License: CC BY 4.0 (https://creativecommons.org/licenses/by/4.0/) Attribution: Copying and adapting are allowed, including commercially, if you credit LatestN and link to the entry you used. Each entry ends with a ready-made citation. URL: https://latestn.com/tool/github-copilot/memory-and-context/approve-memory-updates-cli