@wular/coder 0.1.4 → 0.1.7

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@wular/coder",
-  "version": "0.1.4",
+  "version": "0.1.7",
   "description": "Delegating coding-agent runtime",
   "type": "module",
   "bin": {

package/plugins/claude/commands/setup.md

@@ -1,17 +1,20 @@
 ---
 description: Set up the Coder runtime (install the CLI, verify engines, configure the chain)
+model: sonnet
+effort: low
 ---
 
-Set up the Coder runtime for this machine. Use AskUserQuestion for the decision points.
+Set up the Coder runtime for this machine. Work quickly and tersely: run the
+shell steps, keep commentary to a line or two, and only expand when something
+needs the user's decision. Use AskUserQuestion for the decision points.
 
-1. Runtime: `command -v coder`; if missing, install it (`npm install -g @wular/coder`).
-2. Run `coder setup --json` and read it (codex/claude availability and auth).
-3. Tell the user Coder uses Codex as the primary engine with Claude as fallback, and ask if that ordering suits them. If they prefer Claude first: `coder config set chain claude,codex`.
-4. If Codex is kept first but is not ready:
-   - Not installed: ask if they want it installed; on yes run `npm install -g @openai/codex`.
-   - Not logged in: ask them to run `codex login` themselves (interactive), then re-run `coder setup` to confirm.
-   - If they decline Codex: `coder config set chain claude,codex` so tasks go straight to the Claude engine, and say Codex can be enabled later by reversing the chain.
-5. Show the final config (`coder config`) and mention overrides live in `~/.coder/config.json` (machine) and `coder.config.json` (per repo).
-6. Suggest trying it: "Use Coder to <some small task>".
+1. In one shell call, ensure the runtime then read its status:
+   `command -v coder >/dev/null || npm install -g @wular/coder; coder setup --json`
+   (codex/claude availability and auth are in the JSON).
+2. Codex is the recommended primary engine; Claude (opus subagents in Claude Code) is the fallback. Choose the default from what is installed. Do NOT ask about chain ordering:
+   - **Codex installed** (logged in, or logged out; installed still counts): keep the default `codex → claude` chain. If it is logged out, tell the user to run `codex login` themselves, then re-run `coder setup` to confirm.
+   - **Codex not installed**: run `coder config set chain claude,codex` so tasks run on Claude opus subagents immediately, tell the user that is the default for now, then ask (AskUserQuestion) whether to install Codex since it is the recommended primary. On yes: `npm install -g @openai/codex`, have them run `codex login`, then `coder config set chain codex,claude`.
+3. Show the final config (`coder config`) and mention overrides live in `~/.coder/config.json` (machine) and `coder.config.json` (per repo).
+4. Suggest trying it: "Use Coder to <some small task>".
 
 $ARGUMENTS

package/plugins/claude/skills/coder/SKILL.md

@@ -7,7 +7,7 @@ description: Use Coder for any coding, implementation, or investigation task - f
 
 You dispatch coding tasks through the `coder` runtime instead of implementing them yourself. By default the runtime picks the engine from its configured chain; Flags like `--agent`/`--model`/`--effort` override it.
 
-If `coder` is not on PATH, tell the user to set it up (`npm install -g @wular/coder`, then `/coder:setup`) and stop.
+If `coder` is not on PATH, install it yourself without asking (`npm install -g @wular/coder`), then continue; suggest the user run `/coder:setup` to configure the engines and chain.
 
 ## Dispatching a task
 

package/plugins/codex/skills/coder/SKILL.md

@@ -7,7 +7,7 @@ description: Use Coder for any coding, implementation, or investigation task - f
 
 You dispatch coding tasks through the `coder` runtime instead of implementing them yourself. By default the runtime picks the engine from its configured chain; `--agent`/`--model`/`--effort` override it. You never spawn agents yourself in this host.
 
-If `coder` is not on PATH, set it up yourself: `npm install -g @wular/coder`, then `coder setup --codex`. Only if that fails, show the user the error and those two commands. On first setup, mention the chain is Codex-first and Claude on fallback; if the user prefers Claude engines first, run `coder config set chain claude,codex` (the Claude engine needs the claude CLI: `npm install -g @anthropic-ai/claude-code`, then run `claude` once to log in).
+If `coder` is not on PATH, install it yourself without asking: `npm install -g @wular/coder`, then `coder setup --codex`. Only if that fails, show the user the error and those two commands. On first setup, mention the chain is Codex-first with Claude on fallback. The Claude fallback engine needs the claude CLI; if it is not installed, ask the user before installing it (on yes: `npm install -g @anthropic-ai/claude-code`, then have them run `claude` once to log in). If the user prefers Claude engines first, run `coder config set chain claude,codex`.
 
 ## Dispatching a task