bluekiwi 0.3.19 → 0.3.20

package/dist/assets/index.js

@@ -12,6 +12,7 @@ export const BUNDLED_SKILLS = [
     "bk-instruction",
     "bk-credential",
     "bk-design",
+    "bk-import",
     "bk-improve",
     "bk-report",
     "bk-scan",

package/dist/assets/skills/bk-design/SKILL.md

@@ -58,14 +58,14 @@ Ask via AskUserQuestion:
 
 ### Step 4: Design Workflow Structure
 
-Analyze the goal and design the nodes.
+Analyze the goal and design the nodes. **Every node instruction must satisfy the Instruction Depth Standard below before proceeding to Step 5.**
 
 **Node structure example:**
 
 ```json
 {
   "title": "Clarify Goal",
-  "instruction": "Analyze the user's stated goal and extract the 3 most important clarifying questions.",
+  "instruction": "## Goal Clarification\n\nExtract precise requirements before any work begins:\n\n1. Read the user's stated goal word by word and list every ambiguity.\n2. For each ambiguity, formulate one closed-ended question (yes/no or multiple choice).\n3. Ask the questions one at a time — never batch them.\n\n**Output**: A numbered list of confirmed constraints and success criteria.\n**Verification**: Every ambiguity is resolved; no open questions remain.",
   "node_type": "action",
   "hitl": false,
   "order": 1
@@ -184,6 +184,75 @@ Type `/bk-run` to execute it now.
 - Use `visual_selection: true` on `gate` nodes when the selection is best expressed visually — e.g., choosing a layout, picking a chart type, selecting a UI template. The agent must call `set_visual_html` with interactive HTML before executing the step; the user's click supplies the response.
 - For nodes requiring external API calls, specify `credential_id`. Create credentials first with `/bk-credential`.
 
+## Instruction Depth Standard
+
+<HARD-RULE>
+Before calling `create_workflow`, verify every node instruction satisfies ALL of the following:
+
+1. **Role/context** (first line or heading): who or what performs this step — e.g., "## Market Analyst", "You are acting as a senior code reviewer"
+2. **Numbered sub-steps**: at minimum 2 explicit steps describing HOW to perform the action, not just WHAT to produce
+3. **Output specification**: exactly what is produced — file path + format, structured data shape, or required fields
+4. **Verification**: one line stating how to confirm the step succeeded
+5. **Loop nodes only**: termination condition as the final line — "Termination: end when X"
+
+**Minimum instruction length: 80 words.** If an instruction is shorter, it is not specific enough — expand it.
+</HARD-RULE>
+
+### Anti-patterns → Prescriptive Rewrites
+
+| ❌ Vague — do not write    | ✅ Prescriptive — write this instead                                                                                                                                                           |
+| -------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| "Analyze the data."        | "Read the CSV at `data/input.csv`. Compute row count, null counts per column, and value distributions for numeric columns. Output a summary table to `data/eda-summary.md`."                   |
+| "Review the results."      | "Check each output against the success criteria from Step 1. Build a pass/fail table with one evidence line per criterion. Flag any criterion below threshold in red."                         |
+| "Ask the user what to do." | "Present exactly 3 options via bk-options (sm): A) proceed as-is, B) revise the output, C) abort. Include a one-sentence consequence for each option."                                         |
+| "Generate a report."       | "Create `docs/report-YYYY-MM-DD.md` with sections: Executive Summary (3 bullets), Findings (numbered, each with evidence), Recommendations (priority-ordered), Next Steps (owner + deadline)." |
+| "Search the web."          | "Run a web search for each of the 3 queries listed. For each result, record: source URL, publication date, key claim (1 sentence). Discard results older than 12 months."                      |
+
+### Instruction Templates by Node Type
+
+**action — data / research step:**
+
+```
+## <Expert Role>
+
+<One sentence: what this step accomplishes and why it matters here.>
+
+1. <First concrete action — tool call, file read, calculation>
+2. <Second concrete action — transformation, filtering, aggregation>
+3. <Third action if needed>
+
+**Output**: <Exact file path or data structure>
+**Verification**: <Command or check that confirms success>
+```
+
+**gate — user decision:**
+
+```
+<Brief context: what was just produced and what the user must decide.>
+
+Present options using bk-options (size=sm):
+- A) <Option> — <one-sentence consequence>
+- B) <Option> — <one-sentence consequence>
+- C) <Option> — <one-sentence consequence>
+
+Mark the recommended option with `data-recommended`.
+```
+
+**loop — iterative interaction:**
+
+```
+## <Role>
+
+<What is being iterated and why iteration is needed.>
+
+Each iteration:
+1. <What to present or ask>
+2. <How to process the response>
+3. <How to update state>
+
+**Termination**: End when <specific, measurable condition>.
+```
+
 #### VS Component Selection Guide
 
 When designing a `visual_selection: true` gate node, specify which `bk-*` components the agent should use in the node instruction. This keeps VS screens consistent and prevents vague "make a selection UI" instructions.

package/dist/assets/skills/bk-help/SKILL.md

@@ -1,48 +1,66 @@
 ---
 name: bk-help
-description: BlueKiwi help skill. Shows a formatted list of all available bk-* commands with descriptions and usage. Use when the user says "/bk-help", "bk help", "what bk commands are there", or asks about BlueKiwi commands.
+description: BlueKiwi help skill. Shows a formatted list of all available bk-* commands with descriptions and usage examples. Use when the user says "/bk-help", "bk help", "what bk commands are there", or asks about BlueKiwi commands.
 user_invocable: true
 ---
 
 # BlueKiwi Help
 
-Output the following help text **exactly as formatted** (use markdown code-free output — render it as readable text, not a code block).
+Detect the user's language and output the matching section below **exactly as formatted** (render as readable text, not a code block).
+
+**Language detection — check in this order, use the first signal found:**
+
+1. **Conversation language**: the language the user wrote the current message in
+2. **System locale**: run `echo $LANG` or `locale` in shell — use the language portion (e.g. `ko` from `ko_KR.UTF-8`, `en` from `en_US.UTF-8`)
+3. **OS language**: check `defaults read -g AppleLanguages 2>/dev/null` (macOS) or `/etc/locale.conf` (Linux)
+4. **Fallback**: English
+
+Map detected language to output:
+
+- `ko` / `ko_KR` → **Korean** section
+- Anything else → **English** section
 
 ---
 
+## Korean output
+
 ## BlueKiwi 명령어 도움말
 
 ### 실행
 
-| 명령어                           | 설명                                                |
-| -------------------------------- | --------------------------------------------------- |
-| `/bk-start`                      | 워크플로 선택 후 즉시 실행. 미완료 태스크 복구 포함 |
-| `/bk-start <이름>`               | 이름으로 워크플로 매칭 후 바로 실행                 |
-| `/bk-start <ID>`                 | 워크플로 ID로 바로 실행 (숫자)                      |
-| `/bk-start #<태스크ID>`          | 특정 태스크 직접 재개                               |
-| `/bk-start <이름> :: <프롬프트>` | 워크플로 지정 + 초기 컨텍스트 전달                  |
-| `/bk-next`                       | 실행 중인 태스크를 찾아 현재 스텝부터 재개          |
-| `/bk-approve`                    | 대기 중인 HITL 승인 처리                            |
-| `/bk-rewind`                     | 이전 스텝으로 되돌리기                              |
+| 명령어                           | 설명                                                | 사용 예시                               |
+| -------------------------------- | --------------------------------------------------- | --------------------------------------- |
+| `/bk-start`                      | 워크플로 선택 후 즉시 실행. 미완료 태스크 복구 포함 | `/bk-start`                             |
+| `/bk-start <이름>`               | 이름으로 워크플로 매칭 후 바로 실행                 | `/bk-start 시장조사`                    |
+| `/bk-start <ID>`                 | 워크플로 ID로 바로 실행 (숫자)                      | `/bk-start 42`                          |
+| `/bk-start #<태스크ID>`          | 특정 태스크 직접 재개                               | `/bk-start #108`                        |
+| `/bk-start <이름> :: <프롬프트>` | 워크플로 지정 + 초기 컨텍스트 전달                  | `/bk-start 코드리뷰 :: PR #77 리뷰해줘` |
+| `/bk-next`                       | 실행 중인 태스크를 찾아 현재 스텝부터 재개          | `/bk-next`                              |
+| `/bk-approve`                    | 대기 중인 HITL 승인 처리                            | `/bk-approve`                           |
+| `/bk-rewind`                     | 이전 스텝으로 되돌리기                              | `/bk-rewind`                            |
 
 ### 설계 / 관리
 
