@a5c-ai/babysitter-cursor 5.0.1-staging.ff2c19f9 → 5.0.1-staging.ffad3b46492e

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.
package/README.md CHANGED
@@ -19,13 +19,13 @@ hooks so Cursor can execute Babysitter commands and hook scripts directly.
19
19
 
20
20
  ## Installation
21
21
 
22
- Install the SDK CLI first:
22
+ Install the Babysitter CLI once:
23
23
 
24
24
  ```bash
25
- npm install -g @a5c-ai/babysitter-sdk
25
+ npm install -g @a5c-ai/babysitter
26
26
  ```
27
27
 
28
- ### Via Cursor Marketplace (recommended)
28
+ ### Via Cursor Marketplace
29
29
 
30
30
  Install through Cursor's marketplace UI using the repo-root
31
31
  `/.cursor-plugin/marketplace.json` manifest:
@@ -34,10 +34,16 @@ Install through Cursor's marketplace UI using the repo-root
34
34
  2. Open the marketplace entry named **a5c-ai**
35
35
  3. Install the plugin named **babysitter**
36
36
 
37
- ### Via Babysitter harness install
37
+ ### Via Babysitter harness install (recommended for automation)
38
+
39
+ Use the SDK helper for scriptable global or workspace installs. This resolves to `npx --yes @a5c-ai/babysitter-cursor install ...` under the hood:
38
40
 
39
41
  ```bash
42
+ # Global install
40
43
  babysitter harness:install-plugin cursor
44
+
45
+ # Workspace install
46
+ babysitter harness:install-plugin cursor --workspace /path/to/repo
41
47
  ```
42
48
 
43
49
  If the workspace does not already have an active process-library binding, the
@@ -51,18 +57,18 @@ babysitter process-library:active --json
51
57
 
52
58
  For local development or environments without marketplace access:
53
59
 
54
- #### Via npm
60
+ #### Via the published package installer
55
61
 
56
62
  ```bash
57
- npm install -g @a5c-ai/babysitter-cursor
58
- babysitter-cursor install
63
+ npx --yes @a5c-ai/babysitter-cursor install --global
64
+ npx --yes @a5c-ai/babysitter-cursor install --workspace /path/to/repo
59
65
  ```
60
66
 
61
- #### From source
67
+ #### From generated source
62
68
 
63
69
  ```bash
64
- cd plugins/babysitter-cursor
65
- node bin/install.js
70
+ npm run generate:plugins
71
+ node artifacts/generated-plugins/cursor/bin/install.js
66
72
  ```
67
73
 
68
74
  #### Manual installation
@@ -70,9 +76,9 @@ node bin/install.js
70
76
  Copy the plugin directory to your local Cursor plugins path:
71
77
 
72
78
  ```bash
73
- cp -r plugins/babysitter-cursor ~/.cursor/plugins/local/babysitter-cursor
79
+ cp -r artifacts/generated-plugins/cursor ~/.cursor/plugins/local/babysitter-cursor
74
80
  # Or symlink for faster iteration:
75
- ln -s "$(pwd)/plugins/babysitter-cursor" ~/.cursor/plugins/local/babysitter-cursor
81
+ ln -s "$(pwd)/artifacts/generated-plugins/cursor" ~/.cursor/plugins/local/babysitter-cursor
76
82
  ```
77
83
 
78
84
  ## Uninstallation
@@ -90,7 +96,7 @@ npm uninstall -g @a5c-ai/babysitter-cursor
90
96
  ## Plugin Structure (Directory Layout)
91
97
 
