@a5c-ai/babysitter-codex 0.1.6-staging.060a3463 → 0.1.6-staging.2df34517

package/.codex-plugin/plugin.json

@@ -0,0 +1,44 @@
+{
+  "name": "babysitter-codex",
+  "version": "0.1.5",
+  "description": "Babysitter orchestration plugin for Codex with skill entrypoints and lifecycle hooks.",
+  "author": {
+    "name": "a5c.ai",
+    "email": "support@a5c.ai",
+    "url": "https://github.com/a5c-ai/babysitter"
+  },
+  "homepage": "https://github.com/a5c-ai/babysitter/tree/main/plugins/babysitter-codex#readme",
+  "repository": "https://github.com/a5c-ai/babysitter",
+  "license": "MIT",
+  "keywords": [
+    "babysitter",
+    "codex",
+    "orchestration",
+    "hooks",
+    "skills"
+  ],
+  "skills": "./skills/",
+  "hooks": "./hooks.json",
+  "interface": {
+    "displayName": "Babysitter",
+    "shortDescription": "Run Babysitter orchestration flows from Codex",
+    "longDescription": "Babysitter adds orchestration entrypoints such as $call, $plan, and $resume, plus Codex lifecycle hooks that keep runs and workspace state in sync.",
+    "developerName": "a5c.ai",
+    "category": "Coding",
+    "capabilities": [
+      "Interactive",
+      "Read",
+      "Write"
+    ],
+    "websiteURL": "https://github.com/a5c-ai/babysitter",
+    "privacyPolicyURL": "https://github.com/a5c-ai/babysitter",
+    "termsOfServiceURL": "https://github.com/a5c-ai/babysitter",
+    "defaultPrompt": [
+      "Use Babysitter to start a new orchestration run",
+      "Plan a Babysitter workflow before executing it",
+      "Resume the latest Babysitter run in this workspace"
+    ],
+    "brandColor": "#0F766E",
+    "screenshots": []
+  }
+}

package/README.md

@@ -2,44 +2,16 @@
 
 Babysitter integration package for OpenAI Codex CLI.
 
-This package is a Codex skill bundle plus installer assets. It is not a native
-Codex plugin manifest and it does not run an external orchestrator. The Codex
-plugin path is:
-
-- installed skill bundle under `~/.codex/skills/babysit`
-- optional user-local prompt aliases under `~/.codex/prompts/call.md`,
-  `plan.md`, `resume.md`, `yolo.md`, and the rest of the Babysitter modes
-- repo-local skill bundle under `.codex/skills/babysit`
-- repo-local prompt aliases under `.codex/prompts/*.md`
-- workspace `.codex/hooks.json`
-- workspace `.codex/config.toml`
-- workspace `.a5c/` state
-- Babysitter SDK CLI for run creation, iteration, result posting, and
-  process-library binding
-
-## What This Package Installs
-
-Global install copies the Codex-facing bundle into `CODEX_HOME`:
-
-- `SKILL.md`
-- `.codex/`
-- `agents/`
-- `prompts/` as the source for user-local prompt aliases
-- `scripts/`
-- `babysitter.lock.json`
-
-It does not bundle the process library.
+This package now ships as a real Codex plugin bundle:
 
-## Integration Model
-
-Babysitter for Codex uses only the hooks model:
+- `.codex-plugin/plugin.json`
+- `skills/`
+- `hooks.json`
+- `hooks/`
 
-- `SessionStart` seeds Babysitter session state
-- `UserPromptSubmit` handles prompt-time transformations
-- `Stop` yields continuation back into the Babysitter orchestration loop
-
-The process library is fetched at workspace-install time through the SDK CLI and
-bound for active use in `.a5c/active/process-library.json`.
+It still uses the Babysitter SDK CLI and the shared `~/.a5c` process-library
+state, but it no longer installs itself by copying fake skill and hook payloads
+into `~/.codex/skills` and `~/.codex/hooks.json`.
 
 ## Installation
 
@@ -49,108 +21,75 @@ Install the SDK CLI first:
 npm install -g @a5c-ai/babysitter-sdk
 ```
 
-Install the Codex package:
+Install the Codex plugin globally:
 
 ```bash
