Babysitter
Babysitter enforces obedience on agentic workforces and enables them to manage extremely complex tasks and workflows through deterministic, hallucination-free self-orchestration
Install
claude plugin install --scope user babysitter@a5c.aiInstall command taken from the project's README or registry entry. Always review code before running it.
README excerpt
Read full README on GitHub →Babysitter
Enforce obedience on agentic workforces. Manage extremely complex workflows through deterministic, hallucination-free self-orchestration.
Getting Started | Documentation | Community
https://github.com/user-attachments/assets/8c3b0078-9396-48e8-aa43-5f40da30c20b
Table of Contents
- What is Babysitter?
- Prerequisites
- Installation
- First Steps
- Quick Start
- Agent Runtime CLI
- How It Works
- Why Babysitter?
- Blueprints
- Compression
- Documentation
- Contributing
- Community and Support
- License
What is Babysitter?
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.
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 and the harness install matrix.
Prerequisites
- Node.js: Version 20.0.0+ (22.x LTS recommended). The host-side
adaptersCLI pins a higher floor of 22.13.0+ (it loads the gateway's built-innode: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/babysitteris the recommended end-user install for the mainbabysitterCLI.@a5c-ai/adapters-cliprovides the host-sideadaptersCLI (Node >=22.13.0) for running and managing any supported harness from your shell. See the Adapters CLI reference.@a5c-ai/babysitter-sdkis the public SDK/library package and the underlying implementation behind the core CLI.@a5c-ai/genty-platformis the optional runtime CLI forgenty call,resume,start-server,tui, and other orchestration/runtime commands.- Harness plugins such as
@a5c-ai/babysitter-codexor@a5c-ai/babysitter-cursorintegrate 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
Similar plugs
Makes your AI agent think like the laziest senior dev in the room. The best code is the code you never wrote.
Turn any codebase, with its docs, SQL schemas, configs, and PDFs, into a queryable knowledge graph. A /graphify skill for Claude Code, Cursor, Codex, and Gemini CLI: local…
Why use many token when few token do trick. Viral skill + proxy for coding agents that cuts 65% of tokens by talking like a caveman.
Production-grade engineering skills for AI coding agents.
The 1st Collaborative AI Design Agent Workspace. Local-first and open source. Create prototypes, websites, apps, dashboards, presentations, images, and videos with your team…