Docs › Getting Started › Migration

Migration Guide: Prod (0.0.x) to v6 (6.0.0)

**Category:** Getting Started · **Last Updated:** 2026-06-22

On this page

• In Plain English
• Version Jump
• Breaking Changes
• Deprecated (still works, will be removed)
• Migration Checklist
• Related Documentation

---

In Plain English

**v6 is a major upgrade. The biggest change is that Babysitter is now harness-agnostic (via Adapters) instead of Claude-only.** Along with that come a few breaking changes: the install package changed, two environment variables were renamed, one flag was removed, and the plugins/ directory was renamed to blueprints/.

This page lists every breaking change and what to do about it. Read it before upgrading from the 0.0.x series (last prod release: 0.0.175).

---

Version Jump

This is a deliberate **semver-major jump**. Treat the upgrade as a breaking change and test your processes after migrating.

---

Breaking Changes

1. Install package changed

The primary install is now **@a5c-ai/babysitter** (core CLI), not @a5c-ai/babysitter-sdk.

# Before (prod)
npm install -g @a5c-ai/babysitter-sdk@latest

# v6
npm install -g @a5c-ai/babysitter
npm install -g @a5c-ai/adapters-cli   # new host-side CLI

The toolchain is now split across @a5c-ai/babysitter (core CLI), @a5c-ai/babysitter-sdk (programmatic runtime), and @a5c-ai/genty-platform. See Installation.

2. Environment variable renames

Session resolution is now **PID-scoped** rather than env-first. If you relied on inheriting a session ID from the environment, set BABYSITTER_TRUST_ENV_SESSION=1 as an explicit escape hatch. See Configuration and Run Resumption.

3. Removed flag: `--plugin-root`

--plugin-root is **removed**. Plugin/root resolution is handled by the harness-agnostic runtime. Remove it from any scripts.

4. `plugins/` → `blueprints/`

The processes directory was renamed:

Update any paths and scripts that referenced plugins/. See Process Library.

5. Concept and package renames

6. Harness model

Babysitter is no longer wired specifically to Claude Code's Stop hook. The orchestration runtime is harness-agnostic, and each harness has its own continuation model. If you wrote integration code against the Claude Stop loop, see Adapters and Hooks.

---

Deprecated (still works, will be removed)

• plugin:* command aliases (use blueprints:*)
• BABYSITTER_SESSION_ID (use AGENT_SESSION_ID)
• breakpoints-pro references (use the Breakpoints Adapter)

These are marked deprecated throughout the docs and will be removed in a future release.

---

Migration Checklist

1. [ ] Upgrade Node.js to >=20.9.0 (for the Adapters CLI). 2. [ ] Install @a5c-ai/babysitter and @a5c-ai/adapters-cli. 3. [ ] Replace BABYSITTER_SESSION_ID with AGENT_SESSION_ID in env/scripts. 4. [ ] Remove --plugin-root from any commands. 5. [ ] Rename plugins/ references to blueprints/. 6. [ ] Reinstall your harness plugin from the Install Matrix. 7. [ ] Run adapters doctor and a smoke test (adapters run claude "say hi"). 8. [ ] Re-run a known process to confirm behavior.

---

Related Documentation

• Installation · Quickstart
• Adapters · Hooks
• Configuration · Glossary
• Install Matrix

---

Next steps

• **Next:** Installation — install the v6 packages
• **Related:** CLI Reference
• **Related:** Adapters CLI