Before exporting
- Use a current Chrome or Chromium-based Edge build.
- Sign in to Teams on the web.
- Open the conversation itself, not the Files tab.
- Wait for visible messages to load.
- Keep the tab open and do not switch chats during export.
The extension cannot detect the chat
It runs only on teams.cloud.microsoft and teams.microsoft.com. Reload the tab, reopen the personal or group conversation, wait for messages, and try again. Channel posts are outside version 0.1.0 scope.
A long history stops
The exporter uses a bounded completeness check and refuses to make a partial ZIP when it cannot confirm the beginning. Retry with the tab in the foreground. Report repeatable failures with the extension version, browser version, domain, approximate message count, and non-sensitive test steps.
Some files are missing
Open attachments-report.csv and failed-attachments.html. Permission loss, deletion, expired URLs, viewer/sign-in HTML, Conditional Access, CORS, and size limits can prevent inclusion. Use the original link while signed in when policy allows manual download.
The ZIP did not download
Use the persistent Download ZIP button in the progress panel. Check browser download settings, hidden save dialogs, disk space, and endpoint security controls. Do not reload the tab before saving.
Cancellation
Cancellation stops capture and file requests. No partial ZIP is produced. Start a new export to retry.
Report an issue safely
Open a GitHub issue with the extension version, browser and OS, Teams domain, chat type, approximate counts, exact error, and non-sensitive reproduction. Never attach a real archive, signed file URL, token, email address, or confidential screenshot.
Send security or privacy reports privately to 646826@gmail.com.
Inspect the implementation
Tests, selectors, permissions, and release validation are public.