Menu
Use when inspecting state, output, completion, or worktree activity for Codex goal runs launched by Boondoggle.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
| name | boondoggle-runs |
| description | Use when inspecting state, output, completion, or worktree activity for Codex goal runs launched by Boondoggle. |
Use this skill when the user asks about a Boondoggle run or a Codex goal run launched by Boondoggle.
Boondoggle runs a Codex goal from a prompt on stdin. It is often launched through Foolfad, so the worktree and branch may use the Foolfad layout:
~/.remote-work/repos/<repo-path>/foolfad-<run-id>
foolfad/<run-id>
Useful local checks:
worktree="${HOME}/.remote-work/repos/gh/OWNER/REPO/foolfad-run-id"
pgrep -af 'boondoggle|codex app-server|codex' || true
ps -eo pid,ppid,etime,stat,cmd --sort=etime | rg -F "$worktree" || true
ps -eo pid,ppid,etime,stat,cmd --sort=etime | rg 'boondoggle|codex app-server' || true
git -C "$worktree" status --short --branch
git -C "$worktree" log -5 --decorate --oneline
find "$worktree" -xdev -type f -printf '%T@ %p\n' 2>/dev/null | sort -nr | head -40
Boondoggle can commit and push worktree changes on goal success, goal failure, or unexpected exit. By default, publish is enabled for all three outcomes. The default commit subject starts with:
Codex Goal Worktree State: status=<status>
The commit body records prompt length, run status, exit status, Codex thread id, and UTC time.
Use these git checks to identify the latest published outcome:
git -C "$worktree" log --decorate --oneline --grep='Codex Goal Worktree State' -20
git -C "$worktree" log -1 --format=fuller
Tell the user what you can verify:
Boondoggle tracks runs through git commits and live processes, not pidfiles. Report what those signals show instead of looking for a status or pid file.
Use when the user wants to run a long or resource-heavy task on another computer so their local machine stays free, the work continues if they close their laptop or lose connection, and the result returns as a reviewable branch in their project. Use this skill also when no offload target exists yet and the user needs help setting one up.
Use for dispatching a command from the current git repo to a remote machine in order to offload work for execution.
Clone GitHub repos on this machine with ghwc: canonical owner/repo casing, shared bare clone, branch-named sibling worktrees under ~/Projects.
Use this skill for any task involving the ambit CLI: creating or destroying private networks, deploying apps to a private network, checking network or router health, listing routers, diagnosing connectivity problems, managing app secrets, or streaming app logs. Trigger phrases include "create a network", "set up ambit", "deploy with ambit", "ambit create", "ambit deploy", "ambit doctor", "check router status", "destroy a network", "managing app secrets", "streaming app logs", and similar.
Use when launching a persistent Codex goal run with `boondoggle` from a prompt on stdin.
Use this to check or configure auth and config state on a remote device via a Foolfad transport -- this is `foolfad-configure`.