@a5c-ai/babysitter-codex 5.0.1-staging.cb276e93 → 5.0.1-staging.cdf798a9f097

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "babysitter",
3
- "version": "5.0.0",
3
+ "version": "5.0.1-staging.cdf798a9f097",
4
4
  "description": "Orchestrate complex, multi-step workflows with event-sourced state management, hook-based extensibility, and human-in-the-loop approval",
5
5
  "author": {
6
6
  "name": "a5c.ai",
@@ -45,5 +45,5 @@
45
45
  "composerIcon": "./assets/icon.svg",
46
46
  "logo": "./assets/logo.png"
47
47
  },
48
- "homepage": "https://github.com/a5c-ai/babysitter/tree/main/plugins/babysitter-codex#readme"
48
+ "homepage": "https://github.com/a5c-ai/babysitter/tree/main/plugins/babysitter-unified/per-harness/codex#readme"
49
49
  }
package/README.md CHANGED
@@ -17,23 +17,36 @@ workspace-local Codex surface for team setup.
17
17
 
18
18
  ## Installation
19
19
 
20
- Install the SDK CLI first:
20
+ Install the Babysitter CLI once:
21
21
 
22
22
  ```bash
23
- npm install -g @a5c-ai/babysitter-sdk
23
+ npm install -g @a5c-ai/babysitter
24
24
  ```
25
25
 
26
- clone the repo and install the plugin globally:
26
+ Install the Codex plugin through the SDK helper. This is the canonical path used by the installer tests and resolves to `npx --yes @a5c-ai/babysitter-codex install ...` under the hood:
27
27
 
28
28
  ```bash
29
- npx -y @a5c-ai/babysitter-codex install --global
29
+ # Global install
30
+ babysitter harness:install-plugin codex
30
31
 
31
- codex
32
+ # Workspace install
33
+ babysitter harness:install-plugin codex --workspace /path/to/repo
34
+ ```
35
+
36
+ You can also run the published package installer directly:
37
+
38
+ ```bash
39
+ npx --yes @a5c-ai/babysitter-codex install --global
40
+ npx --yes @a5c-ai/babysitter-codex install --workspace /path/to/repo
41
+ ```
42
+
43
+ Then open Codex and finish enabling the plugin from the plugin UI:
32
44
 
33
- > /plugins
45
+ ```text
46
+ /plugins
34
47
  ```
35
48
 
36
- then navigate to the 'babysitter' entry and select 'Install'.
49
+ Navigate to the `babysitter` entry and select `Install`.
37
50
 
38
51
  If Codex was already open when you ran `install --global`, start a new thread
39
52
  after installing from `/plugins` before expecting `babysitter:*` skills such as
@@ -104,7 +104,7 @@ function ensureMarketplaceEntry(marketplacePath, pluginRoot) {
104
104
  name: PLUGIN_NAME,
105
105
  source: relSource,
106
106
  description: "Orchestrate complex, multi-step workflows with event-sourced state management, hook-based extensibility, and human-in-the-loop approval",
107
- version: "5.0.0",
107
+ version: "5.0.1-staging.cdf798a9f097",
108
108
  author: { name: "a5c.ai" },
109
109
  };
110
110
  if (idx >= 0) marketplace.plugins[idx] = entry;
