@a5c-ai/babysitter-codex 0.1.6-staging.f48a64a2 → 0.1.6

package/.app.json

@@ -0,0 +1,3 @@
+{
+  "apps": {}
+}

package/.codex-plugin/plugin.json

@@ -0,0 +1,47 @@
+{
+  "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",
+  "apps": "./.app.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",
+    "composerIcon": "./assets/icon.svg",
+    "logo": "./assets/logo.svg",
+    "screenshots": []
+  }
+}

package/README.md

@@ -2,47 +2,17 @@
 
 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 core skill under `~/.codex/skills/babysit`
-- installed mode-wrapper skills under `~/.codex/skills/<mode>`
-- global `~/.codex/hooks.json`
-- global `~/.codex/hooks/`
-- global `~/.codex/config.toml`
-- optional workspace `.codex/hooks.json`
-- optional workspace `.codex/hooks/`
-- optional workspace `.codex/config.toml`
-- workspace `.a5c/` state
-- shared global Babysitter state under `~/.a5c`
-- Babysitter SDK CLI for run creation, iteration, result posting, and
-  process-library binding
-
-## What This Package Installs
-
-Global install copies the Codex-facing runtime bundle into `CODEX_HOME`:
-
-- `SKILL.md`
-- `.codex/`
-- `scripts/`
-- `babysitter.lock.json`
-- `hooks/`
-- `hooks.json`
-- `config.toml`
-
-It does not bundle the process library.
-
-## Integration Model
-
-Babysitter for Codex uses only the hooks model:
+This package ships a real Codex plugin bundle:
 
-- `SessionStart` seeds Babysitter session state
-- `UserPromptSubmit` handles prompt-time transformations
-- `Stop` yields continuation back into the Babysitter orchestration loop
+- `.codex-plugin/plugin.json`
+- `skills/`
+- `hooks.json`
+- `hooks/`
 
-The process library is fetched at global 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. The installer registers the plugin bundle and also materializes the
+active Codex `skills/`, `hooks/`, and `hooks.json` surface at the selected
+scope so Codex can execute the Babysitter commands and hook scripts directly.
 
 ## Installation
 
@@ -52,100 +22,59 @@ Install the SDK CLI first:
 npm install -g @a5c-ai/babysitter-sdk
 ```
 
-Run the Codex package installer:
+clone the repo and install the plugin globally:
 
 ```bash
-npx @a5c-ai/babysitter-codex install
-```
-
-Global install is the default when no scope flag is provided.
-
-This explicit 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.
-It also installs the global Codex hooks/config surface under `~/.codex`.
-
-Then install the Codex plugin payload into the target workspace:
+git clone https://github.com/a5c-ai/babysitter.git
+cd babysitter
+codex
 
-```bash
-npx @a5c-ai/babysitter-codex install --workspace /path/to/repo
+> /plugins
 ```
 
-Fetching the npm package does not mutate the current repo or workspace. Workspace
-onboarding is a separate explicit step.
-
-## What `team-install.js` Does
+then navigate to the 'babysitter' entry and select 'Install'.
 
-`scripts/team-install.js` is the explicit workspace installer used by
-`babysitter harness:install-plugin codex --workspace ...`.
+## Integration Model
 
-It:
+The plugin provides:
 
-1. Resolves the installed package root.
-2. Reads `babysitter.lock.json`.
-3. Installs the workspace-local Codex skill into `.codex/skills/babysit`.
-4. Installs the workspace-local mode-wrapper skills into `.codex/skills/<mode>`.
-5. Copies hook scripts into `.codex/hooks`.
-6. Resolves the active shared process library with
-   `babysitter process-library:active --json`.
-7. Writes or refreshes `<workspace>/.codex/hooks.json`.
-8. Creates or merges `<workspace>/.codex/config.toml` so the workspace has the
-   required Codex settings.
-9. Writes `<workspace>/.a5c/team/install.json`.
-10. Creates `<workspace>/.a5c/team/profile.json` if it does not already exist.
+- `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`
 
-It does not create an external orchestrator, bundle the process library, or
-turn the workspace into a fake Codex plugin manifest.
+The process library is fetched and bound through the SDK CLI in
+`~/.a5c/active/process-library.json`.
 
-## Resulting Workspace Files
+## Workspace Output
 
-After a successful workspace install, the important files are:
+After `install --workspace`, the important files are:
 
-- `.codex/skills/babysit/SKILL.md`
-- `.codex/skills/call/SKILL.md`
-- `.codex/skills/plan/SKILL.md`
-- `.codex/skills/resume/SKILL.md`
+- `plugins/babysitter-codex/.codex-plugin/plugin.json`
+- `plugins/babysitter-codex/skills/babysit/SKILL.md`
+- `plugins/babysitter-codex/hooks.json`
+- `.codex/skills/`
 - `.codex/hooks/`
 - `.codex/hooks.json`
+- `.agents/plugins/marketplace.json`
 - `.codex/config.toml`
 - `.a5c/team/install.json`
 - `.a5c/team/profile.json`
 
-## Using It In Codex
-
-Use the skill directly:
-
-```text
-$babysit implement authentication with tests
-```
-
-The mode-wrapper skills are thin entrypoints that only load `babysit` in the
-matching mode:
-
-```text
-$call implement authentication with tests
-$plan migration from monolith to services
-$resume latest
-```
-
-Each mode-wrapper skill should only forward into the `babysit` skill for the
-matching mode. Low-level SDK commands remain runtime mechanics, not the
-user-facing interface.
-
 ## 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/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 ~/.codex/hooks.json
 test -f ~/.codex/hooks/babysitter-stop-hook.sh
-test -f ~/.codex/skills/babysit/scripts/team-install.js
-test -f ~/.codex/skills/babysit/.codex/hooks/babysitter-stop-hook.sh
-test -f ~/.codex/skills/call/SKILL.md
-test -f ~/.codex/skills/plan/SKILL.md
-test -f ~/.codex/skills/resume/SKILL.md
+test -f ~/.codex/skills/babysit/SKILL.md
+test -f ~/.agents/plugins/marketplace.json
 ```
 
 Verify the active shared process-library binding:
@@ -154,6 +83,10 @@ Verify the active shared process-library binding:
 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/assets/icon.svg

@@ -0,0 +1,7 @@
+<svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 64 64" role="img" aria-label="Babysitter icon">
+  <rect width="64" height="64" rx="14" fill="#0F766E"/>
+  <path d="M16 22h32v20H16z" fill="#ECFEFF"/>
+  <circle cx="24" cy="32" r="3" fill="#0F766E"/>
+  <circle cx="32" cy="32" r="3" fill="#0F766E"/>
+  <circle cx="40" cy="32" r="3" fill="#0F766E"/>
+</svg>

package/assets/logo.svg

@@ -0,0 +1,8 @@
+<svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 320 80" role="img" aria-label="Babysitter logo">
+  <rect x="0" y="8" width="64" height="64" rx="14" fill="#0F766E"/>
+  <path d="M16 26h32v28H16z" fill="#ECFEFF"/>
+  <circle cx="24" cy="40" r="3" fill="#0F766E"/>
+  <circle cx="32" cy="40" r="3" fill="#0F766E"/>
+  <circle cx="40" cy="40" r="3" fill="#0F766E"/>
+  <text x="80" y="50" font-family="Arial, sans-serif" font-size="34" fill="#0F766E">Babysitter</text>
+</svg>