Download · OpenACP Server · Bug Reports · Discussions
Desktop app for OpenACP — a chat interface for managing AI coding agents across multiple workspaces. Built with Tauri 2 and React.
| Platform | Download |
|---|---|
| macOS (Apple Silicon) | OpenACP.dmg |
| macOS (Intel) | OpenACP.dmg |
| Windows | OpenACP-Setup.exe |
| Linux (deb) | openacp.deb |
| Linux (AppImage) | OpenACP.AppImage |
Or build from source (see below).
- Multi-workspace — connect to multiple OpenACP server instances, each in its own project folder
- Streaming chat — real-time agent responses with tool calls, thinking blocks, and markdown rendering
- Agent switching — switch between Claude Code, Gemini CLI, Codex, and 28+ other agents mid-conversation
- Permission control — approve or deny agent actions with inline buttons
- Session management — create, switch, and archive sessions per workspace
- Auto-updater — receive update notifications and install with one click
- Cross-platform — native app for macOS, Windows, and Linux
- OpenACP server running in your workspace (
openacp start)
For building from source:
- Node.js 22+
- pnpm 9+
- Rust — install via rustup.rs
git clone https://github.com/Open-ACP/OpenACP-App
cd OpenACP-App
make install
make tauri-devAvailable make targets:
| Command | Description |
|---|---|
make install |
Install dependencies |
make dev |
Vite dev server (frontend only) |
make tauri-dev |
Full Tauri dev app (frontend + Rust) |
make build |
TypeScript check + Vite production build |
make tauri-build |
Build native desktop binaries |
make lint |
Type check |
make release |
Tag and push release (triggers CI) |
make release-dry |
Preview next version |
make clean |
Clean build artifacts |
src/openacp/ — Application logic
api/ — REST client + SSE manager
context/ — React contexts (workspace, sessions, chat)
components/ — UI components (sidebar, composer, chat view)
hooks/ — Custom hooks (updater, auto-scroll, pacing)
src/ui/ — @openacp/ui design system (Radix UI + Tailwind CSS 4)
src-tauri/ — Tauri backend (Rust)
src/core/ — Modular backend (sidecar, keychain, onboarding)
Each workspace connects to its own OpenACP server via .openacp/api.port and .openacp/api-secret files in the project directory.
Versioning follows date-based format: YYYY.MDD.N (e.g. 2026.406.1)
make release # Interactive: confirm → commit → tag → push → CI builds
make release-dry # Preview next version without changesCI automatically builds for all platforms and publishes to GitHub Releases.
- Fork the repo
- Create a feature branch from
develop:git checkout -b feat/my-feature develop - Make changes in
src/openacp/ - Run
pnpm buildto verify - Open a PR to
develop
See issue templates for bug reports and feature requests.
MIT