Babysitter CLI
An orchestrator for agents: the workflow is defined in code, every step is enforced, key points need human approval and decisions go into an immutable journal
- 1,907 ★ on the repository
- Last commit
- MIT
Broad access
Why this level
- Directs agents and runs steps that execute code
- Can run complex multi-step processes autonomously between checkpoints
Install
- Works in
In your terminal, with SkillFoxx CLI
npx skillfoxx add cli/babysitterDetects the agents on your machine, shows the access level and pins the version.
Other ways to install
Access and checks
How we reviewBroad accessThe tool can change data, run commands or handle secrets.
- Directs agents and runs steps that execute code
- Can run complex multi-step processes autonomously between checkpoints
This is third-party code. Review the repository files before installing.
What it does
Babysitter makes teams of agents follow a defined process strictly. The workflow is described in code, and the orchestrator ensures each step runs and quality gates pass before moving on. At checkpoints it requires human approval, and it records every decision in an immutable journal. It installs as a CLI via npm, with plugins for Claude Code, Codex and Cursor for specific agents.
Who it is for. For teams and developers running complex multi-step tasks on agents who want predictability.
Good fit when
- You need a strict, repeatable process for agents
- You need quality gates and human approval between steps
- You need a journal of every decision
Not a fit when
- The task is simple and needs no orchestration
- You want agent freedom without strict rails
Example request
Run this task through Babysitter step by step with quality gates and a stop for my approvalLimitations
The process must be described in code, which takes setup time. The orchestrator runs steps that execute code, so use it in a controlled environment. The agents themselves call their models, whose availability from Russia should be checked separately.
How to disable. Remove the @a5c-ai/babysitter package via npm and uninstall the added plugins from your agents.
FAQ
How is the process defined?
In code: you set the steps and checks, and the orchestrator enforces them and keeps a journal.
Does it replace the agent?
No, it directs your agents and hosts rather than replacing them.
Discussion
No questions or reviews yet.
Related
CLI toolsA harness for long-running tasks: Claude Code or Codex becomes an orchestrator that launches workers and testers and decides when to stop
A memory and coordination layer for coding agents: specs and issues live in git while agents work in parallel
A skill that turns the main Claude Code session into a dispatcher: tasks go to background subagents and the chat never blocks.
Multi-agent orchestration for Claude Code: teams, roles, autopilot and task routing across skills and subagents
CLI Agent Orchestrator
CLI Agent Orchestrator (CAO)
A CLI that coordinates several coding agents: a supervisor delegates tasks to specialists in parallel or in sequence across isolated tmux sessions
Self-hosted system for a team of AI agents: org chart, tasks, budgets and oversight of Claude Code, Codex and OpenClaw
README in short
The README describes Babysitter as a deterministic orchestrator for teams of agents, with the process defined in code. It installs via npm as a global CLI, with separate plugins for Claude Code, Codex and Cursor. It lists quality gates, checkpoints with human approval and an immutable decision journal. It also mentions a runtime package for orchestration and build commands.