Web Exporter · 100% Client-Side

Drop your chats. Get a clean export, in 10 seconds.

No upload. No account. No telemetry.
Every byte you drop stays in your browser tab.

Drop your AI chat files or folder

Æfusio recognizes dozens of AI chat stores — VS Code extensions (GitHub Copilot Chat, Cline, Roo Code, Kilo Code, Continue, Cody, plus Augment · Supermaven · Blackbox · PearAI · Bito), terminal agents (Claude Code, Codex, Gemini CLI, Aider, llm, ShellGPT), IDEs (Xcode Intelligence, JetBrains AI / Junie, Zed Assistant, Neovim plugins), desktop apps (Claude · ChatGPT · Perplexity · Warp AI · Raycast AI · LM Studio · Jan · Msty · AnythingLLM · BoltAI), and cloud data-export folders (Claude.ai · ChatGPT · Gemini Takeout). Unknown formats fall through to a generic JSON / JSONL / SQLite parser. Pick the folder, drop it here, hit export.

📁

Drop a folder or files here

…or pick one below. Everything stays in your browser.

Tips — try dropping one of these paths:
~/.claude/projects/  ·  ~/.codex/sessions/
~/Library/Application Support/Code/User/workspaceStorage/ (macOS)
%APPDATA%\Code\User\workspaceStorage\ (Windows)

Three steps. Zero servers.

Drop

Drag in a folder or pick individual files. Æfusio reads them locally using the browser's File System APIs — your files never travel over the network.

Parse

Tiered parsers run in-page: Claude Code · Codex · Gemini CLI · Aider for .jsonl transcripts; VS Code SQLite stores (Copilot Chat, Cline, Roo, Continue, Cody); Xcode, JetBrains, Zed, Warp, BoltAI, LM Studio, Jan, Msty via generic JSON+SQLite walkers; plus cloud data-export ZIPs from Claude.ai, ChatGPT, and Gemini Takeout.

Export

Choose a format (markdown, jsonl, json, txt, csv, openai-messages, or memory-bundle), merge or keep separate, and download. Screenshots go into a deduped screenshots/ sidecar inside the zip.

Quick answers

Which folder should I drop in?

Point Æfusio at the parent directory of your AI tool's storage. Safe defaults:

  • VS Code extensions~/Library/Application Support/Code/User/workspaceStorage/ (macOS), ~/.config/Code/User/workspaceStorage/ (Linux), %APPDATA%\Code\User\workspaceStorage\ (Windows).
  • Claude Code CLI~/.claude/projects/
  • OpenAI Codex CLI~/.codex/
  • Claude.ai / ChatGPT data export — the unzipped export folder (looks for conversations.json).
  • Gemini Takeout — the unzipped Takeout folder (finds My Activity/Gemini Apps/MyActivity.json).

When in doubt, drop your entire home folder. The walker is cheap and skips files over 50 MB.

What output format should I pick?

Markdown — default, human-readable, Obsidian-ready.

JSONL — pipe into LLM fine-tuning or analytics.

JSON — one file, easy to script against.

OpenAI messages{role, content} arrays, compatible with chat-completions APIs.

Memory bundle — ZIP with manifest + per-session markdown + deduped screenshots. Good for handing back to another AI as project context.

Does anything get uploaded?

No. This page is static HTML/JS served from nginx. Every parser runs in your browser tab. The only network calls are the initial page load, Google Fonts, and the CDN fetches for sql.js (pinned + SRI-hashed) and JSZip (pinned + SRI-hashed). Your files never leave the tab — verify with your browser's Network tab.

Which browsers work best?

Directory access (drop a whole folder) requires the File System Access API: Chrome 86+, Edge 86+, Brave, Opera, Arc. Safari and Firefox fall back to multi-file picker mode — same results, just a less polished UX.

My tool isn't recognized — what now?

First try the generic walker: just drop the folder. If that doesn't pull turns, open an issue on GitHub with a sample file (redact anything sensitive) and the tool's storage path. Adding a dedicated parser typically takes less than a day.

What Æfusio supports — across every surface

Æfusio ships as a desktop app, a CLI, and this web exporter. They share the same parsers, writers, run-log, and README handoff. The matrix below is the authoritative cross-surface parity snapshot — re-rendered straight from the same data the release pipeline checks against.