openJiuwen-ai / iCode
git clone https://github.com/openJiuwen-ai/iCode.git
v0.30.1 · 1d ago
A lightweight, extensible, fully offline development platform and agent/workflow toolkit for the AI era, with an intuitive TUI, easy deployment, and complete control over your data, agents, and workflows.
—
stars, 24h
—
stars, 7 days
+361
stars, 30 days · #735
361
★ total
64
forks · 11 open issues
Star history starts 2026-10-20; the chart appears after the second daily snapshot.
LanguagePython
LicenseApache-2.0
Created2026-09-28 (22d ago)
Last push1d ago
Watchers3
OwnerOrganization
Links
README excerpt
[code] English | 简体中文 > **Work in progress.** Interfaces, file formats, and defaults still change between > releases. > **Use a modern terminal.** iCode works best in one such as > Windows Terminal on Windows or > Ghostty on macOS and Linux. ## What is iCode? Let the screenshots speak for themselves. ### Home The agent, model, approval mode and session at a glance, with agents (`#`), models (`$`), commands (`/`), files (`@`) and the shell (`!`) a keystroke away from the input bar. ### Chat Answers render as rich Markdown in the terminal, diagrams included. ### Workflows Watch a workflow run node by node, with each agent node's model, tool calls and token spend. ### Agents An agent is configuration, not code: instructions, tools, sub-agents, skills, MCP servers and memory, all edited in one place (**F2**). ### Models Model profiles from different providers side by side, switchable mid-conversation (**F4**). ### Diff Every file the agent changed, turn by turn or all at once, in unified or split view. ### Rollback Pick a turn, review the file changes that would be reverted, then discard the conversation after it. ### Trajectory Where the time and tokens went (**F12**): model versus tools versus waiting, a per-turn breakdown, and token and cache usage. Every model call, hook and tool call in a turn, laid out on a timeline. ### Shell The shell (`!`) is a real terminal, so full-screen programs run in place with every keystroke forwarded to them: here `htop`, inside iCode, inside iCode, inside iCode. ## How to run Use one of the three ways below. iCode ships no model profiles, so press **F4** on first launch to add one. ### From source uv is the only prerequisite; it provisions Python 3.14 for you. From a checkout: [code] ### Install with uv uv installs iCode from PyPI and provisions Python 3.14 for you: [code] Windows (x64) and Linux (x86-64 or ARM64, glibc 2.27 or later) need nothing else. On a Mac with Apple silicon, run `xcode-select --install` first. ### Offline package On an Intel Mac, Windows on Arm or an older Linux, use the offline package, which bundles Python and every dependency. The install script downloads the one for your platform, checks it and installs it; run it again to upgrade: [code] [code] On a machine without internet access, download the package from Releases elsewhere, unpack it, then install and run iCode: [code] Getting started lists the package for each platform and its requirements. ## User guide Press **F8** inside iCode to open the built-in user guide, a complete walkthrough of using it. The same pages live in `docs/`, in English and 简体中文. ## Privacy iCode does not collect your data. It has no telemetry, analytics or crash reporting, and it sends nothing about you or your work, usage data included, to us or to any other third party. What iCode itself sends goes only to destinations you configure: the model providers you add, the MCP servers your agents use, and any hooks or OpenTelemetry export you set up. The o