autonomic-bot
e805baf030
Three new skills for keeping cc-ci itself current (manual triggers for what should ideally be automatic): - /cc-ci-server-update — bump the cc-ci SERVER host's nixpkgs/sops-nix flake inputs (hard rev pin, moves deliberately), open a cc-ci PR, then deploy to the live host via nixos-rebuild switch (operator-authorized, no-CI window) + health gate (no failed units, infra up, endpoints 200). Manual trigger for periodic nixpkgs bumps. - /cc-ci-tests-update — sweep all maintained recipes for stale cc-ci tests (carry-over from /upgrade-all's commented stale tests + a fresh /ci-test-review sweep), author the minimal test update per stale recipe, open a cc-ci test PR, verify via the standard PR + !testme -> CI flow. Closes the loop the weekly /upgrade-all deliberately defers (it comments-only; this fixes the tests). Never weakens a test. - /cc-ci-update — umbrella: run server-update then tests-update, in that order, gated on the server health check (don't sweep tests on a sick/rolled-back host). Server-first because the harness toolchain rides on the host nixpkgs. All three: create + verify, NEVER merge. Reuse the existing ci-test-review helpers (open-cc-ci-pr.sh, run-all-recipes.sh, verify-pr.sh) and the recipe-upgrade --with-tests discipline.
cc-ci-orchestrator
Orchestrator workspace for building the cc-ci Co-op Cloud recipe CI server. The plan, launch
tooling, and loop prompts live in cc-ci-plan/; see AGENTS.md for the
roles and operating model. Secrets (.testenv) are gitignored — never commit them.
Run the orchestrator in tmux (survives disconnects + closing your laptop)
Keep this supervising session alive on the host with tmux, and use --remote-control so you can
watch/steer it from claude.ai/code (or the mobile app).
# 0. Exit any running orchestrator session first — a conversation can't be resumed while it's live:
# /exit (inside Claude) or Ctrl-D
# 1. Start a detachable tmux session on this host
tmux new -s orchestrator
# 2. Inside tmux, resume the orchestrator conversation WITH remote control:
claude --resume autonomous-orchestrator \
--remote-control "autonomous-orchestrator" \
--dangerously-skip-permissions
# - If name-resume opens a picker instead of resuming directly, choose "autonomous-orchestrator".
# - Or resume by the stable session id (more deterministic in a fresh pane):
# claude --resume 34a80a99-b37e-4809-b8da-ccc9fafe785e \
# --remote-control "autonomous-orchestrator" --dangerously-skip-permissions
# 3. Detach — the process keeps running: press Ctrl-b, then d
Reconnect later
- On this host:
tmux attach -t orchestrator - From anywhere: claude.ai/code → the
autonomous-orchestratorsession
Why it survives: tmux keeps the claude process alive across SSH disconnects and your laptop
closing; remote-control runs outbound from this host to Anthropic, so it stays connected
regardless of the viewer. After a host reboot, re-run steps 1–2.
Two different "names":
--resume <name|id>selects the conversation to restore (shown in the/resumepicker); the--remote-control "<name>"value is only the web display label and resumes nothing. Resuming reuses the same session id each time (stays34a8…) — don't pass--fork-sessionunless you intend to branch a new conversation.Already inside a live session and just want the web surface? Run
/remote-control— no exit/resume.
Kick off / supervise the loops
cd /srv/cc-ci/cc-ci-plan
./launch.sh start # Builder + Adversary loops (interactive --remote-control in tmux) + watchdog
./launch.sh status # session + DONE state
./launch.sh logs builder|adversary|watchdog
./launch.sh stop
Full supervision guide, credential map, and the Incus VM fallback are in
cc-ci-plan/kickoff.md and cc-ci-plan/plan.md §1.5.