@@ -297,7 +297,7 @@ function renderCodexConfigToml() {
297
297
  'writable_roots = [".a5c", ".codex"]',
298
298
  '',
299
299
  '[features]',
300
- 'codex_hooks = true',
300
+ 'hooks = true',
301
301
  'multi_agent = true',
302
302
  '',
303
303
  '[agents]',
@@ -406,7 +406,7 @@ function mergeCodexConfig(existing) {
406
406
  content = insertRootKey(content, 'sandbox_mode', 'sandbox_mode = "workspace-write"');
407
407
  content = insertRootKey(content, 'project_doc_max_bytes', 'project_doc_max_bytes = 65536');
408
408
  content = ensureWritableRoots(content);
409
- content = ensureSectionLine(content, 'features', 'codex_hooks', 'codex_hooks = true');
409
+ content = ensureSectionLine(content, 'features', 'hooks', 'hooks = true');
410
410
  content = ensureSectionLine(content, 'features', 'multi_agent', 'multi_agent = true');
411
411
  content = ensureSectionLine(content, 'agents', 'max_depth', 'max_depth = 3');
412
412
  content = ensureSectionLine(content, 'agents', 'max_threads', 'max_threads = 4');
@@ -0,0 +1,3 @@
1
+ #!/bin/bash
2
+ set -euo pipefail
3
+ babysitter hook:run --harness unified --hook-type post-tool-use --json
@@ -0,0 +1,3 @@
1
+ #!/bin/bash
2
+ set -euo pipefail
3
+ babysitter hook:run --harness unified --hook-type pre-tool-use --json
@@ -0,0 +1,3 @@
1
+ #!/bin/bash
2
+ set -euo pipefail
3
+ babysitter hook:run --harness unified --hook-type session-end --json
File without changes
File without changes
File without changes
package/hooks.json CHANGED
@@ -6,7 +6,7 @@
6
6
  "hooks": [
7
7
  {
8
8
  "type": "command",
9
- "command": "npx -y -p @a5c-ai/hooks-mux-cli -c \"a5c-hooks-mux invoke --adapter codex --handler 'bash ./hooks/babysitter-proxied-session-start.sh' --json\""
9
+ "command": "a5c-hooks-mux invoke --adapter codex --handler \"bash .codex/hooks/babysitter-proxied-session-start.sh\" --json"
10
10
  }
11
11
  ]
12
12
  }
@@ -17,7 +17,7 @@
17
17
  "hooks": [
18
18
  {
19
19
  "type": "command",
20
- "command": "npx -y -p @a5c-ai/hooks-mux-cli -c \"a5c-hooks-mux invoke --adapter codex --handler 'bash ./hooks/babysitter-proxied-stop.sh' --json\""
20
+ "command": "a5c-hooks-mux invoke --adapter codex --handler \"bash .codex/hooks/babysitter-proxied-stop.sh\" --json"
21
21
  }
22
22
  ]
23
23
  }
@@ -28,7 +28,40 @@
28
28
  "hooks": [
29
29
  {
30
30
  "type": "command",
31
- "command": "npx -y -p @a5c-ai/hooks-mux-cli -c \"a5c-hooks-mux invoke --adapter codex --handler 'bash ./hooks/babysitter-proxied-user-prompt-submit.sh' --json\""
31
+ "command": "a5c-hooks-mux invoke --adapter codex --handler \"bash .codex/hooks/babysitter-proxied-user-prompt-submit.sh\" --json"
32
+ }
33
+ ]
34
+ }
35
+ ],
36
+ "PreToolUse": [
37
+ {
38
+ "matcher": ".*",
39
+ "hooks": [
40
+ {
41
+ "type": "command",
42
+ "command": "a5c-hooks-mux invoke --adapter codex --handler \"bash .codex/hooks/babysitter-proxied-pre-tool-use.sh\" --json"
43
+ }
44
+ ]
45
+ }
46
+ ],
47
+ "PostToolUse": [
48
+ {
49
+ "matcher": ".*",
50
+ "hooks": [
51
+ {
52
+ "type": "command",
53
+ "command": "a5c-hooks-mux invoke --adapter codex --handler \"bash .codex/hooks/babysitter-proxied-post-tool-use.sh\" --json"
54
+ }
55
+ ]
56
+ }
57
+ ],
58
+ "SessionEnd": [
59
+ {
60
+ "matcher": ".*",
61
+ "hooks": [
62
+ {
63
+ "type": "command",
64
+ "command": "a5c-hooks-mux invoke --adapter codex --handler \"bash .codex/hooks/babysitter-proxied-session-end.sh\" --json"
32
65
  }
33
66
  ]
34
67
  }
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@a5c-ai/babysitter-codex",
3
- "version": "5.0.1-staging.cb276e93",
3
+ "version": "5.0.1-staging.cdf798a9f097",
4
4
  "description": "Orchestrate complex, multi-step workflows with event-sourced state management, hook-based extensibility, and human-in-the-loop approval",
5
5
  "scripts": {
6
6
  "test": "npm run validate:ci",
@@ -38,11 +38,10 @@
38
38
  },
39
39
  "repository": {
40
40
  "type": "git",
41
- "url": "git+https://github.com/a5c-ai/babysitter.git",
42
- "directory": "plugins/babysitter-codex"
41
+ "url": "git+https://github.com/a5c-ai/babysitter-codex.git"
43
42
  },
44
- "homepage": "https://github.com/a5c-ai/babysitter/tree/main/plugins/babysitter-codex#readme",
43
+ "homepage": "https://github.com/a5c-ai/babysitter-codex#readme",
45
44
  "bugs": {
46
- "url": "https://github.com/a5c-ai/babysitter/issues"
45
+ "url": "https://github.com/a5c-ai/babysitter-codex/issues"
47
46
  }
48
47
  }
