Copilot Chat History Disappears After Browser Refresh: Safe Fix

Official documentation checked October 14, 2026.

If Copilot’s chat list becomes empty after refreshing the browser, first confirm the account and experience you are using. An empty sidebar is not proof that the conversations were deleted, and deleting browser databases is not a guaranteed recovery method.

Preserve any still-visible content through an approved private method before signing out or resetting anything. Do not create a public conversation-sharing link to back up confidential work.

Why Copilot Chat History Vanishes After a Browser Refresh

Different personal and organisational identities can show different histories. Microsoft describes saved conversations in its conversation history guide and the current Chat history guide. Start with the account used for the original conversation and open its Chats list.

A sign-in failure, an app change, a browser-specific display problem, or deletion may explain the symptom. The screenshot of an empty list alone does not distinguish them. Do not assume Copilot uses a particular IndexedDB database named copilot as the authoritative record of every chat.

Cookies can affect browser sessions. Microsoft’s Edge cookie guidance documents clearing cookies when the browser closes. That is different from refreshing a tab. Clearing cookies can sign you out; it does not establish that Copilot’s saved account history was erased.

Work records also have compliance storage rules. Microsoft’s Copilot retention documentation distinguishes messages visible in an AI app from backend retention and eDiscovery copies. Do not infer a 24-hour server deletion policy merely because a chat disappeared from view.

Steps to Prevent Copilot Chat History From Disappearing

1. Record the symptom. Note the chat title/date if known, last time it was visible, current time, browser version/profile, and whether the failure followed a refresh, browser close, sign-out, or app update. Keep an error message or a redacted screenshot.
2. Confirm the signed-in identity. Check the account in Copilot itself, not just the browser’s profile. A personal Microsoft account and a work account using a similar address are different identities. Use the account and tenant that created the conversation. Follow your organisation’s current approved Copilot entry point.
3. Open the history navigation. In the current Microsoft Copilot app, look for Chats on the left. If the sidebar is collapsed, expand it. Select an existing conversation if one is shown. Do not press Delete or clear activity history while troubleshooting a missing list.
4. Compare another supported session. Sign into the same account in an approved alternate browser/profile or the supported app. If history is visible there, preserve the result and focus on the affected browser. If it is absent everywhere, investigate account/product scope, actual deletion, or a service problem before changing browser storage.
5. Refresh sign-in once when needed. After preserving visible drafts, use normal sign-out and sign-in for the intended account, then reopen the history list. Complete only authentication requests you initiated. This can restore access to an existing session; it cannot be promised to restore deleted conversations.
6. Review browser cookie policy if sign-in does not persist. In current Edge, use Settings > Privacy, search, and services > Cookies to review site permissions, following the linked guide. Check clear-on-close settings separately. Prefer a limited, approved site setting over turning off all privacy controls. Managed settings should be reviewed by IT.

Chrome’s current cookie documentation describes Privacy and security > Third-party cookies and site-specific exceptions. InPrivate/Incognito sessions can behave differently. Do not use the malformed []copilot.microsoft.com pattern from older instructions or enable every third-party cookie as the default history fix.

If the actual error is license validation in a Microsoft 365 web app, Microsoft’s license validation guide discusses cookie requirements. Treat that as a separate diagnosed problem, and review the smallest supported browser change with IT. A missing-history symptom alone does not establish a license-cookie failure.

If Copilot Still Has Issues After the Main Fix

Only the affected browser shows an empty list

Keep the successful same-account comparison. Review that profile’s extensions and managed policies with support. If support recommends clearing this site’s cookies/data, preserve visible work first and confirm the history is accessible elsewhere. A targeted cleanup can remove sign-in/session state; it should not be described as guaranteed to rebuild every chat from the server. Do not directly delete an assumed IndexedDB database.

The problem began after the Copilot app changed

Identify the old and current app, account, and sign-in provider. Microsoft’s current personal-app privacy overview identifies the August 18, 2026 version boundary and separates organisational use. Give support those details rather than assuming a Microsoft 365 update reset retention to 24 hours.

Work history is missing in every client

Ask the administrator to check the actual service condition and applicable retention/deletion policy. Purview retention is not configured by an invented “Copilot > Chat history retention > 30 or 90 days” switch. Changing retention is a records decision and is not an automatic recovery operation. A retained compliance copy also does not guarantee that the original chat can be restored to the user’s sidebar.

Do not confuse saved chats with personalisation based on chat history. Microsoft’s personal-account controls and current Chat history guide describe separate memory/history choices. Turning a personalisation option on is not a recovery tool for a missing conversation.

Escalate with the account/product scope, times, error, and comparisons. Avoid deleting more evidence or promising that a browser setting can recover content already removed.