92
98
  ```
93
- plugins/babysitter-cursor/
99
+ artifacts/generated-plugins/cursor/
94
100
  .cursor-plugin/
95
101
  plugin.json # Cursor plugin manifest (skills, commands, hooks, metadata)
96
102
  plugin.json # Babysitter plugin manifest (skills dir, hooks path, metadata)
@@ -311,7 +317,7 @@ The Cursor marketplace manifest lives at `.cursor-plugin/plugin.json`:
311
317
  "email": "support@a5c.ai",
312
318
  "url": "https://github.com/a5c-ai/babysitter"
313
319
  },
314
- "homepage": "https://github.com/a5c-ai/babysitter/tree/main/plugins/babysitter-cursor#readme",
320
+ "homepage": "https://github.com/a5c-ai/babysitter/tree/main/plugins/babysitter-unified/per-harness/cursor#readme",
315
321
  "repository": "https://github.com/a5c-ai/babysitter",
316
322
  "license": "MIT",
317
323
  "skills": "skills/",
@@ -438,14 +444,14 @@ or WSL. The Cursor hook manifest includes explicit `powershell` entries alongsid
438
444
  git clone https://github.com/a5c-ai/babysitter.git
439
445
  cd babysitter
440
446
  npm install
441
- cd plugins/babysitter-cursor
447
+ npm run generate:plugins
442
448
  node bin/install.js
443
449
  ```
444
450
 
445
451
  ### Publishing
446
452
 
447
453
  ```bash
448
- cd plugins/babysitter-cursor
454
+ cd artifacts/generated-plugins/cursor
449
455
  npm run deploy # Publish to npm (public)
450
456
  npm run deploy:staging # Publish to npm with staging tag
451
457
  ```
@@ -453,7 +459,7 @@ npm run deploy:staging # Publish to npm with staging tag
453
459
  ### Team installation
454
460
 
455
461
  ```bash
456
- cd plugins/babysitter-cursor
462
+ cd artifacts/generated-plugins/cursor
457
463
  npm run team:install
458
464
  ```
459
465
 
@@ -13,7 +13,7 @@ function getUserHome() {
13
13
  }
14
14
 
15
15
  function getHarnessHome() {
16
- return path.join(os.homedir(), '.cursor');
16
+ return path.join(os.homedir(), ".cursor");
17
17
  }
18
18
 
19
19
  function getHomePluginRoot(scope) {
@@ -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.ffad3b46492e",
108
108
  author: { name: "a5c.ai" },
109
109
  };
110
110
  if (idx >= 0) marketplace.plugins[idx] = entry;
@@ -489,22 +489,22 @@ module.exports = {
489
489
  resolveCliCommand,
490
490
  runCli,
491
491
  ensureGlobalProcessLibrary,
492
- HOOK_SCRIPT_NAMES,
493
- DEFAULT_MARKETPLACE,
494
- MANAGED_HOOKS_CONFIG_PATHS,
495
492
  PLUGIN_BUNDLE_ENTRIES,
496
- getCursorHome,
497
- getHomePluginRoot,
498
- getHomeMarketplacePath,
499
493
  copyRecursive,
500
494
  copyPluginBundle,
495
+ DEFAULT_MARKETPLACE,
501
496
  normalizeMarketplaceSourcePath,
502
497
  normalizeMarketplaceName,
503
498
  ensureMarketplaceEntry,
504
499
  removeMarketplaceEntry,
505
- getManagedHooksConfigPath,
506
500
  mergeManagedHooksConfig,
501
+ warnWindowsHooks,
502
+ HOOK_SCRIPT_NAMES,
503
+ MANAGED_HOOKS_CONFIG_PATHS,
504
+ getCursorHome,
505
+ getHomePluginRoot,
506
+ getHomeMarketplacePath,
507
+ getManagedHooksConfigPath,
507
508
  removeManagedHooks,
508
509
  installCursorSurface,
509
- warnWindowsHooks,
510
510
  };
package/bin/uninstall.js CHANGED
@@ -1,7 +1,6 @@
1
1
  #!/usr/bin/env node
2
2
  'use strict';
3
3
 
4
- const path = require('path');
5
4
  const fs = require('fs');
6
5
  const shared = require('./install-shared');