-npm install -g @a5c-ai/babysitter-codex
+npx @a5c-ai/babysitter-codex install
 ```
 
-This global install now also clones or updates the process library into
-`~/.a5c/process-library/babysitter-repo` and binds it as the default active
-process library in `~/.a5c/active/process-library.json` through the SDK CLI.
+This copies the plugin into `~/.codex/plugins/babysitter-codex`, registers it
+in `~/.agents/plugins/marketplace.json`, merges the required global Codex
+config into `~/.codex/config.toml`, and ensures the Babysitter process library
+is active in `~/.a5c`.
 
-Then install the Codex plugin payload into the target workspace:
+Install the plugin into a specific workspace:
 
 ```bash
-babysitter harness:install-plugin codex --workspace /path/to/repo
+npx @a5c-ai/babysitter-codex install --workspace /path/to/repo
 ```
 
-If `npm install -g @a5c-ai/babysitter-codex` is run from inside the target
-workspace, `postinstall` will also auto-run the packaged `team-install.js`
-against that workspace.
-
-## What `team-install.js` Does
-
-`scripts/team-install.js` is the workspace installer used by the package and by
-`babysitter harness:install-plugin codex`.
-
-It:
-
-1. Resolves the installed package root.
-2. Reads `babysitter.lock.json`.
-3. Installs the single repo-local Codex skill into `.codex/skills/babysit`.
-4. Installs the prompt aliases into `.codex/prompts`.
-5. Copies hook scripts into `.codex/hooks`.
-6. Clones or updates the upstream Babysitter repo into
-   `<workspace>/.a5c/process-library/babysitter-repo`.
-7. Binds `<workspace>/.a5c/process-library/babysitter-repo/library` with
-   `babysitter process-library:use`.
-8. Writes `<workspace>/.a5c/active/process-library.json`.
-9. Writes or refreshes `<workspace>/.codex/hooks.json`.
-10. Creates or merges `<workspace>/.codex/config.toml` so the workspace has the
-   required Codex settings.
-11. Writes `<workspace>/.a5c/team/install.json`.
-12. Creates `<workspace>/.a5c/team/profile.json` if it does not already exist.
-
-It does not create an external orchestrator, bundle the process library, or
-turn the workspace into a fake Codex plugin manifest.
-
-## Resulting Workspace Files
-
-After a successful workspace install, the important files are:
-
-- `.codex/skills/babysit/SKILL.md`
-- `.codex/prompts/call.md`
-- `.codex/prompts/plan.md`
-- `.codex/prompts/resume.md`
-- `.codex/hooks/`
-- `.codex/hooks.json`
-- `.codex/config.toml`
-- `.a5c/team/install.json`
-- `.a5c/team/profile.json`
-- `.a5c/active/process-library.json`
-- `.a5c/process-library/babysitter-repo/library`
+This copies the plugin into `<workspace>/plugins/babysitter-codex`, registers
+it in `<workspace>/.agents/plugins/marketplace.json`, merges
+`<workspace>/.codex/config.toml`, and records install metadata under
+`<workspace>/.a5c/team/`.
+
+## Integration Model
 
-## Using It In Codex
+The plugin provides:
 
-Use the skill directly:
+- `skills/babysit/SKILL.md` as the core entrypoint
+- mode wrapper skills such as `$call`, `$plan`, and `$resume`
+- plugin-level lifecycle hooks for `SessionStart`, `UserPromptSubmit`, and
+  `Stop`
 
-```text
-$babysit implement authentication with tests
-```
+The process library is fetched and bound through the SDK CLI in
+`~/.a5c/active/process-library.json`.
 
-The optional prompt aliases are the mode shortcuts:
+## Workspace Output
 
-```text
-/call implement authentication with tests
-/plan migration from monolith to services
-/resume latest
-```
+After `install --workspace`, the important files are:
 
-Each prompt alias should only forward into the `babysit` skill for the
-matching mode. Low-level SDK commands remain runtime mechanics, not the
-user-facing interface.
+- `plugins/babysitter-codex/.codex-plugin/plugin.json`
+- `plugins/babysitter-codex/skills/babysit/SKILL.md`
+- `plugins/babysitter-codex/hooks.json`
+- `.agents/plugins/marketplace.json`
+- `.codex/config.toml`
+- `.a5c/team/install.json`
+- `.a5c/team/profile.json`
 
 ## Verification
 
-Verify the installed skill bundle:
+Verify the installed plugin bundle:
 
 ```bash
 npm ls -g @a5c-ai/babysitter-codex --depth=0
