| name | kilroy:setup |
| description | Build the Kilroy binary, verify CXDB is reachable on the central server via Tailscale, and verify all prerequisites for running Kilroy pipelines. |
| user-invocable | true |
Set up the Kilroy software factory environment. Run all checks and report results. Stop on the first fatal error.
This repo is the current working directory. The Kilroy source repo is at ../kilroy.
Step 1: Check prerequisites
Verify the following are installed and report each result:
go — required to build Kilroyruby — required for pipeline generation scriptsclaude — the Claude CLI, required by Kilroy to run agents. Must be authenticated (claude auth status should show loggedIn: true). Kilroy uses backend: cli so it authenticates via the CLI's OAuth session (e.g. Max plan), not an API key.- Tailscale connectivity —
ping -c 1 $KILROY_CXDB_HOST
Note: The .env file is loaded via direnv. Claude Code's non-interactive shell does not trigger direnv hooks automatically, so use direnv exec "$PWD" to wrap any command that needs to check or use environment variables from .env. Additionally, prefix with env -u CLAUDECODE to unset the nested-session guard variable, since Kilroy internally invokes claude and would otherwise fail with "cannot be launched inside another Claude Code session". For example:
env -u CLAUDECODE claude auth status
If any are missing, report which ones and stop. Do not proceed to build.
Step 2: Build Kilroy
cd ../kilroy && go build -o kilroy ./cmd/kilroy
Verify the binary was produced: ../kilroy/kilroy --version
If the build fails, report the error and stop.
Step 3: Verify CXDB
CXDB runs on the central server ($KILROY_CXDB_HOST), managed by kilroy cxdb. Verify it is reachable:
curl -sf http://$KILROY_CXDB_HOST:9110/healthz > /dev/null
If the curl fails, report that CXDB is not reachable and suggest:
- Ensure you are connected to Tailscale
- Start the instance on the server:
ssh vps 'kilroy cxdb start cxdb-graph-ui'
Step 4: Report
Summarize: prerequisites status, Kilroy version, CXDB status. Remind the user the next step is /kilroy:generate-pipeline.