7
6
 
package/commands/call.md CHANGED
@@ -4,4 +4,8 @@ argument-hint: Specific instructions for the run.
4
4
  allowed-tools: Read, Grep, Write, Task, Bash, Edit, Grep, Glob, WebFetch, WebSearch, Search, AskUserQuestion, TodoWrite, TodoRead, Skill, BashOutput, KillShell, MultiEdit, LS
5
5
  ---
6
6
 
7
- Invoke the babysitter:babysit skill (using the Skill tool) and follow its instructions (SKILL.md).
7
+ 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.
8
+
9
+ User arguments for this command:
10
+
11
+ $ARGUMENTS
@@ -10,11 +10,33 @@ Create and run a cleanup process using the process at `skills\babysit\process\cr
10
10
 
11
11
  Implementation notes (for the process):
12
12
  - Parse arguments for `--dry-run` flag (if present, set dryRun: true in inputs) and `--keep-days N` (default: 7)
13
- - The process scans .a5c/runs/ for completed/failed runs, aggregates insights, writes summaries, then removes old data
14
- - Always show the user what will be removed before removing (in interactive mode via breakpoints)
15
- - In non-interactive mode (yolo), proceed with cleanup using defaults
16
- - The insights file goes to docs/run-history-insights.md
17
- - Only remove terminal runs (completed/failed) older than the keep-days threshold
18
- - Never remove active/in-progress runs
19
- - Remove orphaned process files not referenced by remaining runs
20
- - After cleanup, show remaining run count and disk usage
13
+
14
+ CRITICAL: The cleanup MUST follow this exact phase order. Do NOT delete any run before Phase 2 completes.
15
+
16
+ Phase 1 Scan:
17
+ - Scan .a5c/runs/ for all runs
18
+ - Classify each as terminal (completed/failed) or active (in-progress/created)
19
+ - Identify terminal runs older than the keep-days threshold as removal candidates
20
+ - Never mark active/in-progress runs for removal
21
+ - Count and report: total runs, terminal, active, removal candidates, disk usage
22
+
23
+ Phase 2 — Aggregate insights (BEFORE any deletion):
24
+ - For EVERY removal candidate, read its run.json and journal/ events
25
+ - Extract: processId, prompt, status, event count, created date, task summaries
26
+ - Group by process type and extract patterns (retry counts, convergence behavior, failure modes)
27
+ - Append a new dated section to docs/run-history-insights.md with:
28
+ - Summary statistics (runs removed, disk freed, runs retained)
29
+ - Run categories with counts and descriptions
30
+ - Key patterns observed (multi-batch convergence, retry behavior, etc.)
31
+ - What worked well / what didn't from the run data
32
+ - This file MUST be written and verified before proceeding to Phase 3
33
+
34
+ Phase 3 — Confirm removal:
35
+ - In interactive mode, show the user what will be removed via a breakpoint
36
+ - In non-interactive mode (yolo), proceed with defaults
37
+ - In dry-run mode, stop here and show what would be removed
38
+
39
+ Phase 4 — Remove:
40
+ - Delete the terminal runs older than keep-days threshold
41
+ - Identify and remove orphaned process files not referenced by remaining runs
42
+ - Show remaining run count and disk usage after cleanup
@@ -156,7 +156,6 @@ If it exists:
156
156
  **Goal:** Inspect babysitter session files for health and detect runaway loops.
157
157
 
158
158
  - Search for session state files using Glob:
159
- - `plugins/babysitter/skills/babysit/state/*.md`
160
159
  - `.a5c/state/*.md`
161
160
  - `.a5c/state/*.json`
162
161
  - For each session state file found:
@@ -260,7 +259,7 @@ Mark as PASS if total size < 500MB and no files > 10MB. Mark as WARN if total si
260
259
 
261
260
  ### 10a. Hook Registration
262
261
 
263
- - 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.
262
+ - 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.
264
263
  - If found, read `hooks.json` and verify:
265
264
  - A `Stop` hook entry exists with a command referencing `babysitter-stop-hook.sh`.
266
265
  - A `SessionStart` hook entry exists with a command referencing `babysitter-session-start-hook.sh`.
@@ -315,7 +314,7 @@ If the stop hook shows NO evidence of execution (no log entries, no journal even
315
314
 
316
315
  Perform these diagnostic steps in order and report the first failure found:
317
316
 
318
- 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."
317
+ 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."
319
318
 
320
319
  2. **Plugin not enabled**: Check for Claude settings files:
321
320
  - `~/.claude/settings.json` — look for `babysitter` in `enabledPlugins`.
package/commands/help.md CHANGED
@@ -233,7 +233,8 @@ SECONDARY COMMANDS
233
233
  How it works: Runs npx @a5c-ai/babysitter-observer-dashboard@latest which watches
234
234
  the .a5c/runs/ directory (or a parent directory containing multiple projects) and
235
235
  serves a live dashboard. The process is blocking -- it runs until you stop it, and
236
- it prints the local URL to share with the user.
236
+ it prints the local URL to share with the user. Do not use `babysitter observe`
237
+ as a fallback; the core Babysitter CLI does not expose that subcommand.
237
238
 
238
239
  Example: /babysitter:observe
239
240
  (opens browser showing all runs with live-updating task
@@ -7,6 +7,11 @@ allowed-tools: Read, Grep, Write, Task, Bash
7
7
  Run the babysitter observer dashboard:
8
8
 
9
9
  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.
10
- 2. Launch the dashboard: `npx -y @a5c-ai/babysitter-observer-dashboard@latest --watch-dir <dir>`
10
+ 2. Launch the standalone dashboard package: `npx -y @a5c-ai/babysitter-observer-dashboard@latest --watch-dir <dir>`.
11
11
  3. This is a blocking process — it will keep running until stopped.
12
12
  4. Report the URL printed by the dashboard to the user, then open it in the browser.
13
+
14
+ Do not fall back to `babysitter observe`; the core Babysitter CLI does not expose
15
+ that subcommand. Some harness runtimes may provide a separate
16
+ `agent-platform observe` surface, but this skill uses the verified standalone
17
+ dashboard package.
package/commands/yolo.md CHANGED
@@ -1,7 +1,11 @@
1
- ---
2
- description: Orchestrate a babysitter run. use this command to start babysitting a complex workflow in a non-interactive mode, without any user interaction or breakpoints in the run.
3
- argument-hint: Specific instructions for the run.
4
- allowed-tools: Read, Grep, Write, Task, Bash, Edit, Grep, Glob, WebFetch, WebSearch, Search, AskUserQuestion, TodoWrite, TodoRead, Skill, BashOutput, KillShell, MultiEdit, LS
5
- ---
6
-
7
- 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.
1
+ ---
2
+ description: Orchestrate a babysitter run. use this command to start babysitting a complex workflow in a non-interactive mode, without any user interaction or breakpoints in the run.
3
+ argument-hint: Specific instructions for the run.
4
+ allowed-tools: Read, Grep, Write, Task, Bash, Edit, Grep, Glob, WebFetch, WebSearch, Search, AskUserQuestion, TodoWrite, TodoRead, Skill, BashOutput, KillShell, MultiEdit, LS
5
+ ---
6
+
7
+ 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.
8
+
9
+ User arguments for this command:
10
+
11
+ $ARGUMENTS
@@ -0,0 +1,12 @@
1
+ # PowerShell hook wrapper — sets env vars and delegates to bash
2
+ $env:HOOK_TYPE = 'post-tool-use'
3
+ $env:ADAPTER_NAME = 'cursor'
4
+ $env:PLUGIN_ROOT = Split-Path -Parent (Split-Path -Parent $PSScriptRoot)
5
+
6
+ $input_data = [Console]::In.ReadToEnd()
7
+ $result = $input_data | & bash "$PSScriptRoot/../$($MyInvocation.MyCommand.Name -replace '\.ps1$','.sh')" 2>$null
8
+ if ($LASTEXITCODE -eq 0 -and $result) {
9
+ Write-Output $result
10
+ } else {
11
+ Write-Output '{}'
12
+ }
@@ -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,12 @@
1
+ # PowerShell hook wrapper — sets env vars and delegates to bash
2
+ $env:HOOK_TYPE = 'pre-tool-use'
3
+ $env:ADAPTER_NAME = 'cursor'
4
+ $env:PLUGIN_ROOT = Split-Path -Parent (Split-Path -Parent $PSScriptRoot)
5
+
6
+ $input_data = [Console]::In.ReadToEnd()
7
+ $result = $input_data | & bash "$PSScriptRoot/../$($MyInvocation.MyCommand.Name -replace '\.ps1$','.sh')" 2>$null
8
+ if ($LASTEXITCODE -eq 0 -and $result) {
9
+ Write-Output $result
10
+ } else {
11
+ Write-Output '{}'
12
+ }
@@ -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,12 @@
1
+ # PowerShell hook wrapper — sets env vars and delegates to bash
2
+ $env:HOOK_TYPE = 'session-end'
3
+ $env:ADAPTER_NAME = 'cursor'
4
+ $env:PLUGIN_ROOT = Split-Path -Parent (Split-Path -Parent $PSScriptRoot)
5
+
6
+ $input_data = [Console]::In.ReadToEnd()
7
+ $result = $input_data | & bash "$PSScriptRoot/../$($MyInvocation.MyCommand.Name -replace '\.ps1$','.sh')" 2>$null
8
+ if ($LASTEXITCODE -eq 0 -and $result) {
9
+ Write-Output $result
10
+ } else {
11
+ Write-Output '{}'
12
+ }
@@ -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
@@ -0,0 +1,12 @@
1
+ # PowerShell hook wrapper — sets env vars and delegates to bash
2
+ $env:HOOK_TYPE = 'user-prompt-submit'
3
+ $env:ADAPTER_NAME = 'cursor'
4
+ $env:PLUGIN_ROOT = Split-Path -Parent (Split-Path -Parent $PSScriptRoot)
5
+
6
+ $input_data = [Console]::In.ReadToEnd()
7
+ $result = $input_data | & bash "$PSScriptRoot/../$($MyInvocation.MyCommand.Name -replace '\.ps1$','.sh')" 2>$null
8
+ if ($LASTEXITCODE -eq 0 -and $result) {
9
+ Write-Output $result
10
+ } else {
11
+ Write-Output '{}'
12
+ }
@@ -0,0 +1,3 @@
1
+ #!/bin/bash
2
+ set -euo pipefail
3
+ babysitter hook:run --harness unified --hook-type user-prompt-submit --json
@@ -16,6 +16,38 @@
16
16
  "powershell": "powershell -NoProfile -ExecutionPolicy Bypass -File \"./hooks/babysitter-proxied-stop.ps1\"",
17
17
  "loop_limit": null
18
18
  }
19
+ ],
20
+ "userPromptSubmit": [
21
+ {
22
+ "type": "command",
23
+ "bash": "bash \"./hooks/babysitter-proxied-user-prompt-submit.sh\"",
24
+ "powershell": "powershell -NoProfile -ExecutionPolicy Bypass -File \"./hooks/babysitter-proxied-user-prompt-submit.ps1\"",
25
+ "timeoutSec": 30
26
+ }
27
+ ],
28
+ "preToolUse": [
29
+ {
30
+ "type": "command",
31
+ "bash": "bash \"./hooks/babysitter-proxied-pre-tool-use.sh\"",
32
+ "powershell": "powershell -NoProfile -ExecutionPolicy Bypass -File \"./hooks/babysitter-proxied-pre-tool-use.ps1\"",
33
+ "timeoutSec": 30
34
+ }
35
+ ],
36
+ "postToolUse": [
37
+ {
38
+ "type": "command",
39
+ "bash": "bash \"./hooks/babysitter-proxied-post-tool-use.sh\"",
40
+ "powershell": "powershell -NoProfile -ExecutionPolicy Bypass -File \"./hooks/babysitter-proxied-post-tool-use.ps1\"",
41
+ "timeoutSec": 30
42
+ }
43
+ ],
44
+ "sessionEnd": [
45
+ {
46
+ "type": "command",
47
+ "bash": "bash \"./hooks/babysitter-proxied-session-end.sh\"",
48
+ "powershell": "powershell -NoProfile -ExecutionPolicy Bypass -File \"./hooks/babysitter-proxied-session-end.ps1\"",
49
+ "timeoutSec": 30
50
+ }
19
51
  ]
20
52
  }
21
53
  }
package/hooks.json CHANGED
@@ -16,6 +16,38 @@
16
16
  "powershell": "powershell -NoProfile -ExecutionPolicy Bypass -File \"./hooks/babysitter-proxied-stop.ps1\"",
17
17
  "loop_limit": null
18
18
  }
19
+ ],
20
+ "userPromptSubmit": [
21
+ {
22
+ "type": "command",
23
+ "bash": "bash \"./hooks/babysitter-proxied-user-prompt-submit.sh\"",
24
+ "powershell": "powershell -NoProfile -ExecutionPolicy Bypass -File \"./hooks/babysitter-proxied-user-prompt-submit.ps1\"",
25
+ "timeoutSec": 30
26
+ }
27
+ ],
28
+ "preToolUse": [
29
+ {
30
+ "type": "command",
31
+ "bash": "bash \"./hooks/babysitter-proxied-pre-tool-use.sh\"",
32
+ "powershell": "powershell -NoProfile -ExecutionPolicy Bypass -File \"./hooks/babysitter-proxied-pre-tool-use.ps1\"",
33
+ "timeoutSec": 30
34
+ }
35
+ ],
36
+ "postToolUse": [
37
+ {
38
+ "type": "command",
39
+ "bash": "bash \"./hooks/babysitter-proxied-post-tool-use.sh\"",
40
+ "powershell": "powershell -NoProfile -ExecutionPolicy Bypass -File \"./hooks/babysitter-proxied-post-tool-use.ps1\"",
41
+ "timeoutSec": 30
42
+ }
43
+ ],
44
+ "sessionEnd": [
45
+ {
46
+ "type": "command",
47
+ "bash": "bash \"./hooks/babysitter-proxied-session-end.sh\"",
48
+ "powershell": "powershell -NoProfile -ExecutionPolicy Bypass -File \"./hooks/babysitter-proxied-session-end.ps1\"",
49
+ "timeoutSec": 30
50
+ }
19
51
  ]
20
52
  }
21
53
  }
package/package.json CHANGED
@@ -1,15 +1,13 @@
1
1
  {
2
2
  "name": "@a5c-ai/babysitter-cursor",
3
- "version": "5.0.1-staging.ff2c19f9",
3
+ "version": "5.0.1-staging.ffad3b46492e",
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
  "deploy": "npm publish --access public",
7
7
  "deploy:staging": "npm publish --access public --tag staging",
8
8
  "postinstall": "node bin/install.js",
9
9
  "preuninstall": "node bin/uninstall.js",
10
- "team:install": "node scripts/team-install.js",
11
- "test": "node scripts/sync-command-surfaces.js --check",
12
- "sync:commands": "node scripts/sync-command-surfaces.js"
10
+ "team:install": "node scripts/team-install.js"
13
11
  },
14
12
  "bin": {
15
13
  "babysitter-cursor": "bin/cli.js"
@@ -37,11 +35,14 @@
37
35
  "access": "public"
38
36
  },
39
37
  "dependencies": {
40
- "@a5c-ai/babysitter-sdk": "5.0.1-staging.ff2c19f9"
38
+ "@a5c-ai/babysitter-sdk": "5.0.1-staging.ffad3b46492e"
41
39
  },
42
40
  "repository": {
43
41
  "type": "git",
44
- "url": "https://github.com/a5c-ai/babysitter"
42
+ "url": "git+https://github.com/a5c-ai/babysitter-cursor.git"
45
43
  },
46
- "homepage": "https://github.com/a5c-ai/babysitter/tree/main/plugins/babysitter-cursor#readme"
44
+ "homepage": "https://github.com/a5c-ai/babysitter-cursor#readme",
45
+ "bugs": {
46
+ "url": "https://github.com/a5c-ai/babysitter-cursor/issues"
47
+ }
47
48
  }
package/plugin.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "babysitter",
3
- "version": "5.0.1-staging.ff2c19f9",
3
+ "version": "5.0.1-staging.ffad3b46492e",
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": "a5c.ai",
6
6
  "license": "MIT",
@@ -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
package/versions.json CHANGED
@@ -1,3 +1,4 @@
1
1
  {
2
- "sdkVersion": "5.0.1-staging.ff2c19f9"
2
+ "sdkVersion": "5.0.1-staging.ffad3b46492e",
3
+ "extensionVersion": "5.0.1-staging.ffad3b46492e"
3
4
  }
@@ -1,62 +0,0 @@
1
- 'use strict';
2
-
3
- const path = require('path');
4
- const {
5
- listDirectories,
6
- listMarkdownBasenames,
7
- reportCheckResult,
8
- syncCommandMirrors,
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 ROOT_COMMANDS = path.join(REPO_ROOT, 'plugins', 'babysitter', 'commands');
15
- const PLUGIN_COMMANDS = path.join(PACKAGE_ROOT, 'commands');
16
- const PLUGIN_SKILLS = path.join(PACKAGE_ROOT, 'skills');
17
- const LABEL = 'babysitter-cursor sync';
18
-
19
- function getMirroredCommandNames() {
20
- const local = new Set(listMarkdownBasenames(PLUGIN_COMMANDS));
21
- return listMarkdownBasenames(ROOT_COMMANDS).filter((name) => local.has(name));
22
- }
23
-
24
- function getDerivedSkillNames() {
25
- const local = new Set(listDirectories(PLUGIN_SKILLS));
26
- return listMarkdownBasenames(PLUGIN_COMMANDS).filter((name) => local.has(name));
27
- }
28
-
29
- function main() {
30
- const check = process.argv.includes('--check');
31
- const mirrorResult = syncCommandMirrors({
32
- label: LABEL,
33
- sourceRoot: ROOT_COMMANDS,
34
- targetRoot: PLUGIN_COMMANDS,
35
- names: getMirroredCommandNames(),
36
- check,
37
- cwd: PACKAGE_ROOT,
38
- });
39
- const skillsResult = syncSkillsFromCommands({
40
- label: LABEL,
41
- sourceRoot: PLUGIN_COMMANDS,
42
- skillsRoot: PLUGIN_SKILLS,
43
- names: getDerivedSkillNames(),
44
- check,
45
- cwd: PACKAGE_ROOT,
46
- });
47
-
48
- if (check) {
49
- reportCheckResult(LABEL, [...mirrorResult.stale, ...skillsResult.stale]);
50
- return;
51
- }
52
-
53
- const updated = mirrorResult.updated + skillsResult.updated;
54
- if (updated === 0) {
55
- console.log(`[${LABEL}] no Cursor plugin command changes were needed.`);
56
- return;
57
- }
58
-
59
- console.log(`[${LABEL}] updated ${updated} Cursor plugin file(s).`);
60
- }
61
-
62
- main();