@@ -0,0 +1,18 @@
1
+ #!/usr/bin/env node
2
+ import { spawnSync } from 'node:child_process';
3
+ import { existsSync, readFileSync } from 'node:fs';
4
+
5
+ function run(command, args) {
6
+ const result = spawnSync(command, args, { encoding: 'utf8', stdio: 'inherit' });
7
+ if (result.status !== 0) process.exit(result.status || 1);
8
+ }
9
+
10
+ const branch = process.env.GITHUB_REF_NAME || 'develop';
11
+ const sha = (process.env.GITHUB_SHA || '').slice(0, 12);
12
+ const version = existsSync('package.json') ? JSON.parse(readFileSync('package.json', 'utf8')).version : JSON.parse(readFileSync('versions.json', 'utf8')).sdkVersion;
13
+ const normalized = String(version).replace(/[^0-9A-Za-z._-]/g, '-');
14
+ const tag = 'release/' + branch + '/v' + normalized + '-' + sha;
15
+ run('git', ['config', 'user.name', 'github-actions[bot]']);
16
+ run('git', ['config', 'user.email', 'github-actions[bot]@users.noreply.github.com']);
17
+ run('git', ['tag', tag]);
18
+ run('git', ['push', 'origin', tag]);
@@ -0,0 +1,41 @@
1
+ #!/usr/bin/env node
2
+ import { spawnSync } from 'node:child_process';
3
+ import { readFileSync } from 'node:fs';
4
+
5
+ function run(command, args, options = {}) {
6
+ const result = spawnSync(command, args, { stdio: options.stdio || 'inherit', encoding: options.encoding });
7
+ if (result.status !== 0 && !options.allowFailure) process.exit(result.status || 1);
8
+ return result;
9
+ }
10
+
11
+ function npmView(packageSpec) {
12
+ return run('npm', ['view', packageSpec, 'version'], { allowFailure: true, stdio: 'pipe', encoding: 'utf8' }).status === 0;
13
+ }
14
+
15
+ const pkg = JSON.parse(readFileSync('package.json', 'utf8'));
16
+ const ref = process.env.GITHUB_REF_NAME || '';
17
+ const branch = ref.split('/')[1] || 'develop';
18
+ const tag = branch === 'main' ? 'latest' : branch;
19
+
20
+ if (!process.env.NODE_AUTH_TOKEN) {
21
+ console.log('NODE_AUTH_TOKEN is not configured; skipping npm publish.');
22
+ process.exit(0);
23
+ }
24
+
25
+ if (npmView(pkg.name + '@' + pkg.version)) {
26
+ console.log(pkg.name + '@' + pkg.version + ' already exists; ensuring dist-tag ' + tag + '.');
27
+ run('npm', ['dist-tag', 'add', pkg.name + '@' + pkg.version, tag], { allowFailure: true });
28
+ process.exit(0);
29
+ }
30
+
31
+ for (const field of ['dependencies', 'peerDependencies', 'optionalDependencies']) {
32
+ for (const [name, version] of Object.entries(pkg[field] || {})) {
33
+ if (!name.startsWith('@a5c-ai/') || version.startsWith('^') || version.startsWith('~') || version === '*' || version.startsWith('workspace:')) continue;
34
+ if (!npmView(name + '@' + version)) {
35
+ console.log('Required internal dependency ' + name + '@' + version + ' is not published yet; skipping npm publish.');
36
+ process.exit(0);
37
+ }
38
+ }
39
+ }
40
+
41
+ run('npm', ['publish', '--access', 'public', '--tag', tag]);
@@ -1,14 +1,12 @@
1
1
  ---
