← ClaudeAtlas

ciao-dev-installlisted

Build the current develop checkout into a self-contained Ciaobot.app and install it on this machine for testing, then watch logs for issues. Trigger on "install develop", "test the develop build", "install the current dev version", "build and install ciaobot", "install dev build", or asking to test new changes locally instead of via the release installer.
raffaelefarinaro/ciaobot · ★ 9 · AI & Automation · score 72
Install: claude install-skill raffaelefarinaro/ciaobot
# Ciaobot develop install > Contributor/project skill — lives in the repo's workspace `skills/` folder, **not** `ciao/stock/skills/`. It is for people working *on* Ciaobot and is deliberately not packaged or shipped to end-user installs. `ciao sync-skills` mirrors it into the runtime-discovered `.claude/skills/` catalog. Don't move it into `ciao/stock/`. Replaces the end-user one-liner (`curl -fsSL .../install.sh | sh`) with the same outcome built from the **local `develop` checkout**: a self-contained `Ciaobot.app` with the current `ciao/` backend and PWA embedded, installed on this machine, preserving the existing workspace and password. Then watch the engine logs and report anything broken. Two things make this heavy but faithful: the embedded runtime is rebuilt (it pip-installs the current `ciao/` code and PWA static assets), and the Tauri app is rebuilt from `desktop/`. Expect 10–20+ minutes on a laptop, dominated by the runtime build's two Python downloads and dependency installs. ## Before you start - The checkout must be on `develop`, clean, and up to date. - Toolchain must be present: Node 22 (`.nvmrc`), cargo (Rust 1.90.0 via rustup), `swiftc`, `uv`, and a repo `.venv`. If any is missing, install it before building. - The installed app currently lives at `~/Applications/Ciaobot.app` (`CIAO_APP_DIR`); the workspace and password live in the existing `com.ciao.server.plist` and are preserved. - Ask the user before installing if the build or install steps would ove