Update to Kombai

Changed files

Choose a file to see its text changes. Binary or large files show metadata only.

.codex-plugin/plugin.json →

README.md →

kombai.package.json →

skills/about-kombai/SKILL.md →

skills/about-kombai/agents/openai.yaml →

skills/get-started-with-kombai/SKILL.md →

skills/get-started-with-kombai/agents/openai.yaml →

skills/kombai-workflow/SKILL.md →

skills/kombai-workflow/agents/openai.yaml →

skills/work-with-kombai/SKILL.md →

skills/work-with-kombai/agents/openai.yaml →

README.md

− removed · + added

--- before
+++ after
@@ -1,8 +1,16 @@
 # Kombai for Codex
 
-This plugin teaches Codex to hand UI design and implementation work to the installed Kombai desktop app. It supplies a workflow skill and visual assets. The app independently owns the local `kombai` MCP server; this payload contains no MCP executable, `.mcp.json`, or fixed localhost address.
+This plugin's `work-with-kombai` skill runs the Kombai CLI (`npx -y @kombai/cli@0.1.5 skill`) and follows what it prints: Codex designs on a hosted Kombai canvas. The CLI needs Node.js 20 or later.
 
-Kombai must be installed and its MCP registered with Codex. You can turn on Codex in Kombai's MCP settings, or run `mcp install codex` through the **installed Kombai app executable**. The command requires a packaged Kombai build that includes this operation; it writes the Codex entry and the app's existing client skills. Check the result with `codex mcp get kombai --json`. If Codex cannot see newly registered tools in its current task, start a new Codex task.
+Its `about-kombai` skill runs `npx -y @kombai/cli@0.1.5 skill faq` and answers the user's questions about Kombai (accounts, credits, where designs and data live, updates, support) from what it prints.
+
+The skill requests approved execution outside Codex's sandbox before this first `npx` call
+and for later Kombai CLI commands, using the execution tool's
+`sandbox_permissions: "require_escalated"` setting. npm may need network access before Kombai
+starts, and the CLI writes `~/.kombai`. Update the installed plugin to receive this bootstrap
+guidance; updating only the CLI does not change the installed skill.
+
+The plugin ships skills only (`cli.view` is off in `kombai.package.json`, and `requires_local_executor` is set in the manifest): OpenAI's plugin directory drops a plugin's local MCP config. Kombai's canvas view is the Kombai CLI's MCP server, `kombai` (`npx -y @kombai/cli@0.1.5 mcp`), in the user's own Codex config. Setting the plugin up right after installing it runs its onboarding skill, `get-started-with-kombai` (the manifest's `onboardingSkill`; Codex's Try now after an install asks for it too, through the manifest's first `defaultPrompt`), which adds that server with `npx -y @kombai/cli@0.1.5 mcp install codex`, checks the Kombai sign-in, and ends with links that each open a new chat with a Kombai prompt filled in, so the user's first design chat has the view from its first message. Codex gives a chat only the MCP servers it had when it started, so that first onboarding chat can't show the canvas. The user can run the onboarding again: in a chat that has Kombai's view it shows the CLI's starters card, prompts to try with a Try button each. If the user skipped setup, the first time the `work-with-kombai` skill finds no `canvas_app` tool, it runs, without asking, `npx -y @kombai/cli@0.1.5 mcp install codex` to add that server to `config.toml` (`$CODEX_HOME`, else `~/.codex`), and continues in a new task, since a running task never picks up a new MCP server. `npx -y @kombai/cli@0.1.5 mcp uninstall codex` takes the entry out again; uninstalling the plugin leaves it in place. In the Codex desktop app the view is the only way the skill shows a canvas: never a browser or a link. Codex in a terminal gets no view; the skill opens the canvas in the browser instead. The skills read the plugin's Codex id from their own install path (`plugins/cache/<marketplace>/kombai/…`), for the `@Kombai` mention a new chat's prompt starts with: the same ZIP installs as `kombai@openai-curated-remote` from OpenAI's directory and under its marketplace's name when added as a local marketplace.
 
 For local development, point Codex at this package's marketplace root, then install its plugin:
 
@@ -11,37 +19,20 @@
 codex plugin add kombai@kombai --json
 ```
 
-This installs the plugin payload only. Register the MCP from the installed Kombai app or its settings.
-
-To rehearse the user journey, install this plugin **before** installing Kombai Dev. Ask Codex to
-use Kombai Dev for a task. It should explain that the requested app build is missing, without
-offering the production download as a substitute. Install and sign in to your Dev build, then
-tell Codex to continue. The workflow skill should locate that installed build, register its
-MCP with Codex (in a sandboxed task it should first ask to run that command outside the
-sandbox; when the chat's permissions refuse that, as they do in a desktop chat with no project
-set to ask for approval, it should ask you to switch the chat's permissions or run the command in
-Terminal), verify the entry, and offer to start a new Codex task that carries your request, since
-the current task cannot load the new tools. In the desktop app it starts that task itself once
-you agree; in the CLI or IDE extension it asks you to start one.
-
-For a direct registration diagnostic, `mcp install codex` must run through the installed
-**Kombai Dev** executable, not the production app. On macOS, find the executable name in that app's
-`Contents/Info.plist` and run the binary under `Contents/MacOS/`. Then inspect
-`codex mcp get kombai --json`: its command and gateway paths should point into the Dev
-installation, and its registration argument should name that build's launch record.
-Start a new Codex task after registration so it loads the changed MCP entry.
-
-The app's launch record is separate for each build identity, including Dev and variants.
-Codex currently has one user-level MCP key, `kombai`, shared by those builds. Registering
-another installed build replaces that key, and an opted-in app can refresh it at startup.
-Re-run the desired build's install command before testing if the entry points elsewhere.
+To install a packaged build, unzip `kombai-codex-plugin-0.4.2.zip` into a directory you will keep.
+The extracted root contains `.agents/plugins/marketplace.json`, which points to the bundled
+`plugins/codex` directory. Register the extracted root, then install the plugin:
 
-When Kombai is not installed, the workflow skill installs the official production build itself (Homebrew cask or the signed installer from agent.kombai.com, signature checked first) instead of sending the user to a download page; Codex asks the user to approve the download and the install. A non-production build is never substituted.
+```sh
+codex plugin marketplace add /absolute/path/to/kombai-codex-plugin-0.4.2 --json
+codex plugin add kombai@kombai --json
+```
 
-Signing in needs no visit to the Kombai app: a `not_signed_in` refusal opens Kombai's sign-in page in the user's browser, and the app finishes the sign-in by polling. The plugin never requests credentials in chat or stores them in MCP arguments.
+Start a new Codex chat after installation. Versions through 0.3.4 packaged only the plugin
+payload and cannot be registered directly as a marketplace; use a 0.3.5 or later ZIP.
 
-Kombai's questions during a run are asked in the Codex chat: `chat_question` shows them as a card the user answers in.
+Signing in happens in the browser: the CLI opens Kombai's sign-in page and shows a match code to compare. The plugin never requests credentials in chat or stores them in MCP arguments.
 
-The skill is [`skills/kombai-workflow/SKILL.md`](skills/kombai-workflow/SKILL.md). It complements the task-specific Kombai skills installed by the app, such as `design-with-kombai` and `code-with-kombai`.
+The skills are [`skills/work-with-kombai/SKILL.md`](skills/work-with-kombai/SKILL.md) and [`skills/about-kombai/SKILL.md`](skills/about-kombai/SKILL.md).
 
 Licensed under the [MIT License](LICENSE).