feat: sync/upstream main

.github/workflows/ci.yml

@@ -15,7 +15,7 @@ jobs:
       contents: read
     steps:
       - uses: actions/checkout@v7
-      - uses: actions/setup-node@v6
+      - uses: actions/setup-node@v7
         with:
           node-version: "24"
       - uses: oven-sh/setup-bun@0c5077e51419868618aeaa5fe8019c62421857d6

.github/workflows/publish.yml

@@ -15,7 +15,7 @@ jobs:
       contents: read
     steps:
       - uses: actions/checkout@v7
-      - uses: actions/setup-node@v6
+      - uses: actions/setup-node@v7
         with:
           node-version: '24'
       - name: Configure sandboxing
@@ -41,7 +41,7 @@ jobs:
       id-token: write
     steps:
       - uses: actions/checkout@v7
-      - uses: actions/setup-node@v6
+      - uses: actions/setup-node@v7
         with:
           node-version: '24'
           registry-url: 'https://registry.npmjs.org'
@@ -51,6 +51,7 @@ jobs:
   create-release:
     needs: publish-to-npm
     runs-on: ubuntu-latest
+    environment: release
     permissions: {}
     steps:
       - name: Generate GitHub token
@@ -61,7 +62,32 @@ jobs:
           private-key: ${{ secrets.RELEASE_PLZ_APP_PRIVATE_KEY }}
 
       - name: Create Release
-        uses: softprops/action-gh-release@718ea10b132b3b2eba29c1007bb80653f286566b # v3.0.1
+        uses: softprops/action-gh-release@3d0d9888cb7fd7b750713d6e236d1fcb99157228 # v3.0.2
         with:
           token: ${{ steps.generate-token.outputs.token }}
           generate_release_notes: true
+
+  trigger-registry-update:
+    needs: create-release
+    runs-on: ubuntu-latest
+    environment: release
+    permissions: {}
+    steps:
+      - name: Generate token scoped to the registry repo
+        uses: actions/create-github-app-token@v3
+        id: registry-token
+        with:
+          app-id: ${{ secrets.REGISTRY_UPDATER_APP_ID }}
+          private-key: ${{ secrets.REGISTRY_UPDATER_APP_PRIVATE_KEY }}
+          owner: ${{ github.repository_owner }}
+          repositories: registry
+
+      - name: Dispatch registry version update
+        env:
+          GH_TOKEN: ${{ steps.registry-token.outputs.token }}
+        run: |
+          gh workflow run update-versions.yml \
+            --repo ${{ github.repository_owner }}/registry \
+            --ref main \
+            -f apply=true \
+            -f agents=codex-acp

README.md

@@ -12,6 +12,7 @@ Use [OpenAI Codex](https://github.com/openai/codex) from [Agent Client Protocol]
 - Model, reasoning effort, fast mode, approval, and sandbox mode configuration.
 - Text prompts, embedded context, images, resource links, and additional workspace directories.
 - Shell command, file change, permission request, MCP tool call, terminal output, reasoning, plan, web search, image generation, image view, token usage, and review events.
+- Subagent launches as standard ACP tool calls, with Codex thread identity and activity details in namespaced `_meta.codex.subagent` metadata.
 - Client-provided MCP servers over command-based stdio config and HTTP transport.
 - Native ACP session forking through Codex App Server `thread/fork`.
 - Acknowledged steering of an active Codex turn through app-server `turn/steer`.
@@ -49,11 +50,12 @@ The adapter advertises ACP auth methods during initialization. Clients can authe
 ## Steering extension
 
 The initialize response advertises `_meta.codex.steer` with the applied notification
-method and active-turn configuration policy. To steer a running prompt, send another
-`session/prompt` with a unique `_meta.codex.steer.id`. The adapter calls Codex
-`turn/steer` and emits `_codex/steerApplied { sessionId, steerId }` only after Codex
-commits the correlated user-message item. The steer keeps the active turn's model,
-mode, and configuration; slash commands cannot be steered.
+method and active-turn configuration policy. To steer a running prompt, call the
+advertised `_session/steering` method with `{ sessionId, prompt }`. Clients that need a
+committed-application boundary can also include a unique `steerId`. The adapter calls
+Codex `turn/steer` and emits `_codex/steerApplied { sessionId, steerId }` only after
+Codex commits that correlated user-message item. The steer keeps the active turn's
+model, mode, and configuration; slash commands cannot be steered.
 
 ## Runtime options