-ls -1 ~/.codex/skills/babysit
-test -f ~/.codex/skills/babysit/scripts/team-install.js
-test -f ~/.codex/skills/babysit/.codex/hooks/babysitter-stop-hook.sh
-test -f ~/.codex/prompts/call.md
-test -f ~/.codex/prompts/plan.md
-test -f ~/.codex/prompts/resume.md
+test -f ~/.codex/plugins/babysitter-codex/.codex-plugin/plugin.json
+test -f ~/.codex/plugins/babysitter-codex/hooks.json
+test -f ~/.codex/plugins/babysitter-codex/hooks/babysitter-stop-hook.sh
+test -f ~/.codex/plugins/babysitter-codex/skills/babysit/SKILL.md
+test -f ~/.agents/plugins/marketplace.json
 ```
 
-Verify the active process-library binding for a workspace:
+Verify the active shared process-library binding:
 
 ```bash
-babysitter process-library:active --state-dir /path/to/repo/.a5c --json
+babysitter process-library:active --json
 ```
 
+On native Windows, Codex currently does not execute hooks. The plugin still
+installs correctly, but the lifecycle hooks will not fire until Codex enables
+Windows hook execution.
+
 ## License
 
 MIT

package/bin/cli.js

@@ -0,0 +1,104 @@
+#!/usr/bin/env node
+'use strict';
+
+const path = require('path');
+const { spawnSync } = require('child_process');
+
+const PACKAGE_ROOT = path.resolve(__dirname, '..');
+
+function printUsage() {
+  console.error([
+    'Usage:',
+    '  babysitter-codex install [--global]',
+    '  babysitter-codex install --workspace [path]',
+    '  babysitter-codex uninstall',
+  ].join('\n'));
+}
+
+function parseInstallArgs(argv) {
+  let scope = 'global';
+  let workspace = null;
+  const passthrough = [];
+
+  for (let i = 0; i < argv.length; i += 1) {
+    const arg = argv[i];
+    if (arg === '--global') {
+      if (scope === 'workspace') {
+        throw new Error('install accepts either --global or --workspace, not both');
+      }
+      scope = 'global';
+      continue;
+    }
+    if (arg === '--workspace') {
+      if (scope === 'global' && workspace !== null) {
+        throw new Error('install accepts either --global or --workspace, not both');
+      }
+      scope = 'workspace';
+      const next = argv[i + 1];
+      if (next && !next.startsWith('-')) {
+        workspace = path.resolve(next);
+        i += 1;
+      } else {
+        workspace = process.cwd();
+      }
+      continue;
+    }
+    passthrough.push(arg);
+  }
+
+  return {
+    scope,
+    workspace,
+    passthrough,
+  };
+}
+
+function runNodeScript(scriptPath, args, extraEnv = {}) {
+  const result = spawnSync(process.execPath, [scriptPath, ...args], {
+    cwd: process.cwd(),
+    stdio: 'inherit',
+    env: {
+      ...process.env,
+      ...extraEnv,
+    },
+  });
+  process.exitCode = result.status ?? 1;
+}
+
+function main() {
+  const [command, ...rest] = process.argv.slice(2);
+  if (!command || command === '--help' || command === '-h' || command === 'help') {
+    printUsage();
+    process.exitCode = command ? 0 : 1;
+    return;
+  }
+
+  if (command === 'install') {
+    const parsed = parseInstallArgs(rest);
+    if (parsed.scope === 'workspace') {
+      const args = [];
+      if (parsed.workspace) {
+        args.push('--workspace', parsed.workspace);
+      }
+      args.push(...parsed.passthrough);
+      runNodeScript(
+        path.join(PACKAGE_ROOT, 'scripts', 'team-install.js'),
+        args,
+        { BABYSITTER_PACKAGE_ROOT: PACKAGE_ROOT },
+      );
+      return;
+    }
+    runNodeScript(path.join(PACKAGE_ROOT, 'bin', 'install.js'), parsed.passthrough);
+    return;
+  }
+
+  if (command === 'uninstall') {
+    runNodeScript(path.join(PACKAGE_ROOT, 'bin', 'uninstall.js'), rest);
+    return;
+  }
+
+  printUsage();
+  process.exitCode = 1;
+}
+
+main();