About
What CODEXT is, and why it exists
AI models are only as useful as the context you give them. The problem isn't the models — it's the workflow. You copy a file. Paste it in. The AI asks a question about another file. You copy that one. Repeat. You're doing data entry, not engineering.
CODEXT fixes this by giving you one command: drop your project folder. Get one structured .txt file with your entire codebase — file tree, contents, metadata. Paste it into any AI. Done. The AI now has full context. You can do real work.
Manifesto
The principles behind every decision
01
Your code never leaves your machine
CODEXT reads files from your local filesystem and writes output to your local filesystem. There is no upload step. There is no sync step. There is no "processing in the cloud." The only time CODEXT touches a network connection is when you explicitly use the GitHub clone feature — and even then, the clone lands in your local temp folder, not our servers.
02
No account. No identity. No profile.
You download CODEXT and it works. There is no sign-up screen, no email confirmation, no OAuth flow for the app itself. Pro licenses are activated with a key. That's it. We don't know who you are, what projects you work on, or how often you use the app. We can't — that data doesn't exist on our end.
03
The output format is a plain .txt file
We deliberately chose .txt over a proprietary format, a JSON schema, or a binary blob. A .txt file is readable in any editor, pasteable into any AI, transferable to any colleague, and versionable in any git repo. If CODEXT disappears tomorrow, your workflow survives intact. No migration needed.
04
AI portability is a feature, not a bug
The AI landscape shifts constantly. Models that are state-of-the-art today will be commoditized in 12 months. CODEXT produces a file that works with Claude, GPT-4, Gemini, Mistral, and every local LLM you can run on your hardware. You're not locked to any model, any provider, or any API. Your context is yours.
05
One-time payment because SaaS doesn't fit
A codebase bundler that runs locally doesn't need a subscription. There's no server to maintain, no bandwidth to pay for, no per-user overhead. We charge $12 once because that's the honest model for a tool that does its work entirely on your machine. Future v1.x updates are included.
06
Developer trust is the product
Every other choice in this product — Rust for performance and memory safety, Tauri over Electron, local storage over cloud sync, plain text over proprietary format — is a consequence of this principle. We are building a tool that developers can trust with their most sensitive asset: their source code.
Stack
Built with deliberate choices
Every technology was chosen for a reason. Here's the reasoning.
Core
Rust
Memory safety, no runtime, native performance. Handles large monorepos without the overhead of GC pauses.
Desktop shell
Tauri
Uses the OS WebView instead of bundling Chromium. Smaller binary, better integration, no Electron overhead.
Output format
Plain .txt
Readable in any editor. Pasteable into any AI. No migration cost. No vendor dependency. Versionable in git.
Payments
Polar
Developer-focused payment processor. Clean API, honest pricing, no dark patterns. License delivery is instant.
Web
Next.js + Vercel
The marketing site only. The app itself has no web dependency — it bundles to a self-contained binary.
Storage
Local only
Settings, license token, GitHub token — all stored in the OS app data directory. Nothing synced. Nothing transmitted.
Local-first. Developer-owned.
No compromises.
Read the security details, or just download it and see for yourself.
Nothing is uploaded. Nothing is tracked. It just works.