II.
Page overview
Reference · livepage:docs-user-guide-reference-cli-reference
Babysitter CLI Reference overview
Inspect the raw attributes, linked wiki pages, and inbound or outbound graph edges for page:docs-user-guide-reference-cli-reference.
Attributes
nodeKind
Page
sourcePath
docs/user-guide/reference/cli-reference.md
sourceKind
repo-docs
title
Babysitter CLI Reference
displayName
Babysitter CLI Reference
slug
docs/user-guide/reference/cli-reference
articlePath
wiki/docs/user-guide/reference/cli-reference.md
article
# Babysitter CLI Reference
**Version:** 1.1
**CLI/SDK Version:** 5.0.0
**Last Updated:** 2026-01-25
Complete reference documentation for the core Babysitter command-line interface.
> **Looking for slash commands?** See [Slash Commands Reference](./slash-commands.md) for `/babysitter:call`, `/babysitter:yolo`, and other Claude Code commands.
---
## Table of Contents
- [Overview](#overview)
- [Installation](#installation)
- [Global Options](#global-options)
- [Run Management Commands](#run-management-commands)
- [run:create](#runcreate)
- [run:assign-process](#runassign-process)
- [run:status](#runstatus)
- [run:events](#runevents)
- [run:iterate](#runiterate)
- [run:rebuild-state](#runrebuild-state)
- [Task Commands](#task-commands)
- [task:list](#tasklist)
- [task:show](#taskshow)
- [task:post](#taskpost)
- [Breakpoint Rule Commands](#breakpoint-rule-commands)
- [breakpoint:approve-rule](#breakpointapprove-rule)
- [breakpoint:remove-rule](#breakpointremove-rule)
- [breakpoint:list-rules](#breakpointlist-rules)
- [breakpoint:should-auto-approve](#breakpointshould-auto-approve)
- [breakpoint:history](#breakpointhistory)
- [Exit Codes](#exit-codes)
- [Output Formats](#output-formats)
- [Examples](#examples)
---
## Overview
The Babysitter CLI provides deterministic orchestration for event-sourced workflows. It enables run lifecycle management, task introspection, plugin/profile management, and result posting.
**Binary Names:**
- `babysitter` (primary)
- `babysitter-sdk` (alias)
**Package split:**
- Install `@a5c-ai/babysitter` for the recommended end-user `babysitter` command.
- Install `@a5c-ai/babysitter-sdk` if you need the SDK/library directly or want the underlying CLI implementation package.
- Install `@a5c-ai/babysitter-agent` for runtime commands such as `call`, `resume`, `plan`, `start-server`, and `tui`.
**Design Principles:**
- Deterministic operations (same inputs = same outputs)
- JSON-first output for automation
- POSIX path separators in all output (cross-platform)
- No hidden state mutations
---
## Installation
### Global Installation (Recommended)
```bash
npm install -g @a5c-ai/babysitter@latest
```
### Optional Runtime CLI
```bash
npm install -g @a5c-ai/babysitter-agent@latest
```
### Via npx (No Install)
```bash
npx -y @a5c-ai/babysitter@latest <command>
```
### Verify Installation
```bash
babysitter --version
# Output: 5.0.0
```
### Alias Setup
```bash
# Recommended alias for scripts
CLI="babysitter"
# Or for npx usage
CLI="npx -y @a5c-ai/babysitter@latest"
```
---
## Global Options
These options are available on all commands:
| Option | Description | Default |
|--------|-------------|---------|
| `--runs-dir <path>` | Override the runs directory | `~/.a5c/runs` |
| `--json` | Output in JSON format | `false` |
| `--verbose` | Enable verbose logging (paths, resolved options) | `false` |
| `--dry-run` | Preview changes without applying (where supported) | `false` |
| `--help`, `-h` | Show agent-facing help (default; covers commands intended for agent/automation use) | - |
| `--help-human` | Show human-facing help for the core CLI surface (for example `session:*`, `plugin:*`, `harness:*`, `configure`) | - |
| `--version`, `-v` | Show version number | - |
> The default `--help` (and the usage text printed on a wrong-syntax invocation or a bare command name) lists **agent-facing** commands only — the surface a babysitter skill or hook would call. Run `babysitter --help-human` to see the commands intended for direct human use.
> Runtime/orchestration commands such as `babysitter-agent call`, `resume`, `plan`, `doctor`, `start-server`, and `tui` are part of the optional `@a5c-ai/babysitter-agent` package and are not covered by this reference unless explicitly noted.
### Path Handling
- All paths in output use POSIX separators (`/`) regardless of platform
- Input paths accept both POSIX (`/`) and Windows (`\`) separators
- Paths are relative to the run directory unless absolute
---
## Run Management Commands
### run:create
Creates a new orchestration run.
#### Synopsis
```bash
babysitter run:create \
--process-id <id> \
--entry <path>#<export> \
[--inputs <file>] \
[--run-id <id>] \
[--process-revision <rev>] \
[--request <description>] \
[--prompt <text>] \
[--json]
```
#### Options
| Option | Required | Description |
|--------|----------|-------------|
| `--process-id <id>` | Yes | Process identifier (e.g., `dev/build`) |
| `--entry <path>#<export>` | Yes | Entry point file and export name |
| `--inputs <file>` | No | Path to inputs JSON file |
| `--run-id <id>` | No | Custom run ID (auto-generated if omitted) |
| `--process-revision <rev>` | No | Process revision/version |
| `--request <description>` | No | Human-readable request description |
| `--prompt <text>` | No | Initial user prompt to persist in run metadata and journal |
#### Output (Human)
```
[run:create] runId=run-20260125-143012 runDir=.a5c/runs/run-20260125-143012
```
#### Output (JSON)
```json
{
"runId": "run-20260125-143012",
"runDir": ".a5c/runs/run-20260125-143012",
"process": {
"processId": "dev/build",
"entry": "processes/build/process.mjs#process"
}
}
```
#### Examples
```bash
# Basic run creation
babysitter run:create \
--process-id dev/build \
--entry .a5c/processes/build/main.js#buildProcess
# With inputs and custom ID
babysitter run:create \
--process-id tdd/feature \
--entry .a5c/processes/tdd/main.js#tddProcess \
--inputs ./inputs.json \
--run-id "run-$(date -u +%Y%m%d-%H%M%S)-auth-feature" \
--prompt "Implement auth feature with TDD" \
--json
# With request description
babysitter run:create \
--process-id dev/api \
--entry ./process.js#apiProcess \
--request "Build REST API with authentication" \
--prompt "Build REST API with authentication"
```
---
### run:assign-process
Assigns a process to an existing run.
#### Synopsis
```bash
babysitter run:assign-process <runDir> \
--entry <path>#<export> \
[--process-id <id>] \
[--process-revision <rev>] \
[--force] \
[--json] \
[--dry-run] \
[--verbose]
```
#### Description
Assigns a process entrypoint to an existing bare run (one created without `--entry`). Updates the run's `entrypoint`, `processPath`, and `processId` fields in `run.json` and appends a `PROCESS_ASSIGNED` journal event. If the run already has a process assigned, the command rejects unless `--force` is provided.
#### Arguments
| Argument | Required | Description |
|----------|----------|-------------|
| `<runDir>` | Yes | Run ID or path to run directory |
#### Options
| Option | Required | Description |
|--------|----------|-------------|
| `--entry <path>#<export>` | Yes | Entry point file and export name |
| `--process-id <id>` | No | Process identifier (retains existing if omitted) |
| `--process-revision <rev>` | No | Process revision/version |
| `--force` | No | Override if a process is already assigned |
| `--json` | No | Output in JSON format |
| `--dry-run` | No | Preview changes without applying |
| `--verbose` | No | Enable verbose logging |
#### Output (Human)
```
[run:assign-process] runId=run-20260125-143012 runDir=.a5c/runs/run-20260125-143012 entry=.a5c/processes/build/main.js#buildProcess processId=dev/build
```
#### Output (JSON)
```json
{
"runId": "run-20260125-143012",
"runDir": ".a5c/runs/run-20260125-143012",
"entry": ".a5c/processes/build/main.js#buildProcess",
"processId": "dev/build",
"previousEntrypoint": {
"importPath": "bare-run"
},
"assigned": true
}
```
#### Dry Run Output (JSON)
```json
{
"dryRun": true,
"runDir": ".a5c/runs/run-20260125-143012",
"runId": "run-20260125-143012",
"entry": ".a5c/processes/build/main.js#buildProcess",
"processId": "dev/build",
"previousEntrypoint": {
"importPath": "bare-run"
},
"force": false
}
```
#### Error Responses (JSON)
| Error Code | Condition |
|------------|-----------|
| `RUN_NOT_FOUND` | Run directory does not exist |
| `PROCESS_ALREADY_ASSIGNED` | Run already has a process and `--force` was not provided |
#### Examples
```bash
# Assign a process to a bare run
babysitter run:assign-process .a5c/runs/run-20260125-143012 \
--entry .a5c/processes/build/main.js#buildProcess \
--process-id dev/build
# Assign with JSON output
babysitter run:assign-process run-20260125-143012 \
--entry .a5c/processes/tdd/main.js#tddProcess \
--process-id tdd/feature \
--json
# Preview without applying
babysitter run:assign-process run-20260125-143012 \
--entry .a5c/processes/build/main.js#buildProcess \
--process-id dev/build \
--dry-run --json
# Force reassign a process to a run that already has one
babysitter run:assign-process run-20260125-143012 \
--entry .a5c/processes/build/main.js#buildProcess \
--process-id dev/build \
--force --json
# With process revision
babysitter run:assign-process run-20260125-143012 \
--entry .a5c/processes/build/main.js#buildProcess \
--process-id dev/build \
--process-revision 2.1.0
```
---
### run:status
Returns the current status of a run.
#### Synopsis
```bash
babysitter run:status <runId> [--json]
```
#### Arguments
| Argument | Required | Description |
|----------|----------|-------------|
| `<runId>` | Yes | Run ID or path to run directory |
#### Output (Human)
```
[run:status] state=waiting last=EFFECT_REQUESTED#0042 2026-01-25T14:30:12.123Z pending[node]=2 pending[total]=2 stateVersion=42
```
#### Output (JSON)
```json
{
"runId": "run-20260125-143012",
"state": "waiting",
"lastEvent": "EFFECT_REQUESTED#0042 2026-01-25T14:30:12.123Z",
"pendingByKind": {
"node": 2
},
"metadata": {
"processId": "dev/build",
"stateVersion": 42,
"pendingEffectsByKind": {
"node": 2
}
},
"completionProof": "..." // Only present when state=completed
}
```
#### State Values
| State | Description |
|-------|-------------|
| `created` | Run initialized, not yet started |
| `running` | Run in progress |
| `waiting` | Blocked on breakpoint or sleep |
| `completed` | Run finished successfully |
| `failed` | Run terminated with error |
#### Examples
```bash
# Check status
babysitter run:status run-20260125-143012
# JSON output
babysitter run:status run-20260125-143012 --json
# Using run directory path
babysitter run:status .a5c/runs/run-20260125-143012 --json
```
---
### run:events
Lists journal events for a run.
#### Synopsis
```bash
babysitter run:events <runId> \
[--limit <n>] \
[--reverse] \
[--filter-type <type>] \
[--json]
```
#### Options
| Option | Description | Default |
|--------|-------------|---------|
| `--limit <n>` | Maximum events to return | All |
| `--reverse` | Show newest events first | `false` |
| `--filter-type <type>` | Filter by event type | All types |
#### Output (Human)
```
[run:events] count=42
#0001 2026-01-25T14:30:12.123Z RUN_CREATED processId=dev/build
#0002 2026-01-25T14:30:12.234Z EFFECT_REQUESTED effectId=effect-abc123
#0003 2026-01-25T14:30:15.456Z EFFECT_RESOLVED effectId=effect-abc123
...
```
#### Output (JSON)
```json
{
"count": 42,
"events": [
{
"type": "RUN_CREATED",
"recordedAt": "2026-01-25T14:30:12.123Z",
"data": {
"processId": "dev/build"
},
"checksum": "a1b2c3..."
}
]
}
```
#### Examples
```bash
# Show all events
babysitter run:events run-20260125-143012
# Last 20 events (newest first)
babysitter run:events run-20260125-143012 --limit 20 --reverse
# Filter by type
babysitter run:events run-20260125-143012 --filter-type EFFECT_RESOLVED --json
```
---
### run:iterate
Executes a single orchestration iteration. This is the core command for driving runs.
#### Synopsis
```bash
babysitter run:iterate <runId> \
[--iteration <n>] \
[--json]
```
#### Options
| Option | Description | Default |
|--------|-------------|---------|
| `--iteration <n>` | Iteration number (for logging) | 1 |
#### Output (Human)
```
[run:iterate] iteration=1 status=executed action=executed-tasks count=3
```
#### Output (JSON)
```json
{
"iteration": 1,
"status": "executed",
"action": "executed-tasks",
"reason": "auto-runnable-tasks",
"count": 3,
"metadata": {
"runId": "run-20260125-143012",
"processId": "dev/build",
"hookStatus": "executed",
"stateVersion": 45
},
"completionProof": "..." // Only present when status=completed
}
```
#### Status Values
| Status | Description | Action |
|--------|-------------|--------|
| `executed` | Tasks were executed | Continue looping |
| `waiting` | Breakpoint or sleep active | Pause, check periodically |
| `completed` | Run finished successfully | Exit loop |
| `failed` | Run encountered error | Exit loop, investigate |
| `none` | No pending effects | May indicate completion |
#### Examples
```bash
# Single iteration
babysitter run:iterate run-20260125-143012 --json
# With iteration number
babysitter run:iterate run-20260125-143012 --iteration 5 --json
# Orchestration loop pattern
ITERATION=0
while true; do
((ITERATION++))
RESULT=$(babysitter run:iterate "$RUN_ID" --json --iteration $ITERATION)
STATUS=$(echo "$RESULT" | jq -r '.status')
case "$STATUS" in
completed|failed) break ;;
waiting) sleep 5 ;;
*) continue ;;
esac
done
```
---
### run:rebuild-state
Rebuilds the state cache from the journal.
#### Synopsis
```bash
babysitter run:rebuild-state <runId> [--json]
```
#### Description
Replays the journal to reconstruct `state/state.json`. Useful when the state cache is missing, corrupted, or stale.
#### Output (JSON)
```json
{
"status": "rebuilt",
"reason": "missing-state-file",
"eventCount": 42,
"stateVersion": 42
}
```
#### Examples
```bash
# Rebuild state
babysitter run:rebuild-state run-20260125-143012
# Check result
babysitter run:status run-20260125-143012 --json
```
---
## Task Commands
### task:list
Lists tasks in a run with their status.
#### Synopsis
```bash
babysitter task:list <runId> \
[--pending] \
[--kind <kind>] \
[--json]
```
#### Options
| Option | Description | Default |
|--------|-------------|---------|
| `--pending` | Show only pending (unresolved) tasks | All tasks |
| `--kind <kind>` | Filter by task kind | All kinds |
#### Output (Human)
```
[task:list] pending=2
- ef-build-001 [node requested] build workspace (taskId=build.workspaces)
- ef-lint-001 [node requested] lint sources (taskId=lint.sources)
```
#### Output (JSON)
```json
{
"tasks": [
{
"effectId": "ef-build-001",
"status": "requested",
"kind": "node",
"label": "build workspace",
"taskId": "build.workspaces",
"taskDefRef": "tasks/ef-build-001/task.json",
"resultRef": null,
"stdoutRef": null,
"stderrRef": null
}
]
}
```
#### Examples
```bash
# List all tasks
babysitter task:list run-20260125-143012
# List pending tasks only
babysitter task:list run-20260125-143012 --pending --json
# Filter by kind
babysitter task:list run-20260125-143012 --kind breakpoint
```
---
### task:show
Shows detailed information about a specific task.
#### Synopsis
```bash
babysitter task:show <runId> <effectId> [--json]
```
#### Arguments
| Argument | Required | Description |
|----------|----------|-------------|
| `<runId>` | Yes | Run ID |
| `<effectId>` | Yes | Effect ID of the task |
#### Output (JSON)
```json
{
"effect": {
"effectId": "ef-build-001",
"taskId": "build.workspaces",
"status": "requested",
"kind": "node",
"stdoutRef": null
},
"task": {
"kind": "node",
"node": {
"entry": "build/scripts/build-workspace.mjs",
"args": ["--workspace", "frontend"]
}
},
"result": null,
"largeResult": null
}
```
#### Examples
```bash
# Show task details
babysitter task:show run-20260125-143012 ef-build-001 --json
# Human readable
babysitter task:show run-20260125-143012 ef-build-001
```
---
### task:post
Posts a result for an executed task. This is how you commit external execution results into the run.
#### Synopsis
```bash
babysitter task:post <runId> <effectId> \
--status <ok|error> \
[--value <file>] \
[--value-inline <json>] \
[--error <file>] \
[--stdout-ref <ref>] \
[--stderr-ref <ref>] \
[--stdout-file <file>] \
[--stderr-file <file>] \
[--started-at <iso8601>] \
[--finished-at <iso8601>] \
[--metadata <file>] \
[--invocation-key <key>] \
[--dry-run] \
[--json]
```
#### Options
| Option | Required | Description |
|--------|----------|-------------|
| `--status <ok\|error>` | Yes | Task completion status |
| `--value <file>` | No | Path to result value JSON (for status=ok) |
| `--value-inline <json>` | No | Inline JSON result value (for status=ok, cannot be combined with `--value`) |
| `--error <file>` | No | Path to error payload JSON (for status=error) |
| `--stdout-ref <ref>` | No | Reference to stdout file |
| `--stderr-ref <ref>` | No | Reference to stderr file |
| `--stdout-file <file>` | No | Path to stdout file to copy |
| `--stderr-file <file>` | No | Path to stderr file to copy |
| `--started-at <iso8601>` | No | Task start timestamp |
| `--finished-at <iso8601>` | No | Task end timestamp |
| `--metadata <file>` | No | Path to additional metadata JSON |
| `--invocation-key <key>` | No | Invocation key for the task |
| `--dry-run` | No | Preview without committing |
#### Output (JSON)
```json
{
"status": "ok",
"committed": {
"resultRef": "tasks/ef-build-001/result.json",
"stdoutRef": "tasks/ef-build-001/stdout.log",
"stderrRef": "tasks/ef-build-001/stderr.log"
},
"stdoutRef": "tasks/ef-build-001/stdout.log",
"stderrRef": "tasks/ef-build-001/stderr.log",
"resultRef": "tasks/ef-build-001/result.json"
}
```
#### Important Notes
1. **Do NOT write `result.json` directly** - The SDK owns this file
2. Provide your result value either as a separate file (for example `output.json`) or inline JSON
3. Pass the value via `--value <file>` or `--value-inline '<json>'`
4. The CLI will create the proper `result.json` with metadata
#### Examples
```bash
# Post successful result
echo '{"score": 85}' > tasks/ef-build-001/output.json
babysitter task:post run-20260125-143012 ef-build-001 \
--status ok \
--value tasks/ef-build-001/output.json \
--json
# Post successful result inline
babysitter task:post run-20260125-143012 ef-build-001 \
--status ok \
--value-inline '{"approved": true}' \
--json
# Post with stdout/stderr
babysitter task:post run-20260125-143012 ef-build-001 \
--status ok \
--value tasks/ef-build-001/output.json \
--stdout-file tasks/ef-build-001/stdout.log \
--stderr-file tasks/ef-build-001/stderr.log \
--json
# Post error
echo '{"error": "Build failed", "exitCode": 1}' > tasks/ef-build-001/error.json
babysitter task:post run-20260125-143012 ef-build-001 \
--status error \
--error tasks/ef-build-001/error.json \
--json
# Dry run (preview)
babysitter task:post run-20260125-143012 ef-build-001 \
--status ok \
--dry-run
```
---
## Exit Codes
| Code | Meaning |
|------|---------|
| `0` | Success |
| `1` | Expected user error (bad args, missing run, validation failure) |
| `2+` | Unexpected internal error |
### Error Handling
Errors include:
- Command prefix
- Resolved run directory
- Descriptive message
- Stack trace (with `--verbose`)
Example error:
```
[run:events] unable to read run metadata at .a5c/runs/invalid-run
```
---
## Output Formats
### Human Format (Default)
Terse, single-line output optimized for CI logs and human readability.
```
[run:status] state=waiting last=EFFECT_REQUESTED#0042 pending[node]=2
```
### JSON Format (`--json`)
Structured JSON for programmatic parsing.
```json
{
"state": "waiting",
"pendingByKind": { "node": 2 }
}
```
**JSON Conventions:**
- Single JSON document (not streaming)
- All timestamps are ISO 8601 strings
- Numbers remain numeric
- Paths use POSIX separators
### Secret Handling
Task payloads are never echoed by default. To see full payloads:
```bash
BABYSITTER_ALLOW_SECRET_LOGS=true babysitter task:show <runId> <effectId> --json --verbose
```
---
## Examples
### Complete Orchestration Flow
```bash
#!/bin/bash
set -euo pipefail
CLI="babysitter"
PROCESS_ID="tdd/feature"
ENTRY=".a5c/processes/tdd/main.js#tddProcess"
# 1. Create run
RESULT=$($CLI run:create \
--process-id "$PROCESS_ID" \
--entry "$ENTRY" \
--inputs inputs.json \
--prompt "Build feature with TDD" \
--json)
RUN_ID=$(echo "$RESULT" | jq -r '.runId')
echo "Created run: $RUN_ID"
# 2. Orchestration loop
ITERATION=0
MAX_ITERATIONS=100
while [ $ITERATION -lt $MAX_ITERATIONS ]; do
((ITERATION++))
echo "Iteration $ITERATION..."
# Run iteration
RESULT=$($CLI run:iterate "$RUN_ID" --json --iteration $ITERATION)
STATUS=$(echo "$RESULT" | jq -r '.status')
echo "Status: $STATUS"
case "$STATUS" in
completed)
echo "Run completed successfully!"
break
;;
failed)
echo "Run failed!"
exit 1
;;
waiting)
echo "Waiting for breakpoint..."
sleep 10
;;
executed|none)
continue
;;
esac
done
# 3. Final status
$CLI run:status "$RUN_ID" --json
```
### Task Execution Pattern
```bash
#!/bin/bash
RUN_ID="$1"
# Get pending tasks
TASKS=$($CLI task:list "$RUN_ID" --pending --json)
COUNT=$(echo "$TASKS" | jq '.tasks | length')
echo "Found $COUNT pending tasks"
# Process each task
echo "$TASKS" | jq -c '.tasks[]' | while read -r task; do
EFFECT_ID=$(echo "$task" | jq -r '.effectId')
KIND=$(echo "$task" | jq -r '.kind')
echo "Processing: $EFFECT_ID ($KIND)"
# Execute based on kind
case "$KIND" in
node)
# Execute node task...
node "$(echo "$task" | jq -r '.task.node.entry')"
;;
esac
# Post result
echo '{"success": true}' > "tasks/$EFFECT_ID/output.json"
$CLI task:post "$RUN_ID" "$EFFECT_ID" \
--status ok \
--value "tasks/$EFFECT_ID/output.json" \
--json
done
```
---
## Quick Reference Card
### Run Commands
```bash
# Create
babysitter run:create --process-id <id> --entry <path>#<export> [--prompt <text>] --json
# Assign process to bare run
babysitter run:assign-process <runDir> --entry <path>#<export> [--process-id <id>] --json
# Status
babysitter run:status <runId> --json
# Iterate
babysitter run:iterate <runId> --json --iteration <n>
# Events
babysitter run:events <runId> --limit 20 --reverse
# Rebuild state
babysitter run:rebuild-state <runId>
```
### Task Commands
```bash
# List pending
babysitter task:list <runId> --pending --json
# Show details
babysitter task:show <runId> <effectId> --json
# Post result
babysitter task:post <runId> <effectId> --status ok --value <file> --json
```
---
---
## Breakpoint Rule Commands
Commands for managing breakpoint auto-approval rules. Rules are stored at `~/.a5c/breakpoint-approvals/rules.json`.
### breakpoint:approve-rule
Add or update an auto-approval rule.
```bash
babysitter breakpoint:approve-rule <pattern> [--action auto-approve|never-auto-approve] [--source <source>] [--note <note>] [--json]
```
| Argument/Flag | Required | Description |
|---------------|----------|-------------|
| `<pattern>` | Yes | Pattern to match breakpointIds. Supports glob (`confirm.*`) and attribute predicates (`*.review(tags contains 'design')`). |
| `--action` | No | Rule action: `auto-approve` (default) or `never-auto-approve`. |
| `--source` | No | Who created the rule (e.g., `cli`, `agent`, `analyze-history`). |
| `--note` | No | Human-readable note about why this rule exists. |
| `--json` | No | Emit JSON output. |
### breakpoint:remove-rule
Remove an auto-approval rule by ID.
```bash
babysitter breakpoint:remove-rule <ruleId> [--json]
```
### breakpoint:list-rules
List all configured auto-approval rules.
```bash
babysitter breakpoint:list-rules [--json]
```
### breakpoint:should-auto-approve
Check whether a breakpoint should be auto-approved given current rules.
```bash
babysitter breakpoint:should-auto-approve <breakpointId> [--tags <csv>] [--expert <expert>] [--json]
```
| Flag | Description |
|------|-------------|
| `--tags` | Comma-separated list of tags to evaluate against rules. |
| `--expert` | Expert identifier to evaluate against rules. |
### breakpoint:history
View breakpoint approval history from run journals.
```bash
babysitter breakpoint:history [--breakpoint-id <id>] [--runs-dir <dir>] [--limit <n>] [--json]
```
| Flag | Description |
|------|-------------|
| `--breakpoint-id` | Filter history to a specific breakpointId. |
| `--runs-dir` | Override runs directory (default: `.a5c/runs`). |
| `--limit` | Maximum number of entries to display (default: 50). |
---
## Related Documentation
- [Breakpoints Feature Guide](../features/breakpoints.md) - Breakpoint usage, auto-approval rules, and patterns
- [Glossary](./glossary.md) - Term definitions
- [Configuration Reference](./configuration.md) - Environment variables and settings
- [Troubleshooting](./troubleshooting.md) - Common issues and solutions
documents
[]
Outgoing edges
None.
Incoming edges
None.