WindCli

A web-based UI for Claude Code, Codex, Cursor CLI, OpenCode, and Pi Coding Agent.

WindCli is an independent secondary-development project based on siteboon/claudecodeui. We are grateful to the original project and its contributors for the foundation.

Highlights

• One local interface for Claude Code, Codex, Cursor CLI, OpenCode, and Pi.
• Persistent projects, conversations, terminals, worktrees, scheduled tasks, custom agents, and provider-specific settings.
• Browser automation through your existing Chrome profile, an isolated managed browser, or a loopback CDP endpoint, with manual takeover when needed.
• Optional Agent integration that installs the maintained windcli-browser Skill and MCP registration for supported providers.
• Installable PWA and packaged desktop applications with version notifications.

Run locally

Requires Node.js 22 or newer.

Pi support uses the external pi executable from @earendil-works/pi-coding-agent 0.84.2 or newer. Install it separately and authenticate a model in the Pi TUI with /login (or configure the relevant provider environment variable). WindCli does not read or manage upstream API keys. Pi sessions are discovered from PI_CODING_AGENT_SESSION_DIR, then the global Pi sessionDir setting, then ~/.pi/agent/sessions.

npx wind-agent-cli

Or install the command globally:

npm install -g wind-agent-cli
wacli

Open http://localhost:5200 after the server starts.

For configuration, desktop builds, sandbox support, and development instructions, see the full documentation.

Updates

WindCli checks for new stable releases. When an update is available, a green dot appears next to WindCli in the upper-left corner. Select the brand to review the installed and latest versions, then confirm the update.

• An in-app update for a global npm installation installs the resolved release and can restart the standalone WindCli process. The wacli update terminal command updates the package, but a server already running in another process must be restarted manually.
• A source checkout on a clean main branch fast-forwards from its configured remote, installs dependencies, rebuilds, and restarts after confirmation.
• A packaged desktop application downloads its signed update in the background and installs it only after confirmation, then restarts automatically.
• Deployments managed by an external platform do not expose self-update; update them through that platform instead.

Supervisor-managed servers should use their supervisor's restart policy. A dirty source checkout is never changed automatically.

Browser control

Open Settings -> Browser to pair the WindCli Browser Bridge with an existing Chrome profile, install an isolated managed browser, or configure loopback CDP. You can also enable Agent integration per provider so ordinary website requests discover the browser tools without requiring MCP-specific wording.

See Browser control and existing Chrome sessions for installation, security boundaries, connection modes, and troubleshooting.

Agent workspace control

The windcli-workspace Skill uses wacli ui to open project files, manage internal tabs, and display HTML previews in the Agent's bound WindCli window. See Agent workspace control for installation, commands, binding, and the remaining control milestones.

Progressive Web App

WindCli can be installed from a supported desktop or mobile browser. The PWA caches the versioned application shell and static assets, provides an explicit new-version reload prompt, and keeps Web Push notification navigation working in the installed app.

The interface can reopen offline after it has loaded successfully once. Agent runs, project data, terminals, and other server-backed operations still require the WindCli server to be reachable.

License

AGPL-3.0-or-later