-| 명령어            | 설명                                       |
-| ----------------- | ------------------------------------------ |
-| `/bk-design`      | 자연어 목표로 새 워크플로 설계 및 등록     |
-| `/bk-improve`     | 기존 워크플로 분석 후 개선 버전 생성       |
-| `/bk-version`     | 버전 목록 조회, 활성화/비활성화, 버전 비교 |
-| `/bk-instruction` | 에이전트 인스트럭션 템플릿 생성·수정·삭제  |
-| `/bk-credential`  | 외부 서비스 API 키 등록·수정·삭제          |
+| 명령어            | 설명                                              | 사용 예시                                         |
+| ----------------- | ------------------------------------------------- | ------------------------------------------------- |
+| `/bk-design`      | 자연어 목표로 새 워크플로 설계 및 등록            | `/bk-design 경쟁사 분석 워크플로 만들어줘`        |
+| `/bk-import`      | GitHub / 로컬 스킬 / URL을 분석해 워크플로로 변환 | `/bk-import yamadashy/repomix`                    |
+|                   |                                                   | `/bk-import bk-design`                            |
+|                   |                                                   | `/bk-import https://example.com/runbook`          |
+|                   |                                                   | `/bk-import` (대화형 — 텍스트·JSON 붙여넣기 포함) |
+| `/bk-improve`     | 기존 워크플로 분석 후 개선 버전 생성              | `/bk-improve 시장조사`                            |
+| `/bk-version`     | 버전 목록 조회, 활성화/비활성화, 버전 비교        | `/bk-version`                                     |
+| `/bk-instruction` | 에이전트 인스트럭션 템플릿 생성·수정·삭제         | `/bk-instruction`                                 |
+| `/bk-credential`  | 외부 서비스 API 키 등록·수정·삭제                 | `/bk-credential`                                  |
 
 ### 조회 / 공유
 
