An AI-native IDE for running and repairing infrastructure — chat, an agent that proposes changes before it makes them, and terminals across your whole fleet at once.
Download KodarrSetup.exe
Check what you downloaded with
Get-FileHash .\KodarrSetup.exe -Algorithm SHA256 in PowerShell. If it does not
match, do not run it — tell us instead.
Before you run it
This installer is unsigned, and SmartScreen will warn you about it. That is expected rather than a sign something is wrong.
Code signing is deliberately deferred for this round. The certificate is real work and it was not worth blocking testers on, so it is weeks out rather than forgotten.
Two things that look like bugs
Extensions you install cannot use Kodarr’s server connections.
Extensions installed inside Kodarr run in their own sandbox. They have their own SSH, with their own credentials. If you install Codex, Claude Code or Kilo and ask about your servers, they will not reach them through Kodarr — that is not a setting you are missing.
You can hand one over deliberately: Lend on a connected node in the Kodarr panel. While it is lent, anything running as you can reach that node, so the status bar shows it the whole time and it stops when you revoke it or close Kodarr.
An untrusted folder puts Kodarr in limited mode.
Open a folder you have not trusted and Kodarr will not open a shell on a remote host, saying so rather than failing quietly. Trust the folder to enable panes. Reading the folder still works — that is the point of opening it.
If something is wrong
Screenshots beat descriptions, and the exact wording of any refusal beats both — the refusals are written to say which kind of “no” they are, so if one reads as broken that is worth knowing.