babysitter AI工具

Prerequisites

• Node.js: Version 20.0.0+ (22.x LTS recommended). The host-side adapters CLI pins a higher floor of 22.13.0+ (it loads the gateway's built-in node:sqlite, unflagged only from Node 22.13.0).
• A supported AI coding harness: any of the 12 harnesses covered in the install matrix (e.g. Claude Code — docs).
• Git: For cloning (optional)

---

Installation

Babysitter v6 has two install tracks that should not be conflated: the host-side adapters CLI for running any harness directly from your shell, and the in-session per-harness plugin for driving full orchestration runs from inside your harness. Most people want both. The package split is:

• @a5c-ai/babysitter is the recommended end-user install for the main babysitter CLI.
• @a5c-ai/adapters-cli provides the host-side adapters CLI (Node >=22.13.0) for running and managing any supported harness from your shell. See the Adapters CLI reference.
• @a5c-ai/babysitter-sdk is the public SDK/library package and the underlying implementation behind the core CLI.
• @a5c-ai/genty-platform is the optional runtime CLI for genty call, resume, start-server, tui, and other orchestration/runtime commands.
• Harness plugins such as @a5c-ai/babysitter-codex or @a5c-ai/babysitter-cursor integrate Babysitter into a specific host tool. They do not replace the core CLI packages.

For most users, install the main CLI first:

npm install -g @a5c-ai/babysitter

Prefer to drive a harness directly from your shell instead of from inside a session? Install the host-side adapters CLI and run any supported harness with one command — see the Adapters CLI reference:

npm install -g @a5c-ai/adapters-cli
adapters doctor
adapters run claude "explain this codebase"

Babysitter supports the 12 AI coding harnesses listed in the install matrix. Install the plugin for your harness of choice; the two fully-worked harnesses have dedicated pages — Claude Code and Codex. In this repository, plugins/babysitter-unified is the only maintained plugin source; harness-specific bundles are generated during build/release and are not committed:

Runtime Package Builds

For the core runtime chain (@a5c-ai/babysitter-sdk, @a5c-ai/adapters, @a5c-ai/genty-core, @a5c-ai/genty-platform), use the shared workspace entrypoint from a fresh checkout:

npm ci
npm run build:runtime

build:runtime is the supported root entrypoint for release and CI validation. It builds the runtime graph in workspace order: SDK -> adapters SDK surface -> genty-core -> genty-platform.

Package-local validation is also supported:

npm run build --workspace=@a5c-ai/genty-core
npm run build --workspace=@a5c-ai/genty-platform

Those package-local builds now use tsc --build project references where the runtime packages are owned in this workspace, and they explicitly bootstrap the @a5c-ai/adapters SDK chain through the root runtime scripts. Fresh-checkout validation no longer assumes prebuilt upstream dist/ artifacts.

@a5c-ai/atlas provides the unified knowledge graph, ontology, and catalog data consumed by SDK, adapters, hooks, plugin tooling, and the catalog UI. The agent catalog surface is @a5c-ai/atlas/catalog. See packages/atlas/README.md.

3. Verify Setup

/babysitter:doctor

Run diagnostics to confirm everything is working.

---

Install an agent harness CLI (preferred)

adapters install claude-code

Install a Babysitter harness plugin globally

babysitter harness:install-plugin claude-code

Install a Babysitter harness plugin into a workspace

babysitter harness:install-plugin codex --workspace /path/to/repo ```

Note: babysitter harness:install and babysitter harness:discover are deprecated. Use adapters install <agent> for agent installation and genty for runtime commands.

harness:install-plugin is the canonical scriptable install path for Babysitter plugins. For non-Claude harnesses it resolves to the published package installer shape tested in the SDK, for example npx --yes @a5c-ai/babysitter-codex install --workspace /path/to/repo.

Getting Started

• Quickstart Guide
• Beginner Tutorial: REST API
• Best Practices
• Migration Guide (0.0.x → v6)

Quick Start

claude "/babysitter:call implement user authentication with TDD"

Or in natural language:

Use the babysitter skill to implement user authentication with TDD

Claude will create an orchestration run, execute tasks step-by-step, handle quality checks and approvals, and continue until completion.

1. Configure Your Profile (One-Time)

/babysitter:user-install

This creates your personal profile with: - Breakpoint preferences (how much oversight you want) - Tool preferences and communication style - Expertise areas for better process matching

Show current effective config

babysitter compression:config ```

Config File

Edit .a5c/compression.config.json to persist settings (env vars always take priority):

{
  "enabled": true,
  "layers": {
    "userPromptHook":    { "enabled": true, "threshold": 500, "keepRatio": 0.78 },
    "commandOutputHook": { "enabled": true, "excludeCommands": ["jq", "curl", "docker"] },
    "sdkContextHook":    { "enabled": true, "targetReduction": 0.15, "minCompressionTokens": 150 },
    "processLibraryCache": { "enabled": true, "targetReduction": 0.35, "ttlHours": 24 }
  }
}

Toggle any layer with babysitter compression:toggle <layer> <on|off> or set individual values with babysitter compression:set <key> <value>.

---

Codex CLI (Beta)

Official marketplace install:

codex plugin marketplace add a5c-ai/babysitter-codex
codex plugin add babysitter --marketplace babysitter

--marketplace babysitter is the marketplace name declared in the repo's .agents/plugins/marketplace.json (not the repo name).

Plugin README

Cursor IDE and CLI (Experimental)

Via the Cursor marketplace or the SDK helper:

babysitter harness:install-plugin cursor

Plugin README

Gemini CLI (Experimental)

babysitter harness:install-plugin gemini-cli

Plugin README

CLI Walkthrough Verification

The published CLI walkthrough at docs/cli-examples.md is verified against the real repo surfaces, not a separate docs-only harness. From a fresh checkout, use:

npm ci
npm run build --workspace=@a5c-ai/babysitter-sdk
npm run docs:prepare
npm run docs:examples:smoke
npm run docs:qa

npm run docs:examples:verify runs that docs-focused flow end-to-end. The generated traceability map for the walkthrough lives at docs/generated/cli-examples-verification.md.

---

Reference

• FAQ
• Troubleshooting
• Security
• CLI Reference - The core babysitter CLI
• Adapters CLI Reference - The host-side adapters CLI
• Atlas Knowledge Graph

---

In a CI pipeline or script

genty call \ --harness internal \ --process .a5c/processes/lint-and-test.js#process \ --workspace . \ --no-interactive \ --json ```

It executes processes using the SDK's built-in engine, supports all effect types (tasks, breakpoints, sleeps, parallel dispatch), and produces the same event-sourced journal as any other harness.

Package Boundaries

The repository root package.json is workspace metadata for this monorepo. The public packages users install are the scoped packages above.

Package and Plugin Surface Map

• Package and Plugin Docs Map - canonical public/internal status, docs entrypoints, and coverage notes for active packages and plugins