Skip to content
Back to search

babysitter

MarketplaceWorks with Claude CodeGitHub

Babysitter enforces obedience on agentic workforces and enables them to manage extremely complex tasks and workflows through deterministic, hallucination-free self-orchestration

Safety scan

A static text scan, not a guarantee. Select the badge to see what was scanned and every finding.

Checked today
Badge for your README
findsafeskills safety rating

Markdown

[![findsafeskills safety rating](/api/listings/a5c-ai-babysitter/badge.svg)](/listings/a5c-ai-babysitter)

HTML

<a href="/listings/a5c-ai-babysitter"><img src="/api/listings/a5c-ai-babysitter/badge.svg" alt="findsafeskills safety rating" /></a>

Install

Install instructions from the README

As written by the repo's author. findsafeskills has not verified these steps.

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](docs/user-guide/reference/adapters-cli.md). - `@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](docs/user-guide/reference/adapters-cli.md):

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](docs/user-guide/harnesses/install-matrix.md). Install the plugin for your harness of choice; the two fully-worked harnesses have dedicated pages — [Claude Code](docs/user-guide/harnesses/claude-code.md) and [Codex](docs/user-guide/harnesses/codex.md). In this repository, [`plugins/babysitter-unified`](plugins/babysitter-unified/plugin.json) is the only maintained plugin source; harness-specific bundles are generated during build/release and are not committed:

Claude Code

Native marketplace install:

claude plugin marketplace add a5c-ai/babysitter-claude
claude plugin install --scope user babysitter@a5c.ai

Restart Claude Code, then type `/skills` to verify "babysit" appears.

Claude Cowork can install the same plugin. For a personal install from this repo's Claude marketplace:

1. Open Claude Desktop and switch to the `Cowork` tab. 2. Click `Customize` in the left sidebar. 3. Click `Browse plugins`. 4. Select `Personal`. 5. Click `+`, then choose `Add marketplace from GitHub`. 6. Enter `https://github.com/a5c-ai/babysitter`. 7. Install the `Babysitter` plugin from that marketplace.

For Team and Enterprise org-managed installs, owners can add plugins through `Organization settings > Plugins`. GitHub-synced organization marketplaces require a private or internal GitHub repository, so use a private/internal fork of this repo for that flow, or upload plugin ZIPs manually.

[Plugin README](plugins/babysitter-unified/per-harness/claude-code/README.md)

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](plugins/babysitter-unified/per-harness/codex/README.md)

Cursor IDE and CLI (Experimental)

Via the Cursor marketplace or the SDK helper:

babysitter harness:install-plugin cursor

[Plugin README](plugins/babysitter-unified/per-harness/cursor/README.md)

Gemini CLI (Experimental)

babysitter harness:install-plugin gemini-cli

[Plugin README](plugins/babysitter-unified/per-harness/gemini/README.md)

GitHub Copilot (Experimental)

Via the GitHub Copilot CLI marketplace, or:

babysitter harness:install-plugin github-copilot

What was scanned

The files the safety scan read, as written by the repository's author and shown as plain text. Lines with a finding are marked.

.claude-plugin/marketplace.json · Manifest · 26 lines