-| 명령어       | 설명                               |
-| ------------ | ---------------------------------- |
-| `/bk-status` | 실행 중·완료된 태스크 현황 조회    |
-| `/bk-report` | 태스크 결과 구조화 리포트 생성     |
-| `/bk-share`  | 워크플로·폴더를 그룹에 공유        |
-| `/bk-scan`   | 로컬 저장소 보안·컴플라이언스 스캔 |
+| 명령어       | 설명                               | 사용 예시                       |
+| ------------ | ---------------------------------- | ------------------------------- |
+| `/bk-status` | 실행 중·완료된 태스크 현황 조회    | `/bk-status`                    |
+| `/bk-report` | 태스크 결과 구조화 리포트 생성     | `/bk-report`                    |
+| `/bk-share`  | 워크플로·폴더를 그룹에 공유        | `/bk-share 시장조사 → 마케팅팀` |
+| `/bk-scan`   | 로컬 저장소 보안·컴플라이언스 스캔 | `/bk-scan`                      |
 
 ---
 
@@ -51,3 +69,53 @@ Output the following help text **exactly as formatted** (use markdown code-free
 - `/bk-start`는 `/bk-run`의 상위 호환입니다 — 두 명령어 모두 동작합니다.
 - 태스크 재개가 필요하면 `/bk-start` (인자 없음) 또는 `/bk-start #<태스크ID>`를 사용하세요.
 - 도움말은 언제든 `/bk-help`로 다시 볼 수 있습니다.
+
+---
+
+## English output
+
+## BlueKiwi Command Reference
+
+### Execution
+
+| Command                        | Description                                            | Example                                  |
+| ------------------------------ | ------------------------------------------------------ | ---------------------------------------- |
+| `/bk-start`                    | Pick a workflow and run it. Recovers incomplete tasks. | `/bk-start`                              |
+| `/bk-start <name>`             | Match workflow by name and run immediately             | `/bk-start market-research`              |
+| `/bk-start <ID>`               | Run workflow by numeric ID                             | `/bk-start 42`                           |
+| `/bk-start #<taskID>`          | Resume a specific task directly                        | `/bk-start #108`                         |
+| `/bk-start <name> :: <prompt>` | Specify workflow + pass initial context                | `/bk-start code-review :: review PR #77` |
+| `/bk-next`                     | Find the active task and resume from the current step  | `/bk-next`                               |
+| `/bk-approve`                  | Process a pending HITL approval                        | `/bk-approve`                            |
+| `/bk-rewind`                   | Roll back to the previous step                         | `/bk-rewind`                             |
+
+### Design / Management
+
+| Command           | Description                                                         | Example                                               |
+| ----------------- | ------------------------------------------------------------------- | ----------------------------------------------------- |
+| `/bk-design`      | Design and register a new workflow from a natural language goal     | `/bk-design build a competitor analysis workflow`     |
+| `/bk-import`      | Analyze a GitHub repo / local skill / URL and convert to a workflow | `/bk-import yamadashy/repomix`                        |
+|                   |                                                                     | `/bk-import bk-design`                                |
+|                   |                                                                     | `/bk-import https://example.com/runbook`              |
+|                   |                                                                     | `/bk-import` (interactive — includes text/JSON paste) |
+| `/bk-improve`     | Analyze an existing workflow and generate an improved version       | `/bk-improve market-research`                         |
+| `/bk-version`     | List versions, activate/deactivate, compare versions                | `/bk-version`                                         |
+| `/bk-instruction` | Create, edit, or delete agent instruction templates                 | `/bk-instruction`                                     |
+| `/bk-credential`  | Register, edit, or delete external service API keys                 | `/bk-credential`                                      |
+
+### Monitoring / Sharing
+
+| Command      | Description                                        | Example                                      |
+| ------------ | -------------------------------------------------- | -------------------------------------------- |
+| `/bk-status` | View running and completed task status             | `/bk-status`                                 |
+| `/bk-report` | Generate a structured report from task results     | `/bk-report`                                 |
+| `/bk-share`  | Share a workflow or folder with a group            | `/bk-share market-research → marketing-team` |
+| `/bk-scan`   | Run a security and compliance scan on a local repo | `/bk-scan`                                   |
+
+---
+
+**Tips:**
+
+- `/bk-start` is a superset of `/bk-run` — both commands work.
+- To resume a task, use `/bk-start` (no args) or `/bk-start #<taskID>`.
+- Run `/bk-help` anytime to see this reference again.

package/dist/assets/skills/bk-import/SKILL.md

@@ -0,0 +1,224 @@
+---
+name: bk-import
+description: Analyzes an external resource (GitHub repo, local skill, URL, or text) and converts it into a BlueKiwi workflow registered directly on the server. Triggers when the user says "/bk-import", "import from github", "convert this skill to workflow", "create workflow from repo/url/skill", or pastes content they want turned into a workflow.
+user_invocable: true
+---
+
+# bk-import — External Resource to BlueKiwi Workflow
+
+Analyze an external resource, extract its process logic, convert it into a structured BlueKiwi workflow, and register it directly via MCP.
+
+## Argument Handling
+
+- `/bk-import` → Ask for the resource via AskUserQuestion.
+- `/bk-import <resource>` → Start analysis from the provided resource.
+
+## Step 1: Parse Input
+
+Determine the resource type from the argument:
+
+| Type         | Detection rule                                   | Analysis method           |
+| ------------ | ------------------------------------------------ | ------------------------- |
+| GitHub repo  | `https://github.com/…` or `owner/repo` pattern   | repomix `--remote`        |
+| Local skill  | Matches `bk-*` name or `~/.claude/skills/…` path | Read `SKILL.md` + scripts |
+| Local path   | Starts with `/`, `./`, or `~/`                   | Read files directly       |
+| External URL | `http://` or `https://` (non-GitHub)             | WebFetch                  |
+| Text/JSON    | Anything else                                    | Direct parse              |
+
+If no argument, ask via AskUserQuestion:
+
+- header: "Import from where?"
+- "Which resource do you want to convert into a BlueKiwi workflow?"
+- options: ["GitHub repo URL or owner/repo", "Local skill (e.g. bk-run)", "External URL", "Paste text or JSON"]
+
+## Step 2: Fetch & Analyze Content
+
+### GitHub Repository
+
+```bash
+npx repomix@latest --remote <owner/repo> --compress --output /tmp/bk-import-<repo-name>.xml
+```
+
+After packing, extract in order:
+
+1. File tree → identify architecture layers (API, UI, scripts, config)
+2. README.md → purpose, key steps, usage examples
+3. Main entry points (index, main, app) → sequential process logic
+4. Configuration files → decision points and branching options
+
+Clean up when done: `rm /tmp/bk-import-<repo-name>.xml`
+
+**If the repo URL points to a subdirectory** (e.g., `…/tree/main/packages/cli`), run repomix on the full repo then focus grep analysis on that path.
+
+### Local Skill
+
+Resolve path:
+
+- Bare name (e.g. `bk-run`) → `~/.claude/skills/bk-run/SKILL.md`
+- Full path → read directly
+
+Read `SKILL.md` completely. Also read any files under `scripts/` if present.
+
+Extract:
+
+- Numbered or headed execution steps → sequential actions
+- Options/choices presented to the user → decision points
+- "Repeat until" or loop patterns → iterative steps
+
+### External URL
+
+```
+WebFetch <url>
+```
+
+Extract the main process described: step sequences, decision criteria, iterative patterns.
+
+### Text / JSON Paste
+
+If JSON: detect format (n8n workflow, GitHub Actions, etc.) and parse its nodes/steps/jobs structure.
+
+If plain text: extract numbered or headed steps, conditionals, and loops.
+
+## Step 3: Extract Workflow Logic
+
+From the analyzed content, identify and label each element:
+
+**Sequential execution → `action` node candidates**
+
+- "Do X, then Y" patterns
+- Script / CLI execution steps
+- Data fetching or transformation steps
+- API calls, file generation, report writing
+
+**Decision points → `gate` node candidates**
+
+- User approval required before continuing
+- "Choose between A or B" patterns
+- Final review before an irreversible action
+
+**Iterative patterns → `loop` node candidates**
+
+- "Repeat until condition met"
+- Q&A / clarification loops (ask one question, get answer, repeat)
+- Review → feedback → revise cycles
+
+**Human sign-off for risky actions → `hitl: true` on action nodes**
+
+- Sending emails or external messages
+- Deploying to production
+- Deleting or overwriting data
+
+## Step 4: Design Nodes
+
+Convert the extracted logic into BlueKiwi nodes. Apply the **Instruction Depth Standard** (same rules as bk-design) to every node:
+
+<HARD-RULE>
+Every node instruction must include ALL of the following:
+
+1. **Role/context** (1 line): who or what performs this step
+2. **Numbered sub-steps**: at least 2 explicit steps describing HOW — not just WHAT
+3. **Output specification**: exactly what is produced (file path, format, structure)
+4. **Verification**: how to confirm the step succeeded
+5. **Loop nodes only**: explicit termination condition on the last line
+
+Minimum instruction length: 80 words. One-sentence summaries are rejected.
+</HARD-RULE>
+
+**Anti-patterns to avoid when writing instructions:**
+
+| ❌ Do not write           | ✅ Write instead                                                                                                                                                                   |
+| ------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| "Analyze the repository." | "Read README.md and list top-level directories. For each dir, identify its role. Output a bullet-point component map covering tech stack, architecture pattern, and entry points." |
+| "Review the results."     | "Check output against the success criteria from Step 1. Present a pass/fail table with specific evidence per criterion. Flag any item below threshold."                            |
+| "Ask the user."           | "Present exactly 3 options via bk-options (sm): A) proceed, B) revise, C) cancel. Include a one-sentence consequence for each."                                                    |
+
+**Node count target:** 4–8 nodes. If the source describes more than 10 distinct steps, group related micro-steps into single nodes.
+
+## Step 5: Present Proposed Structure
+
+Display the proposed workflow to the user:
+
+```
+📦 Importing: <resource name>
+
+Proposed workflow: <title>
+━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
+1. [Step Name]           action
+2. [Step Name]           gate      ← user approval
+3. [Step Name]           loop  ↩   repeats until X
+4. [Step Name]           action    🔒 hitl
+━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
+<N> steps  ·  source: <resource>
+```
+
+Ask via AskUserQuestion:
+
+- header: "Confirm import"
+- "Create this workflow from <resource>?"
+- options: ["Create", "Edit node structure", "Cancel"]
+
+If "Edit" → accept modification input, redesign affected nodes, and re-present.
+
+## Step 6: Select Folder
+
+Call `list_folders`. Ask via AskUserQuestion:
+
+- header: "Save location"
+- "Which folder should this workflow be saved in?"
+- options: folder name list (up to 4) + "My Workspace (default)"
+
+## Step 7: Register via MCP
+
+Call `create_workflow`:
+
+```json
+{
+  "title": "<derived title — concise, action-oriented>",
+  "description": "<1–2 sentences: what this workflow does and when to use it>",
+  "version": "1.0",
+  "folder_id": <selected folder id>,
+  "nodes": [
+    {
+      "step_order": 1,
+      "node_type": "action",
+      "title": "...",
+      "instruction": "...",
+      "hitl": false,
+      "loop_back_to": null,
+      "visual_selection": false
+    }
+  ]
+}
+```
+
+## Step 8: Report Result + Open in Browser
+
+On success:
+
+```bash
+open "${WEBUI_URL}/workflows/${WORKFLOW_ID}"
+```
+
+`WEBUI_URL` = the `webui_url` field returned by `create_workflow`.
+
+Display:
+
+```
+✅ Workflow imported
+Name:   <title> (ID: <id>)
+Source: <resource>
+Steps:  <n>
+🔗 ${WEBUI_URL}/workflows/${WORKFLOW_ID}
+
+Type /bk-run to execute it now.
+```
+
+## Node Type Quick Reference
+
+| Type                               | Behavior                                     | When to use                                    |
+| ---------------------------------- | -------------------------------------------- | ---------------------------------------------- |
+| `action`                           | Auto-advances                                | Execution, data work, generation               |
+| `gate`                             | Pauses for user input                        | Approval, direction choice, review             |
+| `loop`                             | Repeats until termination condition          | Q&A, iterative refinement, section review      |
+| `hitl: true` on `action`           | Pauses after execution for explicit sign-off | Irreversible or security-sensitive actions     |
+| `visual_selection: true` on `gate` | Agent renders HTML; user clicks to choose    | Visual A/B choices, layout picks, option cards |

package/dist/commands/accept.js

@@ -5,8 +5,17 @@ import { createEmptyConfig, loadConfig, normalizeProfileName, saveConfig, upsert
 import { applyProfileToRuntimes } from "../runtime-sync.js";
 import { detectInstalledAdapters, getAllAdapters } from "../runtimes/detect.js";
 export async function acceptCommand(token, opts) {
-    const profileName = normalizeProfileName(opts.profile);
+    let profileName = normalizeProfileName(opts.profile);
     const currentConfig = loadConfig() ?? createEmptyConfig();
+    if (process.stdin.isTTY && opts.profile === undefined) {
+        const profileAnswer = await prompts({
+            type: "text",
+            name: "profile",
+            message: "Profile name",
+            initial: profileName,
+        });
+        profileName = normalizeProfileName(profileAnswer.profile);
+    }
     console.log(pc.cyan("→ Validating invite..."));
     const validateRes = await fetch(`${opts.server}/api/invites/accept/${token}`);
     if (!validateRes.ok) {

package/dist/commands/init.js

@@ -37,15 +37,27 @@ function maskApiKey(key) {
 }
 export async function initCommand(options = {}) {
     const isNonInteractive = options.yes === true || process.stdin.isTTY !== true;
-    const profileName = normalizeProfileName(options.profile);
+    let profileName = normalizeProfileName(options.profile);
     // Load existing config for pre-filling prompts
     const existingCfg = loadConfig() ?? createEmptyConfig();
-    const existingProfile = getProfile(existingCfg, profileName);
+    let existingProfile = getProfile(existingCfg, profileName);
     let server = normalizeEnvValue(options.server) ??
         normalizeEnvValue(process.env.BLUEKIWI_API_URL) ??
         normalizeEnvValue(process.env.BLUEKIWI_SERVER);
     let apiKey = normalizeEnvValue(options.apiKey) ??
         normalizeEnvValue(process.env.BLUEKIWI_API_KEY);
+    if (!isNonInteractive) {
+        if (options.profile === undefined) {
+            const profileAnswer = await prompts({
+                type: "text",
+                name: "profile",
+                message: "Profile name",
+                initial: profileName,
+            });
+            profileName = normalizeProfileName(profileAnswer.profile);
+            existingProfile = getProfile(existingCfg, profileName);
+        }
+    }
     if (!isNonInteractive && (server === undefined || apiKey === undefined)) {
         const questions = [];
         if (server === undefined) {

package/dist/commands/logout.js

@@ -1,5 +1,5 @@
 import pc from "picocolors";
-import { clearConfig, loadConfig, removeProfile, saveConfig } from "../config.js";
+import { clearConfig, loadConfig, removeProfile, saveConfig, } from "../config.js";
 import { getAllAdapters } from "../runtimes/detect.js";
 import { applyProfileToRuntimes } from "../runtime-sync.js";
 export async function logoutCommand(profileName) {

package/dist/config.js

@@ -27,7 +27,9 @@ function normalizeProfileName(name) {
 }
 function isLegacyConfig(value) {
     const raw = value;
-    return !!raw && typeof raw.server_url === "string" && typeof raw.api_key === "string";
+    return (!!raw &&
+        typeof raw.server_url === "string" &&
+        typeof raw.api_key === "string");
 }
 function normalizeProfile(name, raw) {
     if (!raw ||

package/dist/runtime-sync.js

@@ -1,5 +1,5 @@
 import { BUNDLED_MCP_PATH, BUNDLED_SKILLS } from "./assets/index.js";
-import { requireProfile, } from "./config.js";
+import { requireProfile } from "./config.js";
 import { getAllAdapters } from "./runtimes/detect.js";
 export function applyProfileToRuntimes(config, profileName, runtimeNames) {
     const { profile } = requireProfile(config, profileName);

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "bluekiwi",
-  "version": "0.3.19",
+  "version": "0.3.20",
   "description": "BlueKiwi CLI — install MCP client and skills into your agent runtime",
   "license": "MIT",
   "repository": {