Connect Codex Desktop and WorkBuddy

Before you start

1. Install the Beav desktop app or the CLI on the same computer.
2. Confirm beav version runs; with a test archive you can use the full path to its bin/beav instead.
3. Open Codex Desktop and send the prompt below in any task.

/goal Read https://www.getbeav.com/agent to install the Beav Creator plugin and set up a new task for me.

What Codex does

1. Reads the machine install guide served at /agent.
2. Locates the CLI bundled inside Codex Desktop itself, without depending on your terminal PATH.
3. Runs beav extension prepare codex --output json to get marketplacePath and pluginId.
4. Adds the beav-local marketplace through the Codex CLI and installs beav-creator@beav-local.
5. Reads the plugin list again to confirm the plugin is installed and enabled.
6. Creates a new task so the freshly loaded Beav Creator MCP takes effect in that session.

beav extension install codex --output json is a compatibility alias that also only prepares the plugin: it never calls a bare codex command or edits your Codex configuration.

How the new task collaborates

The new task calls creator_status and workspace_list first, then delegates the Task Brief to Beav's internal Agent with typed MCP tools. When you need to review, approve, or fine-tune something, Beav returns a localhost browser handoff; the browser is your workspace, not the Agent control plane.

Follow-up changes keep querying and continuing the same Beav task. Codex may only report a task complete once it reaches the protocol's terminal state and the required artifacts can be read back.

The machine-readable install contract lives at https://www.getbeav.com/agent.md.

Connecting WorkBuddy

Send this prompt to WorkBuddy:

Read https://www.getbeav.com/workbuddy to install the Beav Creator plugin and connect it to my local Beav workspace.

WorkBuddy then:

1. Reads the machine install guide served at /workbuddy.
2. Locates the CodeBuddy CLI bundled inside the WorkBuddy app, with no requirement for codebuddy on the shell PATH.
3. Runs beav extension prepare workbuddy --output json to generate a .codebuddy-plugin marketplace.
4. Validates the marketplace with codebuddy plugin validate, then installs beav-creator@beav-local at user scope.
5. Hot-reloads the plugin through /reload-plugins and verifies the same Beav MCP with creator_status and workspace_list.

beav extension install workbuddy --output json is a prepare-only compatibility alias. Codex and WorkBuddy differ only in host install format and load mechanism; both share the same Beav Creator Skill, Creator Gateway, internal Agent, and localhost user workspace.

The machine-readable install contract lives at https://www.getbeav.com/workbuddy.md.