View this file on GitHub (read at the repository's current version: the scan did not record which commit it read)

  1. {
  2. "name": "babysitter",
  3. "owner": {
  4. "name": "a5c.ai",
  5. "email": "support@a5c.ai"
  6. },
  7. "interface": {
  8. "displayName": "Babysitter"
  9. },
  10. "plugins": [
  11. {
  12. "name": "babysitter",
  13. "version": "6.0.2",
  14. "source": {
  15. "source": "url",
  16. "url": "https://github.com/a5c-ai/babysitter-claude.git",
  17. "branch": "main"
  18. },
  19. "description": "Babysitter orchestration plugin",
  20. "author": {
  21. "name": "a5c.ai"
  22. },
  23. "repository": "https://github.com/a5c-ai/babysitter-claude"
  24. }
  25. ]
  26. }
README.md · README · 685 lines

View this file on GitHub (read at the repository's current version: the scan did not record which commit it read)

  1. <div align="center">
  2. # Babysitter
  3. > **Enforce obedience on agentic workforces. Manage extremely complex workflows through deterministic, hallucination-free self-orchestration.**
  4. [![npm version](https://img.shields.io/npm/v/@a5c-ai/babysitter.svg)](https://www.npmjs.com/package/@a5c-ai/babysitter)
  5. [![CI](https://img.shields.io/github/actions/workflow/status/a5c-ai/babysitter/ci.yml?branch=staging)](https://github.com/a5c-ai/babysitter/actions/workflows/ci.yml)
  6. [![npm downloads](https://img.shields.io/npm/dm/@a5c-ai/babysitter?label=downloads)](https://www.npmjs.com/package/@a5c-ai/babysitter)
  7. [![Node.js](https://img.shields.io/node/v/@a5c-ai/babysitter)](https://nodejs.org/)
  8. [![License: MIT](https://img.shields.io/badge/License-MIT-yellow.svg)](https://opensource.org/licenses/MIT)
  9. [![GitHub issues](https://img.shields.io/github/issues/a5c-ai/babysitter.svg)](https://github.com/a5c-ai/babysitter/issues)
  10. [![GitHub stars](https://img.shields.io/github/stars/a5c-ai/babysitter.svg)](https://github.com/a5c-ai/babysitter/stargazers)
  11. ---
  12. [Getting Started](#installation) | [Documentation](#documentation) | [Community](#community-and-support)
  13. </div>
  14. ---
  15. https://github.com/user-attachments/assets/8c3b0078-9396-48e8-aa43-5f40da30c20b
  16. ---
  17. ## Table of Contents
  18. - [What is Babysitter?](#what-is-babysitter)
  19. - [Prerequisites](#prerequisites)
  20. - [Installation](#installation)
  21. - [First Steps](#first-steps)
  22. - [Quick Start](#quick-start)
  23. - [Agent Runtime CLI](#agent-runtime-cli)
  24. - [How It Works](#how-it-works)
  25. - [Why Babysitter?](#why-babysitter)
  26. - [Blueprints](#blueprints)
  27. - [Compression](#compression)
  28. - [Documentation](#documentation)
  29. - [Contributing](#contributing)
  30. - [Community and Support](#community-and-support)
  31. - [License](#license)
  32. ---
  33. ## What is Babysitter?
  34. Babysitter enforces obedience to agentic workforces, enabling them to manage extremely complex tasks and workflows through deterministic, hallucination-free self-orchestration. Define your workflow in code - Babysitter enforces every step, ensures quality gates pass before progression, requires human approval at breakpoints, and records every decision in an immutable journal. Your agents do exactly what the process permits, nothing more.
  35. As of v6, Babysitter is harness-agnostic via its **Adapters** runtime: the same processes run across the 12 supported AI coding harnesses, so you are not locked to a single tool. See [Adapters](docs/user-guide/features/adapters.md) and the [harness install matrix](docs/user-guide/harnesses/install-matrix.md).
  36. ---
  37. ## Prerequisites
  38. - **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).
  39. - **A supported AI coding harness**: any of the 12 harnesses covered in the [install matrix](docs/user-guide/harnesses/install-matrix.md) (e.g. Claude Code — [docs](https://code.claude.com/docs/en/quickstart)).
  40. - **Git**: For cloning (optional)
  41. ---
  42. ## Installation
  43. 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:
  44. - `@a5c-ai/babysitter` is the recommended end-user install for the main `babysitter` CLI.
  45. - `@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](docs/user-guide/reference/adapters-cli.md).
  46. - `@a5c-ai/babysitter-sdk` is the public SDK/library package and the underlying implementation behind the core CLI.
  47. - `@a5c-ai/genty-platform` is the optional runtime CLI for `genty call`, `resume`, `start-server`, `tui`, and other orchestration/runtime commands.
  48. - 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.
  49. For most users, install the main CLI first:
  50. ```bash
  51. npm install -g @a5c-ai/babysitter
  52. ```
  53. 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](docs/user-guide/reference/adapters-cli.md):
  54. ```bash
  55. npm install -g @a5c-ai/adapters-cli
  56. adapters doctor
  57. adapters run claude "explain this codebase"
  58. ```
  59. Babysitter supports the 12 AI coding harnesses listed in the [install matrix](docs/user-guide/harnesses/install-matrix.md). Install the plugin for your harness of choice; the two fully-worked harnesses have dedicated pages — [Claude Code](docs/user-guide/harnesses/claude-code.md) and [Codex](docs/user-guide/harnesses/codex.md).
  60. In this repository, [`plugins/babysitter-unified`](plugins/babysitter-unified/plugin.json) is the only maintained plugin source; harness-specific bundles are generated during build/release and are not committed:
  61. ### Claude Code
  62. Native marketplace install:
  63. ```bash
  64. claude plugin marketplace add a5c-ai/babysitter-claude
  65. claude plugin install --scope user babysitter@a5c.ai
  66. ```
  67. Restart Claude Code, then type `/skills` to verify "babysit" appears.
  68. Claude Cowork can install the same plugin. For a personal install from this
  69. repo's Claude marketplace:
  70. 1. Open Claude Desktop and switch to the `Cowork` tab.
  71. 2. Click `Customize` in the left sidebar.
  72. 3. Click `Browse plugins`.
  73. 4. Select `Personal`.
  74. 5. Click `+`, then choose `Add marketplace from GitHub`.
  75. 6. Enter `https://github.com/a5c-ai/babysitter`.
  76. 7. Install the `Babysitter` plugin from that marketplace.
  77. For Team and Enterprise org-managed installs, owners can add plugins through
  78. `Organization settings > Plugins`. GitHub-synced organization marketplaces
  79. require a private or internal GitHub repository, so use a private/internal fork
  80. of this repo for that flow, or upload plugin ZIPs manually.
  81. [Plugin README](plugins/babysitter-unified/per-harness/claude-code/README.md)
  82. ### Codex CLI (Beta)
  83. Official marketplace install:
  84. ```bash
  85. codex plugin marketplace add a5c-ai/babysitter-codex
  86. codex plugin add babysitter --marketplace babysitter
  87. ```
  88. > `--marketplace babysitter` is the marketplace **name** declared in the repo's
  89. > `.agents/plugins/marketplace.json` (not the repo name).
  90. [Plugin README](plugins/babysitter-unified/per-harness/codex/README.md)
  91. ### Cursor IDE and CLI (Experimental)
  92. Via the Cursor marketplace or the SDK helper:
  93. ```bash
  94. babysitter harness:install-plugin cursor
  95. ```
  96. [Plugin README](plugins/babysitter-unified/per-harness/cursor/README.md)
  97. ### Gemini CLI (Experimental)
  98. ```bash
  99. babysitter harness:install-plugin gemini-cli
  100. ```
  101. [Plugin README](plugins/babysitter-unified/per-harness/gemini/README.md)
  102. ### GitHub Copilot (Experimental)
  103. Via the GitHub Copilot CLI marketplace, or:
  104. ```bash
  105. babysitter harness:install-plugin github-copilot
  106. ```
  107. [Plugin README](plugins/babysitter-unified/per-harness/github/README.md)
  108. ### Pi (Experimental)
  109. ```bash
  110. babysitter harness:install-plugin pi
  111. ```
  112. [Plugin README](plugins/babysitter-unified/per-harness/pi/README.md)
  113. ### Hermes (Experimental)
  114. ```bash
  115. babysitter harness:install-plugin hermes
  116. ```
  117. [Plugin README](plugins/babysitter-unified/per-harness/hermes/README.md)
  118. ### Oh-My-Pi (Experimental)
  119. ```bash
  120. babysitter harness:install-plugin oh-my-pi
  121. ```
  122. [Plugin README](plugins/babysitter-unified/per-harness/omp/README.md)
  123. ### OpenCode (Experimental)
  124. ```bash
  125. babysitter harness:install-plugin opencode
  126. ```
  127. [Plugin README](plugins/babysitter-unified/per-harness/opencode/README.md)
  128. ### OpenClaw (Experimental)
  129. ```bash
  130. babysitter harness:install-plugin openclaw
  131. ```
  132. [Plugin README](plugins/babysitter-unified/per-harness/openclaw/README.md)
  133. ### Internal Harness (No AI Coding Agent Required)
  134. Babysitter ships with a built-in **internal harness** that runs processes programmatically without any external AI coding agent. This is useful for CI/CD pipelines, scripts, automated testing, and headless orchestration:
  135. ```bash
  136. npm install -g @a5c-ai/genty-platform
  137. # Run a process definition using the internal harness
  138. genty call --harness internal --process .a5c/processes/my-process.js#process --workspace .
  139. # Or run a free-form prompt
  140. genty call --harness internal --prompt "run lint and tests" --workspace .
  141. ```
  142. The internal harness uses the SDK's built-in Pi execution engine directly. It supports all capabilities (Programmatic, SessionBinding, StopHook, HeadlessPrompt) and requires no external AI harness CLI.
  143. During process execution, the internal harness can **delegate tasks to any discovered installed harness** via the invoker. A process running under `--harness internal` can spawn subagent tasks that execute through Claude Code, Codex, Gemini CLI, or any other harness found on the system -- the SDK discovers available harness CLIs at runtime and routes task execution accordingly. This means you can orchestrate a multi-agent workflow from a single headless entry point, with different tasks delegated to whichever harness is best suited for them.
  144. ---
  145. ## Runtime Package Builds
  146. 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:
  147. ```bash
  148. npm ci
  149. npm run build:runtime
  150. ```
  151. `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.
  152. Package-local validation is also supported:
  153. ```bash
  154. npm run build --workspace=@a5c-ai/genty-core
  155. npm run build --workspace=@a5c-ai/genty-platform
  156. ```
  157. 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.
  158. `@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`](packages/atlas/README.md).
  159. ### CLI Walkthrough Verification
  160. 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:
  161. ```bash
  162. npm ci
  163. npm run build --workspace=@a5c-ai/babysitter-sdk
  164. npm run docs:prepare
  165. npm run docs:examples:smoke
  166. npm run docs:qa
  167. ```
  168. `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`.
  169. ---
  170. ## First Steps
  171. After installation, set up your environment:
  172. ### 1. Configure Your Profile (One-Time)
  173. ```bash
  174. /babysitter:user-install
  175. ```
  176. This creates your personal profile with:
  177. - Breakpoint preferences (how much oversight you want)
  178. - Tool preferences and communication style
  179. - Expertise areas for better process matching
  180. ### 2. Set Up Your Project
  181. ```bash
  182. /babysitter:project-install
  183. ```
  184. This analyzes your codebase and configures:
  185. - Project-specific workflows
  186. - Test frameworks and CI/CD integration
  187. - Tech stack preferences
  188. ### 3. Verify Setup
  189. ```bash
  190. /babysitter:doctor
  191. ```
  192. Run diagnostics to confirm everything is working.
  193. ---
  194. ## Quick Start
  195. ```bash
  196. claude "/babysitter:call implement user authentication with TDD"
  197. ```
  198. Or in natural language:
  199. ```
  200. Use the babysitter skill to implement user authentication with TDD
  201. ```
  202. Claude will create an orchestration run, execute tasks step-by-step, handle quality checks and approvals, and continue until completion.
  203. ### Choose Your Mode
  204. | Mode | Command | When to Use |
  205. |------|---------|-------------|
  206. | **Interactive** | `/babysitter:call` | Learning, critical workflows - pauses for approval |
  207. | **Autonomous** | `/babysitter:yolo` | Trusted tasks - full auto, no breakpoints |
  208. | **Planning** | `/babysitter:plan` | Review process before executing |
  209. | **Continuous** | `/babysitter:forever` | Monitoring, periodic tasks - runs indefinitely |
  210. ### Utility Commands
  211. | Command | Purpose |
  212. |---------|----------|
  213. | `/babysitter:doctor` | Diagnose run health and issues |
  214. | `/babysitter:observe` | Launch real-time monitoring dashboard |
  215. | `/babysitter:resume` | Continue an interrupted run |
  216. | `/babysitter:help` | Documentation and usage help |
  217. ---
  218. ## Agent Runtime CLI
  219. Beyond the in-session skill commands (`/babysitter:call`, etc.), Babysitter provides an optional agent runtime CLI package, `@a5c-ai/genty-platform`, for orchestration, session management, MCP serving, daemon utilities, and the TUI. The main `babysitter` CLI comes from `@a5c-ai/babysitter` and is backed by `@a5c-ai/babysitter-sdk`; it keeps the core run/task/session/plugin surfaces plus `harness:install` and `harness:install-plugin`.
  220. ```bash
  221. npm install -g @a5c-ai/babysitter
  222. npm install -g @a5c-ai/genty-platform
  223. ```
  224. ### Running Processes via a Harness
  225. ```bash
  226. # Run a process interactively via Claude Code (pauses at breakpoints)
  227. genty call --harness claude-code --prompt "implement user authentication with TDD" --workspace .
  228. # Run fully autonomous (no breakpoints)
  229. genty yolo --harness claude-code --prompt "add pagination to the API" --workspace .
  230. # Plan only (stops after Phase 1)
  231. genty plan --harness claude-code --prompt "implement feature X"
  232. # Run with the internal harness (no external AI agent needed)
  233. genty call --harness internal --prompt "run lint and tests" --workspace .
  234. ```
  235. ### Managing Runs
  236. ```bash
  237. # Resume an interrupted run
  238. genty resume --run-id <runId> --harness claude-code --workspace .
  239. # Initialize or inspect orchestration session state
  240. babysitter session:init --session-id demo --state-dir .a5c --run-id <runId>
  241. babysitter session:state --session-id demo --state-dir .a5c
  242. # Start the MCP server owned by the agent runtime CLI
  243. genty start-server --transport stdio
  244. # Diagnose run health
  245. genty doctor --run-id <runId>
  246. # Analyze past runs for insights
  247. genty retrospect --all --harness claude-code --workspace .
  248. # Clean up old runs
  249. genty cleanup --keep-days 7 --harness claude-code --workspace .
  250. ```
  251. ### Harness Discovery
  252. ```bash
  253. # Install an agent harness CLI (preferred)
  254. adapters install claude-code
  255. # Install a Babysitter harness plugin globally
  256. babysitter harness:install-plugin claude-code
  257. # Install a Babysitter harness plugin into a workspace
  258. babysitter harness:install-plugin codex --workspace /path/to/repo
  259. ```
  260. > **Note:** `babysitter harness:install` and `babysitter harness:discover` are deprecated. Use `adapters install <agent>` for agent installation and `genty` for runtime commands.
  261. `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`.
  262. ### Using `--harness internal` for Automation
  263. The `internal` harness is particularly useful for CI/CD and scripting because it requires no external AI coding agent:
  264. ```bash
  265. # In a CI pipeline or script
  266. genty call \
  267. --harness internal \
  268. --process .a5c/processes/lint-and-test.js#process \
  269. --workspace . \
  270. --no-interactive \
  271. --json
  272. ```
  273. 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.
  274. ### Package Boundaries
  275. | Package | Installs | Use it for |
  276. |---------|----------|------------|
  277. | `@a5c-ai/babysitter` | `babysitter` | Recommended human-facing install for the main CLI |
  278. | `@a5c-ai/babysitter-sdk` | `babysitter`, `babysitter-sdk`, `babysitter-mcp-server` | SDK/library usage and direct access to the core CLI implementation |
  279. | `@a5c-ai/genty-platform` | `genty` | Optional runtime/orchestration commands (`call`, `resume`, `plan`, `start-server`, `tui`, `doctor`) |
  280. | `@a5c-ai/babysitter-<harness>` | Harness-specific installer or plugin binary | Integrating Babysitter into a specific host tool such as Codex, Cursor, Gemini CLI, Pi, or GitHub Copilot |
  281. The repository root `package.json` is workspace metadata for this monorepo. The public packages users install are the scoped packages above.
  282. ### Monorepo Structure
  283. ```
  284. packages/
  285. genty/ # genty agent stack
  286. cli/ # @a5c-ai/genty — CLI binary "genty"
  287. core/ # @a5c-ai/genty-core — agent-core runtime
  288. platform/ # @a5c-ai/genty-platform — orchestration platform
  289. runtime/ # @a5c-ai/genty-runtime — agent runtime
  290. ui/ webui/ tui/ # UI surfaces (web console, terminal UI)
  291. adapters/ # Adapter family
  292. sdk/ # @a5c-ai/adapters — root SDK + CLI "adapters"
  293. codecs/ # @a5c-ai/adapters-codecs — harness codec impls
  294. cli/ # @a5c-ai/adapters-cli
  295. gateway/ # @a5c-ai/adapters-gateway
  296. hooks/ # hooks-adapter-* (per-harness hook adapters)
  297. core/ transport/ ... # comm-adapter, transport-adapter, etc.
  298. atlas/ # @a5c-ai/atlas — knowledge graph + catalog
  299. sdk/ # @a5c-ai/babysitter-sdk — core SDK
  300. kradle/ # @a5c-ai/kradle — Kubernetes-native forge
  301. core/ sdk/ cli/ web/
  302. kip-sdk/ # @a5c-ai/kip-sdk — signed git-substrate memory SDK (private/unpublished)
  303. plugins/ # Installable plugin packages
  304. babysitter-unified/ # Unified plugin for all harnesses
  305. blueprints/ # Blueprint marketplace registry
  306. a5c/marketplace/
  307. library/ # Process library (methodologies + specializations)
  308. ```
  309. **Adjacent: `kip-sdk` (memory substrate).** `packages/kip-sdk` (`@a5c-ai/kip-sdk`) is a signed, git-substrate, bitemporal, typed property-graph memory SDK — a durable memory layer where every fact is an append-only, Ed25519-signed record and reads are a deterministic projection over the fact set. It ships a working `open()`/`KipRepo` SDK, a `kip` CLI, a `kip-mcp` server, and graph-QA (`kip ask`). It is built and runnable but `private`/`0.0.1` (unpublished — consume it via the monorepo workspace or the built `dist/`, not `npm install`). See the [kip-sdk README](packages/kip-sdk/README.md) and the [ecosystem overview](docs/user-guide/ecosystem/kip-sdk.md).
  310. ---
  311. ## How It Works
  312. ```
  313. +=============================================================================+
  314. | /babysitter:call |
  315. +=============================================================================+
  316. | |
  317. | YOUR PROCESS (JavaScript) This is the AUTHORITY |
  318. | +----------------------------------------+ |
  319. | | async function process(inputs, ctx) { | Real code, not config. |
  320. | | | The orchestrator can ONLY |
  321. | | await ctx.task(plan, { ... }); | do what this code permits. |
  322. | | | |
  323. | | await ctx.breakpoint({ | Breakpoints = human gates |
  324. | | question: 'Approve plan?' | (enforced, not optional) |
  325. | | }); | |
  326. | | | |
  327. | | await ctx.task(implement, { ... }); | Tasks = executable work |
  328. | | | |
  329. | | const score = await ctx.task(verify);| Quality gates = code logic |
  330. | | if (score < 80) | (not config, real checks) |
  331. | | await ctx.task(refine, { ... }); | |
  332. | | } | |
  333. | +-------------------+--------------------+ |
  334. | | |
  335. | | governs |
  336. | v |
  337. | +---------------------------------------------------------------------+ |
  338. | | ENFORCEMENT MECHANISM | |
  339. | | | |
  340. | | +-------------+ +------------------+ +-----------------+ | |
  341. | | | MANDATORY |---->| PROCESS CHECK |---->| DECISION | | |
  342. | | | STOP | | What does the | | | | |
  343. | | | (enforced | | process permit | | Permitted: next | | |
  344. | | | by hook) | | next? | | task assigned | | |
  345. | | +-------------+ +------------------+ | | | |
  346. | | | | Blocked: halt | | |
  347. | | v | until gate | | |
  348. | | +--------------+ | passes | | |
  349. | | | Gate/task | +-----------------+ | |
  350. | | | from code | | |
  351. | | +--------------+ | |
  352. | +---------------------------------------------------------------------+ |
  353. | | |
  354. | | records every decision |
  355. | v |
  356. | +---------------------------------------------------------------------+ |
  357. | | JOURNAL: Every task, gate, decision - immutable, replayable | |
  358. | +---------------------------------------------------------------------+ |
  359. | |
  360. +=============================================================================+
  361. ```
  362. **The difference from simple iteration:**
  363. - **Process as Code:** Your workflow is JavaScript - the orchestrator can ONLY do what this code permits
  364. - **Mandatory Stop:** Claude cannot "keep running" - every step ends with a forced stop, then the process decides what's next
  365. - **Enforcement, not Assistance:** Gates block progression until satisfied - they're not suggestions
  366. - **Event-Sourced Journal:** All run state in `~/.a5c/runs/` by default, with repo-local `.a5c/runs/` compatibility reads - deterministic replay and resume from any point
  367. ---
  368. ## Why Babysitter?
  369. | Traditional Approach | Babysitter |
  370. |---------------------|------------|
  371. | Agent decides what to do and when it's "done" | Orchestrator can only do what your process code permits |
  372. | Ad-hoc workflow | Deterministic, code-defined processes — mandatory stop after every step (enforcement, not assistance) |
  373. | Single task execution | Complex agentic workflows: parallel execution, dependencies, sub-agent delegation across harnesses |
  374. | State lost on session end | Event-sourced, deterministic replay, fully resumable |
  375. | Manual approval via chat | Structured breakpoints with context |
  376. | No audit trail | Complete journal of all events |
  377. | Run script once, hope it works | Gates (including quality gates) block progression until satisfied |
  378. **Key differentiators:** Process enforcement, deterministic replay, human-in-the-loop breakpoints, parallel execution, and quality convergence (one gate type among several).
  379. ---
  380. ## Blueprints
  381. Babysitter has its own blueprint system -- and it works differently from what you might expect. A blueprint is not a code module with extension points. It's a **set of natural language instructions** (markdown files) or **deterministic coded processes** (JS files) that an AI agent reads and executes. The SDK stores, versions, and distributes the instructions. The AI agent is the runtime.
  382. This means a blueprint can do anything an AI agent can do: install npm packages, generate CI/CD pipelines, set up git hooks, create Terraform configs, modify your linter rules, copy babysitter processes into your project, and interview you about your preferences along the way.
  383. The official marketplace includes blueprints for **security** (gitleaks, ESLint security rules, audit processes), **testing** (Vitest/Playwright/pytest setup, coverage gates, TDD processes), **deployment** (Terraform, Helm, Dockerfiles, multi-environment pipelines), **themes** (sound effects, design systems, conversational personality), **CI/CD** (GitHub Actions workflows), and **rate limiting** (exponential backoff hooks).
  384. To manage blueprints, use the `/babysitter:blueprints` command inside your harness (or `babysitter blueprints:*` from the CLI). The agent reads the blueprint's install instructions, interviews you, analyzes your project, and executes the setup -- all within a babysitter orchestration run.
  385. See the full [Blueprints documentation](docs/blueprints.md) for details on how installs work, the marketplace format, creating your own blueprints, and the migration system. Agent harness plugins are covered separately in [Plugins documentation](docs/plugins.md).
  386. ---
  387. ## Compression
  388. Babysitter includes a 4-layer token compression subsystem (built into `packages/babysitter-sdk/`) that reduces context window usage by 50-67% on real sessions while maintaining 99% fact retention.
  389. All compression hooks are **automatically registered** by the babysitter plugin -- no manual `settings.json` configuration needed. Install the plugin and compression is active.
  390. ### How It Works
  391. | Layer | Hook | Engine | Content | Reduction |
  392. |---|---|---|---|---|
  393. | 1a | userPromptHook | density-filter | User prompts | ~29% |
  394. | 1b | commandOutputHook | command-compressor | Bash/shell output | ~47% avg |
  395. | 2 | sdkContextHook | sentence-extractor | Agent/task context | ~87% |
  396. | 3 | processLibraryCache | sentence-extractor | Library files (pre-cached) | ~94% |
  397. ### Quick Toggle
  398. ```bash
  399. # Disable all compression
  400. export BABYSITTER_COMPRESSION_ENABLED=false
  401. # Disable a single layer
  402. babysitter compression:toggle sdkContextHook off
  403. # Show current effective config
  404. babysitter compression:config
  405. ```
  406. ### Config File
  407. Edit `.a5c/compression.config.json` to persist settings (env vars always take priority):
  408. ```json
  409. {
  410. "enabled": true,
  411. "layers": {
  412. "userPromptHook": { "enabled": true, "threshold": 500, "keepRatio": 0.78 },
  413. "commandOutputHook": { "enabled": true, "excludeCommands": ["jq", "curl", "docker"] },
  414. "sdkContextHook": { "enabled": true, "targetReduction": 0.15, "minCompressionTokens": 150 },
  415. "processLibraryCache": { "enabled": true, "targetReduction": 0.35, "ttlHours": 24 }
  416. }
  417. }
  418. ```
  419. Toggle any layer with `babysitter compression:toggle <layer> <on|off>` or set individual values with `babysitter compression:set <key> <value>`.
  420. ---
  421. ## Documentation
  422. <!-- docs-surface-map:start -->
  423. ### Package and Plugin Surface Map
  424. - [Package and Plugin Docs Map](docs/package-and-plugin-map.md) - canonical public/internal status, docs entrypoints, and coverage notes for active packages and plugins
  425. <!-- docs-surface-map:end -->
  426. ### Getting Started
  427. - [Quickstart Guide](docs/user-guide/getting-started/quickstart.md)
  428. - [Beginner Tutorial: REST API](docs/user-guide/tutorials/beginner-rest-api.md)
  429. - [Best Practices](docs/user-guide/features/best-practices.md)
  430. - [Migration Guide (0.0.x → v6)](docs/user-guide/getting-started/migration.md)
  431. ### Features
  432. - [Adapters](docs/user-guide/features/adapters.md) - Harness-agnostic runtime across the 12 supported harnesses
  433. - [Harness Install Matrix](docs/user-guide/harnesses/install-matrix.md) - Per-harness install instructions and invocation tokens
  434. - [Process Library](docs/user-guide/features/process-library.md) - 2,000+ pre-built processes
  435. - [Process Definitions](docs/user-guide/features/process-definitions.md)
  436. - [Quality Convergence](docs/user-guide/features/quality-convergence.md)
  437. - [Run Resumption](docs/user-guide/features/run-resumption.md)
  438. - [Journal System](docs/user-guide/features/journal-system.md)
  439. - [Best Practices](docs/user-guide/features/best-practices.md)
  440. - [Architecture Overview](docs/user-guide/features/architecture-overview.md)
  441. ### Reference
  442. - [FAQ](docs/user-guide/reference/faq.md)
  443. - [Troubleshooting](docs/user-guide/reference/troubleshooting.md)
  444. - [Security](docs/user-guide/reference/security.md)
  445. - [CLI Reference](docs/user-guide/reference/cli-reference.md) - The core `babysitter` CLI
  446. - [Adapters CLI Reference](docs/user-guide/reference/adapters-cli.md) - The host-side `adapters` CLI
  447. - [Atlas Knowledge Graph](packages/atlas/README.md)
  448. ---
  449. ## Contributing
  450. We welcome contributions! Here's how you can help:
  451. - **Report bugs**: [GitHub Issues](https://github.com/a5c-ai/babysitter/issues)
  452. - **Suggest features**: Share your ideas for improvements
  453. - **Submit pull requests**: Fix bugs or add features
  454. - **Improve documentation**: Help make docs clearer
  455. - **Check workspace coverage**: [docs/workspace-validation.md](docs/workspace-validation.md)
  456. See [CONTRIBUTING.md](https://github.com/a5c-ai/babysitter/blob/main/CONTRIBUTING.md) for detailed guidelines.
  457. ---
  458. ## Community and Support
  459. - **Discord**: [Join our community](https://discord.gg/dHGkzxf48a) *(GitHub invite link)*
  460. - **GitHub Issues**: [Report bugs or request features](https://github.com/a5c-ai/babysitter/issues)
  461. - **GitHub Discussions**: [Ask questions and share ideas](https://github.com/a5c-ai/babysitter/discussions)
  462. - **npm**: [@a5c-ai/babysitter](https://www.npmjs.com/package/@a5c-ai/babysitter)
  463. ### Community Tools
  464. | Tool | Description |
  465. |------|-------------|
  466. | [Observer Dashboard](https://github.com/a5c-ai/babysitter) | Real-time monitoring UI for parallel runs — install and launch with the built-in `/babysitter:observe` command |
  467. | [Telegram Bot](https://github.com/a5c-ai/claude-code-telegram-bot) | Control sessions remotely |
  468. | [vibe-kanban](https://github.com/BloopAI/vibe-kanban) | Parallel process management |
  469. ### Star History
  470. <a href="https://star-history.com/#a5c-ai/babysitter&Date">
  471. <picture>
  472. <source media="(prefers-color-scheme: dark)" srcset="https://api.star-history.com/svg?repos=a5c-ai/babysitter&type=Date&theme=dark" />
  473. <source media="(prefers-color-scheme: light)" srcset="https://api.star-history.com/svg?repos=a5c-ai/babysitter&type=Date" />
  474. <img alt="Star History Chart" src="https://api.star-history.com/svg?repos=a5c-ai/babysitter&type=Date" />
  475. </picture>
  476. </a>
  477. ### Contributors
  478. <a href="https://github.com/a5c-ai/babysitter/graphs/contributors">
  479. <img src="https://contrib.rocks/image?repo=a5c-ai/babysitter" />
  480. </a>
  481. ---
  482. ## License
  483. This project is licensed under the **MIT License**. See [LICENSE.md](https://github.com/a5c-ai/babysitter/blob/main/LICENSE.md) for details.
  484. ---
  485. <div align="center">
  486. **Built with Claude by A5C AI**
  487. [Back to Top](#babysitter)
  488. </div>

Ratings and comments

Sign in to rate this skill.

Sign in

Free to use. If it’s helped, pass it on.