Kratt Code: the 5-minute guide
An agentic coding assistant in your terminal, powered by your Kratt account.
1. Install
You need Node.js 18+. Then one command:
npm install -g https://krattlabs.eu/kratt-code.tgz
Open a terminal in any project folder and type kratt. The first time, it opens your
browser to log in with your Kratt account, no API keys, ever. It then takes a quick read-only look at
your project and tells you what it sees.
2. Just type what you want
There is nothing to memorize. Describe the outcome, in your own words:
› explain what this project does › find and fix the bug that makes login fail on Safari › add tests for parseUser and run them › @src/app.js why is this file so slow?
@path/to/filepulls a file into the conversation (Tab completes paths). Screenshots work too:@error.png.- Plain words do the obvious thing:
undo,diff,help,exit, no slash needed. !commandruns a shell command directly, without asking the AI.
3. It asks before changing anything
Kratt reads and searches your project freely, but before it edits a file or runs a command it shows you exactly what will happen, including a diff, and waits:
Edit src/utils.js?
❯ Yes
Yes, and don't ask again
No
Want it to move faster? Press ⇧Tab (or type /auto) to change autonomy:
| Mode | What it means |
|---|---|
| 🟢 Asks first | Review every edit and command (default) |
| 🟡 Auto-accept edits | Applies file edits itself, still asks before commands |
| 🔴 Full auto | Runs everything without asking |
Genuinely dangerous commands (rm -rf, force-push, sudo…) always ask, even in
full auto. After every task you get a recap of changed files, diff to review,
undo to revert.
4. The features you'll actually use
| Say / type | What happens |
|---|---|
/verify | Detects your test/build command, runs it, and fixes failures |
/commit | Stages changes and writes a proper commit message from the diff |
/think | Deeper reasoning for gnarly problems (slower, smarter) |
/resume | Reopen a past session, synced across your machines |
/init | Writes a KRATT.md so Kratt understands your project's conventions |
/theme green | Pick your accent color |
kratt "fix the failing test" | One-shot from your shell, runs the task and exits |
kratt -c | Continue the most recent chat in this folder |
5. Staying up to date
Kratt Code updates itself in the background whenever you launch it. You can also run
kratt update manually. Check your version with kratt -v.
Troubleshooting
- “Kratt Code needs Node.js 18 or newer”: install the LTS from nodejs.org, then reinstall.
- Login didn't open a browser? Copy the printed link into any browser where you're logged in to Kratt.
- Signed in on the wrong account?
/logoutthen/login. - Anything else: krattlabs@proton.me.