Connect Codex Desktop and WorkBuddy

Before you start

1. Install the Beav desktop app on the same computer.
2. The desktop installer does not add beav to your PATH, so verify beav version using the desktop app executable's full path; a standard macOS install uses /Applications/Beav.app/Contents/MacOS/beav.
3. Open Codex Desktop and send the prompt below in any task.

/goal Read https://beav.pro/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 without depending on your terminal PATH. In the current macOS ChatGPT app, it lives at Contents/Resources/codex-cli/CodexCLI.app/Contents/MacOS/codex; verify the actual bundle with plugin --help.
3. Checks for Beav first. If it is missing, Codex asks you to install the desktop app, then continues in the same task without attempting plugin installation yet.
4. Runs beav extension prepare codex --output json. If Codex's command sandbox blocks local runtime or file access, it asks you to run beav open --output json and then the preparation command in a normal Terminal outside Codex. Send back only the returned marketplacePath, never the full JSON or credentials.
5. Checks the local marketplace and plugin manifests, adds or updates beav-local with Codex CLI, then runs plugin add beav-creator@beav-local --json to refresh an existing cache as well as install a new plugin.
6. Reads plugin list --json --marketplace beav-local and the installed cache to confirm the plugin is enabled and its version, MCP command, and skill match the prepared package.
7. Creates a new task to verify the connection, identify the active workspace, read its account operating plan, style and collaboration documents, and open the knowledge library in Codex's right-hand browser panel. The installation reply includes the actual workspace, profile-read and browser results, plus the new chat link. Until the new task verifies the connection, it reports installation complete but connection verification pending.

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

Checked 2026-10-08. This handoff uses existing Beav 2.8.14 interfaces and requires the updated website guide, or the updated Skill shipped in a new Beav build and refreshed plugin. The revised full installation and panel display still need desktop acceptance.

The new task calls creator_status, creator_capabilities, and workspace_list to identify the active workspace. It lists knowledge read-only and uses Read for profiles://creator_profile, profiles://soul, and profiles://agent: the actual contents of CreatorProfile.md, Soul.md, and Agent.md. Existing positioning, audience, goals, style and collaboration preferences become reference context for continued creation. Installation verification does not rewrite profiles or generate content.

The reply names the current workspace and any account explicitly identified by its profile, reports which documents were read or unavailable, and gives the local knowledge library opening result. The new chat opens the URL returned by MCP in Codex's right-hand browser panel with the knowledge tab selected, so you can continue creating there. If the host has no panel tool, library_open opens the system browser and the Agent explains that fallback. A failed or queued panel operation is reported accurately with a link.

If no workspace is active, open one in Beav first. Empty, missing or unreadable profiles are reported without claiming complete creation context. A workspace is not a social account: accounts://current archives require a separate actual session-account binding. The Agent must not guess the account from the space name. Relevant documents should be read again after changing spaces or losing context; profile reference material does not override your current instructions.

The tool list carries everyday tools (data reads and writes, topics, image, video, voice, transcription, and delegation); for video editing, asset and manuscript management, and other work, the Agent finds tools with creator_tools and calls them with creator_tool_call. Direct calls take {input} and run in Beav's active workspace; use sessionId from creator_session_open to pin a workspace and a stable idempotencyKey for writes or generation you may retry. Codex can work directly or use creator_delegate when you want Beav's Agent to do the work. The browser is for you to view and pick materials; Agent data operations continue through MCP.

For delegated work, follow-up changes keep querying and continuing the same Beav task. A delegated task's terminal state does not prove content was saved; read the actual resource reference when the request requires a saved artifact. Direct tool calls do not require a delegated task.

The machine-readable install contract lives at https://beav.pro/agent.md.

Save writing and build delivery packages

Ask the connected AI to “save this article to my Beav manuscript library,” or specify a platform and ask it to turn a manuscript into a delivery package. The Agent saves into the active workspace and reports the title and resource references. Continue viewing or editing in Beav under Account archives → Manuscripts; the platform packages are attached to the same manuscript. Building a package does not publish it.

This reuses existing MCP tools: discover manuscripts_create_project, manuscripts_write, and the manuscripts_packages_begin/build/list tools with creator_tools, then invoke them through creator_tool_call. The Agent reads the actual saved body and package resources; a chat response or arbitrary workspace Markdown file is not a manuscript-library save. Later package edits reopen the same manuscript/platform context and keep the existing package ID and URI instead of creating duplicate manuscripts. Saving an article alone does not require selecting a platform.

On 2026-10-08, real MCP calls against Beav 2.8.14 verified creation, body save/read-back, manuscript listing, generic text package build/read-back, same-package update, and moving the test manuscript to recoverable trash. This check did not cover image packages, paid media generation or platform publication. The interfaces already exist; the expanded Skill guidance requires a new Beav build and plugin refresh. Installation verification only reads data and discovers capabilities, without creating test manuscripts.

Connecting WorkBuddy

Send this prompt to WorkBuddy:

Read https://beav.pro/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 and checks for a local Beav installation. If Beav is missing, WorkBuddy asks you to install the Beav desktop app, waits, then continues in the same task; it does not prepare or install the plugin yet. codebuddy does not need to be on the shell PATH.
3. Gives you the full path to the installed Beav desktop app's executable (shown below as <BEAV_APP>). In a normal Terminal outside WorkBuddy, run "<BEAV_APP>" open --output json followed by "<BEAV_APP>" extension prepare workbuddy --output json, then send WorkBuddy only the second command's marketplacePath. WorkBuddy's command sandbox may block Beav from writing local runtime files, so do not keep retrying preparation there.
4. Reads the plugin manifests at that path, validates the marketplace with codebuddy plugin validate, then installs beav-creator@beav-local at user scope. Do not send the full preparation result or credentials.
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://beav.pro/workbuddy.md.