+ 
What is it, really?
+Think of a very capable junior developer who lives in your terminal.
+You describe a job in plain language. korgex looks through your project, figures out a plan, edits the right files, runs the tests to check it worked, and tells you exactly what it did. You stay in control — it can ask before making big changes, and you can undo anything.
+The twist that nothing else has: everything it does is written down in a way that can’t be quietly changed later. That’s the “receipts.”
+The big idea: AI you can check, not just trust
+Most AI tools ask you to take their word for it. korgex gives you proof.
+As it works, korgex keeps a logbook. Every step — every file it read, every command it ran — is sealed to the step before it, like links in a chain. If anyone later changes, removes, or reorders even one entry, the chain visibly breaks and korgex points to exactly where.
+ +Why care? Audits, compliance, debugging, or just peace of mind — you get honest, checkable proof of what the AI actually did, instead of hoping it behaved.
+What it can do
+The everyday stuff, plus a few things no other coding assistant offers.
+Writes & fixes code
Reads your project, makes the change, and edits the exact lines — not a wall of copy-paste.
Runs your tests
It checks its own work by running your test suite, so you get changes that actually pass.
Any AI you like
Claude, ChatGPT, Gemini, Grok, or a private model on your own computer. Switch anytime — no lock-in.
Keeps the receipts
A tamper-evident record of every step you can verify later with one command.
Plugs into your tools
Connects to GitHub, your files, databases and more through open “MCP” connectors.
Undo anything
A rewind log lets you roll files back to before any step. Nothing is one-way.
Try it in 60 seconds
+If you can open a terminal, you can run korgex.
+Install it
+One line. (Needs Python 3.10 or newer.)
+pip install -U korgex+
Connect an AI
+Run korgex setup and paste a key from whichever provider you use — or set one and go.
export ANTHROPIC_API_KEY="…" # or OPENAI_API_KEY, or a local model+
Ask for something — then check the receipt
+Describe the job in plain words. When it’s done, prove the run wasn’t altered.
+$ korgex "add a /healthz endpoint that returns 200 with uptime" +➤ Read(routes.py) ➤ Edit(routes.py) ➤ Bash(pytest -q) +✓ Added GET /healthz returning {"status":"ok","uptime_seconds":…} — tests pass + +$ korgex verify +✓ record intact — 7 steps, chain verified end-to-end+
Is it safe to let it loose?
+It’s built cautious. The powerful stuff is off until you turn it on.
+Big or sensitive changes show you a diff and wait for your “yes.”
A built-in guard refuses obviously destructive shell commands — and records that it did.
When it executes code for you, it can be boxed off from your network and files.
An optional guard flags secrets or large data trying to leave your machine.
Why people choose it
+Two reasons, in plain terms. You’re never locked to one AI company — korgex speaks to all the major ones and to private models, so you can pick the best (or cheapest) for the job and switch whenever. And you can prove what happened — the checkable record means you don’t have to take an AI’s word for anything. As far as we know, no other coding assistant gives you that.
+