@a5c-ai/babysitter-codex 0.1.6-staging.2dca8387 → 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

@@ -1,145 +1,94 @@
 # @a5c-ai/babysitter-codex
 
-Babysitter integration package for OpenAI Codex CLI. It packages Codex-facing
-skills, install helpers, mapping docs, and the hook assets used to keep
-Babysitter in the Codex lifecycle loop.
+Babysitter integration package for OpenAI Codex CLI.
 
-This is a Codex skill bundle plus workspace hook templates. It is not a
-Claude-style manifest plugin, but it does rely on Codex's real lifecycle hook
-engine through `.codex/hooks.json`, and the package postinstall now wires the
-active workspace when the global install is launched from that workspace.
+This package now ships as a real Codex plugin bundle:
 
-## What This Package Owns
+- `.codex-plugin/plugin.json`
+- `skills/`
+- `hooks.json`
+- `hooks/`
 
-- Codex skill payload under `~/.codex/skills/babysitter-codex`
-- Codex-facing command docs
-- Codex runtime hook helpers under `.codex/`
-- Codex mapping and compatibility policy for SDK-driven orchestration
-
-## Active Process-Library Model
-
-`babysitter-codex` does not ship the process library. Workspace onboarding
-fetches the original Babysitter repo through the SDK CLI and binds the active
-process root in `.a5c/active/process-library.json`.
-
-Active-use process discovery should prefer:
-
-1. Project-local `.a5c/processes`
-2. The SDK-managed active process-library binding returned by
-   `babysitter process-library:active --state-dir .a5c --json`
-
-`project-install` and `team-install` layer config, rules, profiles, and pinned
-content metadata. They should not be documented as creating an exclusive
-project/team process-library scope.
-
-## Codex User Experience
-
-Codex should be integrated through its real hook engine:
-
-- `SessionStart` initializes Babysitter session state
-- `UserPromptSubmit` handles prompt-time transformations safely
-- `Stop` keeps Babysitter in the orchestration loop after each yielded turn
-
-Current contract:
-
-- start, resume, and inspect work through Codex command phrases such as
-  `babysitter call`, `babysitter resume`, and `babysitter doctor`
-- let the installed Codex hook assets handle runtime state, result posting,
-  and continuation
-- stop after each completed phase so the `Stop` hook can decide whether Codex
-  exits or receives the next Babysitter iteration message
-- finish only when `completionProof` is emitted and echoed as
-  `<promise>...</promise>`
-
-Do not document external supervisors, hidden wrapper loops, or `notify` as the
-continuation mechanism for the plugin path.
+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
 
-Install from npm:
+Install the SDK CLI first:
 
 ```bash
-npm install -g @a5c-ai/babysitter-codex
+npm install -g @a5c-ai/babysitter-sdk
 ```
 
-If you run that command from inside the target repository, postinstall will:
-
-- install the skill payload into `CODEX_HOME`
-- merge `~/.codex/config.toml` so `codex_hooks` is enabled
-- materialize workspace `.codex/hooks.json` and `.codex/config.toml` for the
-  active workspace
-- clone or update the original Babysitter repo into `.a5c/process-library/...`
-- bind `.a5c/process-library/.../library` for active use through the SDK CLI
-
-If you installed from somewhere else, run:
+Install the Codex plugin globally:
 
 ```bash
-npm install -g @a5c-ai/babysitter-sdk
-babysitter harness:install-plugin codex --workspace /path/to/repo
+npx @a5c-ai/babysitter-codex install
 ```
 
-`babysitter harness:install-plugin ...` is provided by the SDK CLI, so make
-sure `@a5c-ai/babysitter-sdk` is installed first.
+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`.
 
-Or from a local checkout:
+Install the plugin into a specific workspace:
 
 ```bash
-cd /path/to/babysitter-codex
-npm install -g .
+npx @a5c-ai/babysitter-codex install --workspace /path/to/repo
 ```
 
-Verify the installed skill payload:
+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/`.
 
-```bash
-npm ls -g @a5c-ai/babysitter-codex --depth=0
-ls -1 ~/.codex/skills/babysitter-codex
-test -f ~/.codex/skills/babysitter-codex/scripts/team-install.js
-test -f ~/.codex/skills/babysitter-codex/.codex/hooks.json
-test -f ~/.codex/skills/babysitter-codex/.codex/hooks/babysitter-stop-hook.sh
-```
+## Integration Model
 
-Verify the active process-library binding:
+The plugin provides:
 
-```bash
-babysitter process-library:active --state-dir /path/to/repo/.a5c --json
-```
+- `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`
 
-Manual bootstrap uses the same SDK CLI flow:
+The process library is fetched and bound through the SDK CLI in
+`~/.a5c/active/process-library.json`.
 
-```bash
-babysitter process-library:clone --repo https://github.com/a5c-ai/babysitter.git --dir .a5c/process-library/babysitter-repo
-babysitter process-library:use --dir .a5c/process-library/babysitter-repo/library --state-dir .a5c
-babysitter process-library:active --state-dir .a5c --json
-```
+## Workspace Output
 
-## Quick Start
+After `install --workspace`, the important files are:
 
-Use command phrases in Codex chat:
+- `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`
 
-```text
-babysitter help
-babysitter call implement authentication with tests
-babysitter yolo fix lint and failing tests
-babysitter resume latest incomplete run
-babysitter doctor current run
-```
+## Verification
 
-For Codex users, the expected interface is the Codex command phrases plus the
-workspace hook install created by onboarding. Raw Babysitter CLI primitives are
-internal harness details and live in the Codex skill, not in this user-facing
-README.
+Verify the installed plugin bundle:
 
-## Project And Team Install
+```bash
+npm ls -g @a5c-ai/babysitter-codex --depth=0
+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
+```
 
-Use `babysitter team-install` and `babysitter project-install` from Codex chat
-when you want workspace onboarding. They layer pinned config and setup around
-the active process roots already used at runtime; they are not the source of
-truth for process discovery.
+Verify the active shared process-library binding:
 
-## Documentation
+```bash
+babysitter process-library:active --json
+```
 
-- [commands/README.md](./commands/README.md)
-- Internal orchestration details: [.codex/skills/babysitter/call/SKILL.md](./.codex/skills/babysitter/call/SKILL.md)
+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
 

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();