/setup

Interactive setup for the cekernel runtime environment. Creates the directory structure and writes a user profile to ~/.config/cekernel/envs/default.env.

Workflow

Step 1: Ask CEKERNEL_VAR_DIR and CEKERNEL_BACKEND

Use AskUserQuestion to ask both at once:

1. Runtime directory (header: "VAR_DIR"): options ~/.local/var/cekernel (Recommended) ("User-local directory. No sudo required.") and /usr/local/var/cekernel ("System-wide directory. May require sudo to create."); "Other" allows a custom path.
2. Backend (header: "Backend"): options headless (Recommended) ("No terminal required. Runs in the background."), wezterm ("Visualize Workers in WezTerm tabs."), tmux ("Run Workers in tmux sessions.").

Map the answers: the path from the selected label or custom input; the backend name (headless, wezterm, or tmux).

Step 2: Additional variable configuration

1. Read envs/README.md (Read tool) and display the User-configurable Variables table (Variable, Default, Purpose), excluding CEKERNEL_VAR_DIR and CEKERNEL_BACKEND.
2. Ask (AskUserQuestion, header "Additional Configuration"): "No, use defaults" → skip to Step 3 / "Yes, customize" → continue.
3. Accept input via AskUserQuestion with "Other" free-text: "Enter a variable to set (KEY=VALUE format):"
   • Separator normalization: the user may separate key and value with =, :, ;, /, |, or space — replace the first occurrence with = before validation (e.g. CEKERNEL_WORKER_TIMEOUT 1800 → CEKERNEL_WORKER_TIMEOUT=1800).
4. Validate:
   • The variable name must exist in the User-configurable Variables table; otherwise show an error and ask again.
   • The value must match the "Valid Values" column: "Positive integer" → ^[1-9][0-9]*$; enumerations (e.g. true/false, backend names, none/open/pbcopy) → exact match; "Directory path" / "Any filename" → non-empty string. On failure, show the expected format and ask again.
5. After each successful variable, ask (header "More Variables"): "No, continue" → Step 3 / "Yes" → repeat from 3.

Step 3: Create directory structure

mkdir -p "${VAR_DIR}/ipc" "${VAR_DIR}/locks" "${VAR_DIR}/logs" "${VAR_DIR}/runners"
if [ ! -f "${VAR_DIR}/schedules.json" ]; then
  echo '[]' > "${VAR_DIR}/schedules.json"
fi

Step 4: Write user profile

mkdir -p "$HOME/.config/cekernel/envs"
cat > "$HOME/.config/cekernel/envs/default.env" <<EOF
# cekernel user profile (generated by /setup)
CEKERNEL_VAR_DIR=${VAR_DIR}
CEKERNEL_BACKEND=${BACKEND}
# Additional variables set during setup:
${ADDITIONAL_VARS}
EOF

${ADDITIONAL_VARS} is the KEY=VALUE lines from Step 2 (one per line); omit the comment and section if none.

Important: write VAR_DIR as an absolute path — tilde is not expanded inside values read by load-env.sh. Expand ~/... to $HOME/... before writing.

Step 5: Summary

Display: runtime directory, backend, count of additional variables (or "none"), profile path — and point to envs/README.md for other options. If the user selected wezterm, also point to config/README.md for the WezTerm plugin installation (read these files to give the actual path relative to the plugin directory).

Also present the recommended target-repo allowlist (ADR-0012 Amendment 4). Workers run headless in the target repository's checkout; without a pre-configured allowlist they may stall silently (blocked) on permission prompts. Recommend that each target repository ships a .claude/settings.json containing a non-empty permissions.allow, e.g.:

{"permissions": {"allow": ["Bash", "Edit", "Write", "Read"]}}

Do NOT create or modify the target repo's settings — this is a recommendation only; permission configuration is the operator's decision (spawn.sh warns at spawn time when it is missing, and --permission-mode acceptEdits is the alternative escape).

Important

• Do NOT run sudo at any point — the purpose of this skill is to avoid it via user-local paths.
• If ~/.config/cekernel/envs/default.env already exists, show the current content and ask whether to overwrite.
• Use $HOME (not ~) inside scripts.