2
2
  name: babysit
3
3
  description: >-
4
- Orchestrate via @babysitter. Use this skill when asked to babysit a run,
5
- orchestrate a process or whenever it is called explicitly. (babysit,
6
- babysitter, orchestrate, orchestrate a run, workflow, etc.)
4
+ Execute via @babysitter. Use this skill when asked to babysit a task, do anything that is structured process-driven (even a loop) or whenever it is called explicitly. (babysit, babysitter, with a process, orchestrate, orchestrate a run, workflow, loop until, etc.)
7
5
  ---
8
6
 
9
7
  # babysit
10
8
 
11
- Orchestrate `.a5c/runs/<runId>/` through iterative execution.
9
+ Follow the commands below exactly. but apply judgement and creativity to get the job done. no matter how small or simple the task may seem, you must use the babysitter SDK and run lifecycle to execute it. This is non-negotiable. If you are asked to do something that seems like it could be done with a simple tool call, you must still use the babysitter SDK to create a run, define tasks, execute them, and complete the run. This is how you will learn and demonstrate mastery of the babysitter system. Always follow the full process, even for trivial tasks.
12
10
 
13
11
  ## Dependencies
14
12
 
@@ -5,4 +5,8 @@ description: Orchestrate a babysitter run. use this command to start babysitting
5
5
 
6
6
  # call
7
7
 
