byob-cli 0.2.12 → 0.2.13

package/.codex-plugin/plugin.json

@@ -1,6 +1,6 @@
 {
   "name": "byob-cli",
-  "version": "0.2.12",
+  "version": "0.2.13",
   "description": "Codex connector for BYOB projects, backed by Agent MCP with project context, deployment helpers, and coding tools.",
   "skills": "./skills/byob_cli/",
   "mcpServers": "./.mcp.json"

package/README.md

@@ -30,7 +30,7 @@ Refresh synced coding skills later without rerunning OAuth or changing MCP confi
 npx -y byob-cli codex sync-skills --project-id <project_id> --token <agent_access_token>
 ```
 
-For Local Codex billed project editing, the BYOB Agent MCP returns a workspace handle that the Codex host opens as the active Codex workspace. The host uses `codex ssh-proxy` behind that handle:
+For Local Codex billed project editing, the BYOB Agent MCP returns a workspace handle that the Codex host opens as the active Codex workspace. The native handoff uses Codex's `CODEX_EXEC_SERVER_URL` remote execution support; `codex ssh-proxy` remains the fallback transport:
 
 ```bash
 npx -y byob-cli@latest codex ssh-proxy '{"ssh_endpoint":"wss://..."}'
@@ -207,7 +207,7 @@ When a user chooses **Local Codex billed**, open the BYOB project as the active
 
 1. Call `byob_codex_status` for the selected project.
 2. If `Local Codex billed` is available, call `byob_codex_connection_create` with `mode: "local_codex_billed"`.
-3. Hand the returned `workspace_handle` to the Codex host so `/home/workspace/app_data` becomes the active workspace.
+3. Hand the returned `workspace_handle` to the Codex host so `/home/workspace/app_data` becomes the active workspace with `CODEX_EXEC_SERVER_URL` set from MCP `_meta`.
 4. Keep tokens, private keys, and complete proxy commands out of chat.
 5. Use Codex's normal file, shell, and git workflow inside that active workspace.
 

package/bin/byob.js

@@ -41,7 +41,7 @@ Usage:
   byob config
   byob codex install
   byob codex sync-skills
-  byob codex ssh-proxy [json_args]
+  byob codex ssh-proxy [json_args]   # fallback transport only
 
 Options:
   --air-url <url>       Default: BYOB_AIR_URL or https://air.api.byob.studio
@@ -71,11 +71,12 @@ Usage:
 Commands:
   install       Authorize BYOB, configure Codex MCP, and install BYOB skills.
   sync-skills  Refresh BYOB AIR coding skills for an approved project.
-  ssh-proxy    Bridge OpenSSH stdio to a BYOB Local Codex billed workspace.
+  ssh-proxy    Fallback OpenSSH stdio bridge for Local Codex billed workspaces.
 
 Local Codex billed workspaces are normally opened by the Codex host from the
-workspace handle returned by BYOB Agent MCP. Agents should not print or manually
-handle raw SSH tokens, private keys, or complete proxy commands.
+workspace handle returned by BYOB Agent MCP. The native handoff uses Codex's
+exec-server transport; agents should not print or manually handle raw transport
+tokens, private keys, or complete fallback proxy commands.
 `;
 }
 
@@ -257,6 +258,13 @@ function sanitizePreviewUrls(
         ...item,
         byob_local_codex_workspace: {
           ...item.byob_local_codex_workspace,
+          codex_native: {
+            ...item.byob_local_codex_workspace.codex_native,
+            env: {
+              redacted: true,
+              reason: "Use the workspace_handle with a Codex host; direct CLI display omits CODEX_EXEC_SERVER_URL credentials.",
+            },
+          },
           ssh: {
             redacted: true,
             reason: "Use the workspace_handle with a Codex host; direct CLI display omits raw SSH material.",

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "byob-cli",
-  "version": "0.2.12",
+  "version": "0.2.13",
   "description": "Codex connector for BYOB projects, backed by an Agent MCP stdio bridge.",
   "license": "MIT",
   "type": "module",

package/skills/byob_cli/CODEX_CORE.md

@@ -73,7 +73,7 @@ When the user selects **Local Codex billed**, open the BYOB project as the activ
 2. Ensure the project is started and remote editing is available.
 3. Call `byob_codex_status`.
 4. Create a Local Codex billed connection with `byob_codex_connection_create` using `mode: "local_codex_billed"`.
-5. Hand the returned Local Codex billed `workspace_handle` to the Codex host; the host uses `byob-cli@latest`'s `codex ssh-proxy` behind that handle.
+5. Hand the returned Local Codex billed `workspace_handle` to the Codex host; the host uses Codex's `CODEX_EXEC_SERVER_URL` remote execution support behind that handle, with `byob-cli@latest`'s `codex ssh-proxy` only as fallback.
 
 Local Codex billed should let Codex inspect and edit the remote project filesystem directly, including protected files such as `src/app.html` when the task requires reading them. Keep all tokens, private keys, and complete proxy commands out of chat and logs. Use user-facing language like "Local Codex billed"; avoid internal enum names unless debugging BYOB itself.
 

package/skills/byob_cli/SKILL.md

@@ -58,7 +58,7 @@ For **Local Codex billed** project editing, open the BYOB project as the active
 1. Establish project context with `byob_current_project_context`.
 2. Call `byob_codex_status` and confirm the Local Codex billed option is available.
 3. Call `byob_codex_connection_create` with `mode: "local_codex_billed"`.
-4. Hand the returned Local Codex billed `workspace_handle` to the Codex host so Codex edits the remote project container as its active workspace.
+4. Hand the returned Local Codex billed `workspace_handle` to the Codex host so Codex edits the remote project container as its active workspace through `CODEX_EXEC_SERVER_URL`.
 5. Do not print tokens, private keys, or full proxy commands in chat.
 
 After the workspace is open, use Codex's normal file, shell, git, and verification workflow inside the remote project.
@@ -291,7 +291,7 @@ Use this flow:
 1. Confirm the project is started and `connectivity.can_remote_edit` is true.
 2. Call `byob_codex_status`.
 3. If Local Codex billed is available, call `byob_codex_connection_create` with `mode: "local_codex_billed"`.
-4. Hand the returned Local Codex billed `workspace_handle` to the Codex host; the host uses `byob-cli@latest`'s `codex ssh-proxy` behind that handle.
+4. Hand the returned Local Codex billed `workspace_handle` to the Codex host; the host uses Codex's `CODEX_EXEC_SERVER_URL` remote execution support behind that handle, with `byob-cli@latest`'s `codex ssh-proxy` only as fallback.
 5. Keep credentials out of chat, logs, screenshots, and command transcripts.
 
 After the workspace is open, use Codex's normal file, shell, git, and verification workflow inside the remote project.