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/kombai-workflow/SKILL.md →

README.md

− removed · + added

--- before
+++ after
@@ -17,7 +17,12 @@
 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, verify the entry, and direct you to start a new Codex task for the tools.
+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
@@ -31,7 +36,11 @@
 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.
 
-Sign in inside the Kombai app before starting work. The plugin never requests credentials in chat or stores them in MCP arguments.
+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.
+
+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.
+
+Kombai's questions during a run are asked in the Codex chat: `chat_question` shows them as a card the user answers in.
 
 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`.