-
Notifications
You must be signed in to change notification settings - Fork 0
Frequently asked questions about Export2AI, AI-ready zip archives, Cursor/VS Code project handoff, ChatGPT project uploads, Claude code review context, and offline token estimates.
No. Export2AI creates a source context archive for AI analysis. It intentionally omits local Git internals, credentials, dependency caches, generated output, and other machine-local noise.
Use Git, proper backups, or artifact storage for backups.
No. Export2AI writes a local zip file and optionally copies its path to your clipboard. Token estimates are calculated offline. You choose whether and where to upload the resulting archive.
No. Token counting is local. No OpenAI, Anthropic, Google, xAI, DeepSeek, Mistral, or other provider API call is made.
~ means approximate. OpenAI/ChatGPT model families supported by gpt-tokenizer display exact offline counts. Claude and unknown families use approximate local methods.
See Token Estimates & AI Model Support.
Because local .git/ internals contain machine-local repository state, remotes, refs, hooks, object databases, local history, and possible credentials. Export2AI keeps useful repository-control files but omits unsafe .git/ internals.
They are repository-control context. AI agents and tests often need CI workflows, Dependabot config, ignore rules, and repository validation files. Soft-delete preserves those while still blocking actual credential material.
They are usually huge, generated, and not useful for LLM context. Source files, lockfiles, docs, tests, and config usually provide better AI review context.
Yes. Use Export2AI: Manage Built-in Exclude Patterns to disable a built-in pattern, or tune export2ai.excludePatterns and export2ai.excludePaths.
Be careful with dependency folders and generated output: they can make the zip large and less useful.
Yes.
{
"export2ai.excludePatterns": ["coverage", "*.sqlite"],
"export2ai.excludePaths": ["fixtures/private-data"]
}Usually no. Comments often contain rationale, warnings, and maintenance knowledge that AI agents need. Enable export2ai.removeComments only when smaller context is more important than readability.
Zip compression level 9 is already the default and only affects upload byte size. export2ai.compressCode removes whitespace from exported text and can harm readability; keep it off unless you accept that tradeoff.
They are off by default:
"export2ai.showExplorerTokenBadges": falseThe status bar and zip notification still show token estimates.
Yes. Use Copy Project Structure. It can output plaintext, Markdown, or XML based on export2ai.outputFormat.
Yes. Right-click one file and choose Export2AI: Copy Content to Clipboard. It copies exact UTF-8 text without zip processing, comment stripping, or whitespace compression.
The zip is written to the workspace root, even if you export a nested folder.
Yes.
"export2ai.llmModel": "claude-opus-4-8"The model affects token estimates, menu display, zip filenames, notifications, and manifest text.
Upload the generated *-context-*.zip file. In your prompt, tell the AI it is an Export2AI context archive and to read _EXPORT2AI_MANIFEST.txt, README.md, and AGENTS.md first when present.
Export2AI · AI-ready zip archives for VS Code, Cursor, ChatGPT, Claude, and LLM coding agents.
Repository · README · Releases · Open VSX · GPL-3.0-only
Export2AI Wiki
Start
Safety & AI Context
- 🛡️ Safe Exports & Excludes
- 🌿 Git Metadata Soft-Delete
- 🧮 Token Estimates & AI Model Support
- 🧹 Comment Stripping & Compression
Configuration & Support
Contributors