Fix a failing test
Run the suite, read the failure, repair the code, and prove it passes.
Read the guide →iCode Agent · Terminal
iCode Agent works directly in your repository: it reads the code, makes changes, runs your tests, and verifies its own work — while you watch and steer it in your terminal. Long tasks are the hard case, and context is a budget it defends.
npm install -g @icodehq/icode-agent cd ~/my-project icode-agent
Node.js 22+ · Apache-2.0 · One package for Windows, macOS, and Linux
An illustrative session showing the explore → change → verify loop. Walk through your own first task →
Running a long task is where coding agents fall apart: the window fills with old file reads and command output, the agent starts forgetting what it did, and every request costs more. iCode Agent treats context as a budget to defend, not a bucket to fill.
A withheld result keeps a route back to the full output, failure evidence is never hidden, and reduction never rewrites your saved session.
Run the suite, read the failure, repair the code, and prove it passes.
Read the guide →Map the callers, then make a focused refactor with reviewed diffs.
Read the guide →Run headless with -p, stream events with --mode json.
iCode Agent speaks the openai and anthropic
protocols, so it works with the official APIs and any compatible endpoint.
The agent runs locally; your code goes only to the model endpoint you
configure.
Free and open source (Apache-2.0). You pay only your model provider.
How it fits with iCode Workbench.
Workbench (in early access) is the desktop environment for a team of agents — Claude Code, Codex, and OpenCode in isolated worktrees, with tasks, review, and Mira. Agent is the focused terminal surface: one repository, one session, no window. They are separate products with the same discipline, and either one can be used on its own.
iCode Agent · Keep the thread, keep the cost bounded.