Command Surfaces
This page is the concise command map for contributors and coding agents. It is intentionally grouped by surface so AGENTS.md and CLAUDE.md do not need to inline large command dumps.
Core CLI: babysitter
The babysitter binary is shipped by @a5c-ai/babysitter and @a5c-ai/babysitter-sdk. The command families currently registered in the repo source live in packages/sdk/src/cli/main/program.ts.
Agent-facing help
babysitter --help is the automation surface. Its usage text is generated from packages/sdk/src/cli/main/usage.ts and centers on:
run:*andtask:*for deterministic replay loopssession:*for session binding and iteration guardsskill:discoverprocess-library:activeprofile:*instructions:babysit-skillharness:installandharness:install-plugin
Human-facing help
babysitter --help-human is the operator surface. It adds:
log,hook:*,compress-outputskill:fetch-remoteprocess-library:clone|update|useplugin:*tokens:statscompression:*harness:discover|listinstructions:process-create|orchestrate|breakpoint-handlingbreakpoint:*health,configure,version
Harness Runtime CLI: babysitter-harness
The optional runtime binary comes from @a5c-ai/babysitter-agent and is registered as babysitter-harness.
Use it for human-invoked orchestration sessions and runtime services:
create-run,call,yolo,plan,foreverresume-run,resumeretrospect,cleanup,assimilate,doctor,contribanycli,session-historyobserve,tuidaemon:*,cost:stats,start-serverdiscover,list,invoke
Runs Directory Defaults
The repo source now treats global runs storage as the default:
- default scope:
~/.a5c/runs - repo scope:
<repo>/.a5c/runswhenBABYSITTER_RUNS_SCOPE=repo - explicit override:
BABYSITTER_RUNS_DIRor--runs-dir
The implementation lives in packages/sdk/src/config/runs.ts and the default config in packages/sdk/src/config/defaults.ts.
When reading existing runs, the SDK also probes repo-local .a5c/runs for backward compatibility.
Plugin Commands
Plugin concepts are covered in Plugins Overview. The dedicated command reference is Plugin CLI Reference.
One current implementation detail worth remembering: plugin:install, plugin:update, and plugin:configure can auto-resolve the marketplace when --marketplace-name is omitted, as implemented in packages/sdk/src/cli/commands/plugin/packageCommands.ts.