ThreadAtlas is a Chrome/Edge Manifest V3 extension focused on long-form chat navigation, workspace organization, export, and local IDE context bridging.
The product is intentionally ChatGPT-first. Gemini, Claude, and Grok remain supported for export-oriented flows, but the richer workspace features are built primarily for ChatGPT conversation pages.
- Right-side timeline for long conversations
- Active round tracking while scrolling
flow/jumpscroll modes- Timeline-side quick preview and export entry points
- Archived-history windowing so long threads stay lighter without losing jump targets
- Sidebar folders inside the native ChatGPT sidebar
- Prompt Vault
- Title updater
- Sidebar auto-hide
- Folder spacing control
- Markdown patcher
- Snow effect
- History cleaner policy controls
- In-page export panel with turn selection
- Formats:
txt,md,png,pdf,doc,html,json,xls,csv
- Reads the current VSCode workspace through a local extension
- Surfaces active file, current selection, dirty files, diagnostics, and git summary
- Shows a compact VSCode context bar above the ChatGPT composer
- Auto-attaches only unsent context blocks when you send a message
- Does not require the OpenAI API
chatgpt.comchat.openai.comgemini.google.comclaude.ai*.claude.aigrok.com*.grok.com
Current product focus:
- ChatGPT: timeline, folders, archived-history recovery, composer-side VSCode context
- Gemini / Claude / Grok: export-first support
Use this if you just want chat navigation, folders, and export:
- Open a supported chat page.
- Use the popup to configure timeline, reading, export, and local sync settings.
- Use the in-page timeline and workspace UI on the chat page.
Use this if you want ChatGPT Web to reuse your current VSCode context:
- Run the VSCode bridge from
integrations/vscode-threadatlas. - Enable
本地同步in the browser extension popup. - Open a real ChatGPT conversation page such as
https://chatgpt.com/c/<conversation-id>. - The composer shows a VSCode context bar when the local bridge is online.
- If you have a selection in VSCode, that selection becomes the default reference block.
- When you send a message, ThreadAtlas asks the local bridge for unsent context only, then marks those blocks as sent for the current conversation.
- Open:
- Chrome:
chrome://extensions - Edge:
edge://extensions
- Chrome:
- Enable
Developer mode - Click
Load unpacked - Select this project directory
- Open
integrations/vscode-threadatlasin VSCode. - Press
F5to run it in an Extension Development Host. - Keep the bridge port aligned with the popup setting in ThreadAtlas.
Optional packaging:
cd integrations/vscode-threadatlas
npx @vscode/vsce package./scripts/build-crx.shOutputs:
dist/threadatlas.zipdist/threadatlas.crx
Optional environment variables:
CHROME_BIN=/path/to/chromeKEY_PATH=/path/to/private-key.pem
The bridge folder can be zipped or packaged separately. For quick local verification, the repository also supports creating preview zips during validation.
manifest.jsonsrc/content-script.jssrc/service-worker.jssrc/popup.htmlsrc/popup.csssrc/popup.jssrc/timeline-feature.jssrc/folder-feature.jssrc/history-archive-controller.jssrc/history-cleaner-feature.jssrc/context-sync-feature.jssrc/styles.cssintegrations/vscode-threadatlas/package.jsonintegrations/vscode-threadatlas/extension.js
- ChatGPT DOMs change frequently, so selectors and mount points still need maintenance.
- Real browser interaction still requires page-level verification after UI changes.
- VSCode Bridge only exposes local context over
127.0.0.1; it is not a remote sync service. - Sent-context de-dup is scoped per conversation and based on item identity/content hash, not semantic diffing.