8
- Invoke the babysitter:babysit skill (using the Skill tool) and follow its instructions (SKILL.md).
8
+ Invoke the babysitter:babysit skill (using the Skill tool) and follow its instructions (SKILL.md). Then continue executing the returned instructions in this same turn. Do not stop after the Skill tool returns; carry the requested run through to completion proof.
9
+
10
+ User arguments for this command:
11
+
12
+ $ARGUMENTS
@@ -11,11 +11,33 @@ Create and run a cleanup process using the process at `skills\babysit\process\cr
11
11
 
12
12
  Implementation notes (for the process):
13
13
  - Parse arguments for `--dry-run` flag (if present, set dryRun: true in inputs) and `--keep-days N` (default: 7)
14
- - The process scans .a5c/runs/ for completed/failed runs, aggregates insights, writes summaries, then removes old data
15
- - Always show the user what will be removed before removing (in interactive mode via breakpoints)
16
- - In non-interactive mode (yolo), proceed with cleanup using defaults
17
- - The insights file goes to docs/run-history-insights.md
18
- - Only remove terminal runs (completed/failed) older than the keep-days threshold
19
- - Never remove active/in-progress runs
20
- - Remove orphaned process files not referenced by remaining runs
21
- - After cleanup, show remaining run count and disk usage
14
+
15
+ CRITICAL: The cleanup MUST follow this exact phase order. Do NOT delete any run before Phase 2 completes.
16
+
17
+ Phase 1 Scan:
18
+ - Scan .a5c/runs/ for all runs
19
+ - Classify each as terminal (completed/failed) or active (in-progress/created)
20
+ - Identify terminal runs older than the keep-days threshold as removal candidates
21
+ - Never mark active/in-progress runs for removal
22
+ - Count and report: total runs, terminal, active, removal candidates, disk usage
23
+
24
+ Phase 2 — Aggregate insights (BEFORE any deletion):
25
+ - For EVERY removal candidate, read its run.json and journal/ events
26
+ - Extract: processId, prompt, status, event count, created date, task summaries
27
+ - Group by process type and extract patterns (retry counts, convergence behavior, failure modes)
28
+ - Append a new dated section to docs/run-history-insights.md with:
29
+ - Summary statistics (runs removed, disk freed, runs retained)
30
+ - Run categories with counts and descriptions
31
+ - Key patterns observed (multi-batch convergence, retry behavior, etc.)
32
+ - What worked well / what didn't from the run data
33
+ - This file MUST be written and verified before proceeding to Phase 3
34
+
35
+ Phase 3 — Confirm removal:
36
+ - In interactive mode, show the user what will be removed via a breakpoint
37
+ - In non-interactive mode (yolo), proceed with defaults
38
+ - In dry-run mode, stop here and show what would be removed
39
+
40
+ Phase 4 — Remove:
41
+ - Delete the terminal runs older than keep-days threshold
42
+ - Identify and remove orphaned process files not referenced by remaining runs
43
+ - Show remaining run count and disk usage after cleanup
@@ -157,7 +157,6 @@ If it exists:
157
157
  **Goal:** Inspect babysitter session files for health and detect runaway loops.
158
158
 
159
159
  - Search for session state files using Glob:
160
- - `plugins/babysitter/skills/babysit/state/*.md`
161
160
  - `.a5c/state/*.md`
162
161
  - `.a5c/state/*.json`
163
162
  - For each session state file found:
@@ -261,7 +260,7 @@ Mark as PASS if total size < 500MB and no files > 10MB. Mark as WARN if total si
261
260
 
262
261
  ### 10a. Hook Registration
263
262
 
264
- - Locate the plugin root. Check for `CLAUDE_PLUGIN_ROOT` env var, or search for `plugins/babysitter/hooks/hooks.json` by walking up from the current directory.
263
+ - Locate the plugin root. Check for `CLAUDE_PLUGIN_ROOT` env var first, or search for a babysitter `hooks.json` by walking up from the current directory.
265
264
  - If found, read `hooks.json` and verify:
266
265
  - A `Stop` hook entry exists with a command referencing `babysitter-stop-hook.sh`.
267
266
  - A `SessionStart` hook entry exists with a command referencing `babysitter-session-start-hook.sh`.
@@ -316,7 +315,7 @@ If the stop hook shows NO evidence of execution (no log entries, no journal even
316
315
 
317
316
  Perform these diagnostic steps in order and report the first failure found:
318
317
 
319
- 1. **Plugin not installed**: Check if `plugins/babysitter/` exists relative to the project root and if `CLAUDE_PLUGIN_ROOT` is set. If the plugin directory doesn't exist, report: "Plugin not installed — the babysitter plugin directory is missing."
318
+ 1. **Plugin not installed**: Check if `CLAUDE_PLUGIN_ROOT` is set or if a babysitter plugin directory exists relative to the project root. If neither exists, report: "Plugin not installed — the babysitter plugin directory is missing."
320
319
 
321
320
  2. **Plugin not enabled**: Check for Claude settings files:
322
321
  - `~/.claude/settings.json` — look for `babysitter` in `enabledPlugins`.
@@ -234,7 +234,8 @@ SECONDARY COMMANDS
234
234
  How it works: Runs npx @a5c-ai/babysitter-observer-dashboard@latest which watches
235
235
  the .a5c/runs/ directory (or a parent directory containing multiple projects) and
236
236
  serves a live dashboard. The process is blocking -- it runs until you stop it, and
237
- it prints the local URL to share with the user.
237
+ it prints the local URL to share with the user. Do not use `babysitter observe`
238
+ as a fallback; the core Babysitter CLI does not expose that subcommand.
238
239
 
239
240
  Example: /babysitter:observe
240
241
  (opens browser showing all runs with live-updating task
@@ -8,6 +8,11 @@ description: Launch the babysitter observer dashboard. Installs and runs the rea
8
8
  Run the babysitter observer dashboard:
9
9
 
10
10
  1. Determine the watch directory — this is usually the project's container directory (the parent of the project dir), or the current working directory if not specified.
11
- 2. Launch the dashboard: `npx -y @a5c-ai/babysitter-observer-dashboard@latest --watch-dir <dir>`
11
+ 2. Launch the standalone dashboard package: `npx -y @a5c-ai/babysitter-observer-dashboard@latest --watch-dir <dir>`.
12
12
  3. This is a blocking process — it will keep running until stopped.
13
13
  4. Report the URL printed by the dashboard to the user, then open it in the browser.
14
+
15
+ Do not fall back to `babysitter observe`; the core Babysitter CLI does not expose
16
+ that subcommand. Some harness runtimes may provide a separate
17
+ `agent-platform observe` surface, but this skill uses the verified standalone
18
+ dashboard package.
@@ -5,4 +5,8 @@ description: Orchestrate a babysitter run. use this command to start babysitting
5
5
 
6
6
  # yolo
7
7
 
8
- Invoke the babysitter:babysit skill (using the Skill tool) and follow its instructions (SKILL.md). but without any user interaction or breakpoints in the run.
8
+ Run the Babysitter orchestration instructions directly through the CLI, without any user interaction or breakpoints. In Claude Code, use Bash to run `babysitter instructions:babysit-skill --harness claude-code --no-interactive`; in Codex, run `babysitter instructions:babysit-skill --harness codex --no-interactive`; in other harnesses, use the same command with that harness id. Then follow the returned instructions in this same turn until completion proof is produced. Do not stop after reading the instructions, do not invoke the Skill tool first, and use the non-interactive/no-breakpoints path when the instructions offer a mode choice.
9
+
10
+ User arguments for this command:
11
+
12
+ $ARGUMENTS
@@ -1,46 +0,0 @@
1
- #!/usr/bin/env node
2
- 'use strict';
3
-
4
- const fs = require('fs');
5
- const path = require('path');
6
- const {
7
- listDirectories,
8
- reportCheckResult,
9
- syncSkillsFromCommands,
10
- } = require('../../../scripts/plugin-command-sync-lib.cjs');
11
-
12
- const PACKAGE_ROOT = path.resolve(__dirname, '..');
13
- const REPO_ROOT = path.resolve(PACKAGE_ROOT, '..', '..');
14
- const COMMANDS_ROOT = path.join(REPO_ROOT, 'plugins', 'babysitter', 'commands');
15
- const SKILLS_ROOT = path.join(PACKAGE_ROOT, 'skills');
16
- const LABEL = 'babysitter-codex sync';
17
-
18
- function getCommandBackedSkillNames() {
19
- return listDirectories(SKILLS_ROOT)
20
- .filter((name) => fs.existsSync(path.join(COMMANDS_ROOT, `${name}.md`)));
21
- }
22
-
23
- function main() {
24
- const result = syncSkillsFromCommands({
25
- label: LABEL,
26
- sourceRoot: COMMANDS_ROOT,
27
- skillsRoot: SKILLS_ROOT,
28
- names: getCommandBackedSkillNames(),
29
- check: process.argv.includes('--check'),
30
- cwd: PACKAGE_ROOT,
31
- });
32
-
33
- if (process.argv.includes('--check')) {
34
- reportCheckResult(LABEL, result.stale);
35
- return;
36
- }
37
-
38
- if (result.updated === 0) {
39
- console.log(`[${LABEL}] no Codex skill changes were needed.`);
40
- return;
41
- }
42
-
43
- console.log(`[${LABEL}] updated ${result.updated} Codex skill file(s).`);
44
- }
45
-
46
- main();