aiXplain's agentic coding environment — your terminal, your tools, your models.
Install · First run · Using it · Upgrading · Platforms · Configuration
Koder runs in your terminal, reads and edits the project you point it at, runs your tools, and works against the models in your aiXplain account.
-
Run any model — you're not tied to one vendor. Claude Code speaks only to Anthropic and Codex only to OpenAI. Koder runs on the full model catalogue in your aiXplain account from a single API key, or on any provider you bring — Anthropic, OpenAI, Google, OpenRouter, local models, and more. Change models mid-session without changing tools.
-
Bring your history with you. Coming from another tool?
koder importpulls your past sessions in from opencode, Claude Code, and Cursor, so you pick up where you left off instead of starting cold. -
One agent, wherever you work. The same Koder runs as a fast terminal TUI, a headless server (
koder serve) for scripts and CI, a browser interface (koder web), and a desktop app. -
Built to extend. Connect MCP servers for extra tools and data, run specialized subagents in parallel, and switch between agents with a single keypress.
-
Yours to run. Open source under MIT, shipped as one signed-and-notarized binary that installs without root. Your API keys and session history stay on your machine.
curl -fsSL https://github.com/aixplain/koder/releases/latest/download/install | bashOpen a new terminal afterwards, then run koder from inside a project:
cd ~/your-project
koderThe installer drops a single binary in ~/.koder/bin and adds that directory to your
shell's PATH. It does not need root, and it touches nothing else.
To install a specific version, or to skip the PATH edit:
curl -fsSL https://github.com/aixplain/koder/releases/latest/download/install | bash -s -- --version 0.2.4
curl -fsSL https://github.com/aixplain/koder/releases/latest/download/install | bash -s -- --no-modify-pathKoder asks for an aiXplain API key the first time it starts.
Sign in at app.aixplain.com, open Integrations → API keys, create a key and paste it in. That single key unlocks the model catalogue on your account. It is stored under your home directory, never in your project.
If you would rather use a different provider, choose Use a different provider on the
same screen, or run koder providers later.
Start Koder in a project and describe what you want in plain language. It reads the files it needs, proposes edits, and runs commands when you let it.
A few things worth knowing early:
tab |
switch agents |
ctrl+p |
command palette |
koder run "…" |
one-shot: answer and exit, useful in scripts |
koder import |
bring sessions over from opencode, Claude Code, or Cursor |
koder models |
list the models available to your account |
koder stats |
token usage and spend so far |
Other commands: koder agent manages agents, koder mcp manages MCP servers,
koder serve starts a headless server, and koder web opens the browser interface.
Run koder --help for the full list.
koder upgrade # move to the newest release
koder upgrade 0.2.4 # or a specific one
koder uninstall # remove the binary and everything under ~/.koderkoder upgrade re-runs the installer for the version you asked for, so it follows the
same path as a fresh install.
| Platform | Architectures |
|---|---|
| macOS | Apple Silicon (arm64), Intel (x64) |
| Linux | x64, arm64 |
| Windows | x64 |
macOS 12 or later. On Windows, download koder-windows-x64.tar.gz from the
releases page and put koder.exe
somewhere on your PATH; the shell installer above is for macOS and Linux.
macOS builds are signed with aiXplain's Developer ID certificate and notarized by Apple, so they run without a Gatekeeper prompt. You can confirm that yourself:
spctl --assess --type install -vv ~/.koder/bin/koder
# koder: accepted
# source=Notarized Developer ID
# origin=Developer ID Application: aiXplain, Inc. (U6RQVYMH8L)To check an archive against the checksum on its release:
shasum -a 256 koder-darwin-arm64.tar.gzThe command was renamed to koder. The old names — aixplain-code, aixplain and
aiXplain — still work and point at the same binary, so existing scripts and muscle
memory keep working. Release archives are published under both names for the same
reason.
~/.koder/bin |
the binary and its command aliases |
~/.config/koder/koder.json |
configuration |
~/.local/share/koder |
logs, credentials and local state |
~/.cache/koder |
downloaded tooling |
KODER_RELEASE_REPO |
install and upgrade from a different repository |
KODER_DIST_URL |
install and upgrade from a mirror instead of GitHub |
