# Installation ## System Requirements | Requirement | Minimum | |---|---| | Node.js | 20 or later | | Package manager | npm (bundled with Node) or pnpm | | Operating system | macOS, Linux | | Windows | Supported via WSL2 | No database, no Docker, no external services required beyond the messaging platform bots you configure. ## One-liner install (recommended) The fastest way to install OpenACP on macOS or Linux: ```bash curl -fsSL https://raw.githubusercontent.com/Open-ACP/OpenACP/main/scripts/install.sh | bash ``` The script automatically: 1. Detects your platform (macOS or Linux). 2. Checks for Node.js 20+ and installs it if missing. 3. Installs `@openacp/cli` globally via npm. 4. Launches the setup wizard. No prior setup required — the script handles everything. ## Install via npm If you prefer to manage Node.js yourself, install OpenACP directly from npm: ```bash npm install -g @openacp/cli ``` ### Verify the installation ```bash openacp --version ``` This prints the installed version (e.g., `2026.401.1`) and exits. If the command is not found, ensure your npm global bin directory is on `PATH`. ## First Run and Setup Wizard The first time you run `openacp start`, the CLI detects that no config file exists at `~/.openacp/config.json` and launches the interactive setup wizard automatically. The wizard walks you through: 1. **Channel selection** — Telegram, Discord, or both. 2. **Bot credentials** — Token and chat/guild ID, validated live against the platform API. 3. **Agent selection** — Which ACP-compatible agent binary to use (e.g., `claude-agent-acp`). 4. **Workspace directory** — Where agent working directories are created (default: `~/openacp-workspace`). 5. **Run mode** — Foreground (interactive) or daemon (background process with optional autostart on boot). After completing the wizard, config is written to `~/.openacp/config.json` and the server starts. To re-run the wizard at any time: ```bash openacp onboard ``` ## Data Directory All runtime state lives under `~/.openacp/`: ``` ~/.openacp/ config.json — Main configuration file api-secret — Bearer token for the local REST API (auto-generated, mode 0600) api.port — Port file written by the running daemon openacp.pid — PID file for the daemon process running — Marker file: daemon was running before last shutdown (used for autostart) logs/ — Application and session logs openacp.log — Main log (rotated) sessions/ — Per-session log files plugins/ — Installed plugin adapters agents.json — Installed agent definitions ``` You can override the config path with the `OPENACP_CONFIG_PATH` environment variable. ## Running from Source If you want to hack on OpenACP or run an unreleased version: ```bash git clone https://github.com/Open-ACP/OpenACP.git cd OpenACP pnpm install pnpm build # TypeScript compile → dist/ pnpm start # node dist/cli.js ``` For watch mode during development: ```bash pnpm dev # tsc --watch ``` The source build uses the same `~/.openacp/` data directory as the published package, so you can switch between them freely.