What exactly is Æfusio?
A local, privacy-first exporter that reads the chat transcripts AI tools already store on your machine, normalizes them into a unified schema, and writes them out in any of seven formats. Think of it as a universal adapter for AI conversation history.
Does it send my chats anywhere?
No. Æfusio has no network code in the export path. The desktop app reads files from disk and writes files to disk. The web version at aefusio.app uses the browser's File System Access API — your files never leave the tab. You can verify with any network inspector, or run with --offline (the default).
Which AI tools are supported?
See the Sources section for the full list. Dedicated parsers exist for GitHub Copilot Chat, Cline, Roo Code, Continue, Cody, Claude Code CLI, Codex CLI, and Aider. The generic fallback handles Xcode Intelligence, JetBrains AI, Zed, Warp, BoltAI, LM Studio, Jan, Msty, AnythingLLM, Perplexity, Raycast AI, ChatGPT desktop, Claude desktop, and any JSON/JSONL/SQLite store with a recognizable chat shape.
Why does macOS say the app is from an unidentified developer?
Apple Developer organization conversion is in progress (DUNS acquired, case open). Until we can notarize, first-launch requires right-click → Open. Alternatively:
xattr -d com.apple.quarantine /Applications/Aefusio.app
Windows code-signing via Azure Trusted Signing is also pending — SmartScreen will warn on first launch of the Windows build.
Can I export from ChatGPT.com or Claude.ai directly?
Not via scraping — Æfusio never automates your account. Instead, use the provider's built-in data export (ChatGPT Settings → Data Controls, Claude Privacy → Export, Google Takeout for Gemini). Unzip the export and run aefusio --path ./unzipped-export; Æfusio auto-detects the schema.
What's the difference between the desktop app and the web app?
The desktop app auto-discovers every supported source on your machine and exports in one click. Great for recurring use.
The web app at aefusio.app is a zero-install, drop-a-folder-in-the-browser alternative. It uses the File System Access API (Chrome / Edge / Brave / Opera / Arc) for directory access, falls back to file-picker elsewhere, and runs every parser client-side. Good for one-off exports, locked-down machines, or when you just want to try the tool.
What's in a “memory-bundle” export?
A single ZIP containing index.json (manifest: session IDs, sources, timestamps, sha256 hashes), sessions/<id>.md (one markdown per session), and screenshots/<hash>.png (deduplicated image attachments). Designed to be dropped back into another AI as project context, or archived for compliance.
Is Æfusio free and open source?
The binary is free to download and use. The source code is available on GitHub (going public alongside the v1.0 release). Licensing: commercial-friendly permissive license — the code will ship with LICENSE.md spelling it out.
Can I contribute a parser for <my favorite tool>?
Yes — that's the roadmap. Parser contributions go through a plugin interface (see ROADMAP.md). Open an issue with one or two sample transcript files and the target tool's storage path, and we'll add a parser.
Does Æfusio run on anything besides macOS?
Yes — Linux x86_64 and Windows x64 binaries ship via GitHub Actions. See Download. Apple Silicon is the current macOS default; a universal binary lands in v0.2.0.
How does it handle image attachments?
Pasted images inside chats are extracted to a screenshots/ sidecar directory and deduplicated by SHA-256. The markdown export references them relatively (), so the folder stays portable.
What about encrypted Electron chat stores (Claude desktop, ChatGPT desktop)?
Sandboxed Electron apps keep data in LevelDB / IndexedDB that Chromium encrypts with a per-profile key. Æfusio does not crack those stores — instead it picks up whatever JSON / SQLite is exposed alongside them (usually conversation caches). For complete Claude.ai / ChatGPT data, use the cloud data-export route described above.