@miphamai/cli 0.56.0 → 0.58.0

package/src/i18n-core/locales/zh-CN.json

@@ -757,8 +757,6 @@
       "manual": "手动模式",
       "accept_edits": "接受编辑",
       "plan_mode": "计划模式 / 只读",
-      "auto": "自动模式",
-      "dont_ask": "不再询问",
       "bypass": "绕过权限"
     },
     "loading": {
@@ -804,8 +802,7 @@
     "assistant": { "role_label": "Mipham Code" },
     "user": { "role_label": "用户" },
     "input": {
-      "placeholder": "输入消息（Esc 取消）...",
-      "vim_help": "[NORMAL] h/j/k/l w/b 0/$ dd yy p u /（Esc 插入）"
+      "placeholder": "输入消息（Esc 清空）..."
     },
     "slash_hints": {
       "label": "命令：",
@@ -942,7 +939,7 @@
     "mcp": { "name": "MCP", "description": "管理 MCP 服务器连接" }
   },
   "errors": {
-    "tool_not_allowed": "工具 \"{name}\" 需要用户批准（权限：ask），未执行。",
+    "tool_not_allowed": "工具 \"{name}\" 需要用户批准（权限：ask），未执行。按 Shift+Tab 切换权限模式，或运行 /permissions。",
     "tool_blocked": "工具 \"{name}\" 被钩子拦截",
     "user_input_blocked": "用户输入被钩子拦截。",
     "dlp_blocked": "请求被 DLP 策略阻止。",
@@ -963,6 +960,7 @@
     "mcp_register_failed": "[mcp] 注册工具 \"{tool}\"（来自服务器 \"{server}\"）失败：{error}",
     "max_tool_turns": "超出最大工具调用轮次（{max}）。部分工具调用未执行。",
     "max_tool_turns_warning": "已达到最大 {max} 轮工具调用。{pending} 个工具调用未执行。请总结当前发现及后续步骤。",
+    "turn_timeout": "任务已超过 {minutes} 分钟无实质产出，已自动停止。建议拆分任务或明确下一步后重新发起。",
     "mcp_not_connected": "错误：MCP 服务器 \"{server}\" 未连接",
     "mcp_tool_error": "MCP 工具错误：{error}",
     "mcp_no_connection": "未找到 \"{name}\" 的连接"

package/src/index.tsx

@@ -305,6 +305,14 @@ export async function runApp(options: RunOptions): Promise<void> {
   const instructions = new InstructionsLoader()
   instructions.loadAll(process.cwd())
 
+  // 空目录提示：愣建文件夹时温和提醒走 mipham init，而非默默开始（寒暄克制——一句即可）
+  const { isEmptyProject } = await import('./core/project-scaffold')
+  if (isEmptyProject(process.cwd())) {
+    console.log(
+      '\n💡 空目录。运行 `mipham init` 生成规范项目文档（CLAUDE.md / MIPHAM.md / README.md），或直接开始对话。\n',
+    )
+  }
+
   // Load skills
   const skillsLoader = new SkillsLoader()
   skillsLoader.loadBuiltinFromPackage()

package/src/security/gate.ts

@@ -28,8 +28,9 @@ const PROMPT_INJECTION_PATTERNS: Array<{ regex: RegExp; label: string }> = [
 ]
 
 const DANGEROUS_BASH_PATTERNS: Array<{ regex: RegExp; label: string }> = [
-  { regex: /\$\(.+\)/, label: 'command-substitution' },
-  { regex: /`[^`]+`/, label: 'backtick-substitution' },
+  // NOTE: command substitution ($( … ) / `…`) is legitimate Bash syntax and is NOT
+  // blocked here — its dangerous content (a pipe to sh/bash, a chained rm/cat/sh,
+  // …) is still caught by the pipe/chain patterns below.
   { regex: /;\s*(rm|cat|sh|bash)\b/, label: 'command-chain-injection' },
   { regex: /curl.+\|\s*(sh|bash)\b/, label: 'curl-pipe-shell' },
   { regex: /\|\s*(sh|bash)\b/, label: 'pipe-to-shell' },

package/src/shared/graft-stats.ts

@@ -1,5 +1,5 @@
 import { readFileSync, existsSync } from 'node:fs'
-import { join } from 'node:path'
+import { join, resolve, dirname } from 'node:path'
 
 /** Graft's hook-maintained stats cache (`graft/.cache/stats.json`). */
 export interface GraftStats {
@@ -34,3 +34,20 @@ export function readGraftStats(cwd: string): GraftStats | null {
     return null
   }
 }
+
+/**
+ * Find the nearest graft graph by walking up from `cwd` to the filesystem root.
+ * Graft builds its cache at the repo root (`graft/.cache/stats.json`), so this
+ * also resolves when `cwd` is a subdirectory of a graft-indexed repo — not only
+ * the repo root itself.
+ */
+export function findGraftStats(cwd: string): GraftStats | null {
+  let dir = resolve(cwd)
+  for (;;) {
+    const stats = readGraftStats(dir)
+    if (stats) return stats
+    const parent = dirname(dir)
+    if (parent === dir) return null
+    dir = parent
+  }
+}

package/src/shared/package-info.ts

@@ -9,7 +9,7 @@
 export const PACKAGE_NAME = '@miphamai/cli' as const
 
 /** 当前发布版本 */
-export const PACKAGE_VERSION = '0.56.0' as const
+export const PACKAGE_VERSION = '0.58.0' as const
 
 /** npm install 全局安装命令 */
 export const NPM_INSTALL_COMMAND = `npm install -g ${PACKAGE_NAME}` as const

package/src/shared/types.ts

@@ -130,7 +130,7 @@ export interface MiphamConfig {
   version: string
   defaultProvider: string
   defaultModel: string
-  permission: ToolPermission
+  permission: PermissionLevel
   /** Org-level permission restrictions (forbiddenModes, maxAllowedMode). */
   permissionRestrictions?: PermissionRestrictions
   /** User-defined permission rules (allow/deny patterns), wired into the runtime PermissionSystem. */
@@ -269,12 +269,11 @@ export interface InstructionFile {
 }
 
 // ── Permission Types ──
-/** Six explicit permission modes matching Claude Code's permission architecture */
-export type PermissionMode =
-  'default' | 'acceptEdits' | 'plan' | 'auto' | 'dontAsk' | 'bypassPermissions'
+/** Four explicit permission modes matching Claude Code's permission architecture */
+export type PermissionMode = 'default' | 'acceptEdits' | 'plan' | 'bypassPermissions'
 
-/** Backward-compatible alias: PermissionMode plus legacy 'ask' and 'bypass' */
-export type PermissionLevel = PermissionMode | 'ask' | 'bypass'
+/** Backward-compatible alias: PermissionMode plus legacy 'auto'/'ask'/'bypass' */
+export type PermissionLevel = PermissionMode | 'auto' | 'ask' | 'bypass'
 
 /** Org-level restrictions that cap or forbid specific permission modes. */
 export interface PermissionRestrictions {

package/src/skills/bundled-skills.ts

@@ -17,7 +17,7 @@ export const BUNDLED_SKILLS: ReadonlyArray<BundledSkill> = [
   { type: 'standard', raw: "---\nname: grill-with-docs\ndescription: A relentless interview to sharpen a plan or design, creating CONTEXT.md (shared language) and ADRs (architectural decisions) as we go. Use before any non-trivial implementation to align on requirements and terminology.\nversion: 1.0.0\nuser-invocable: true\nallowed-tools:\n  - Read\n  - Write\n  - Edit\n  - Bash\n  - Glob\n  - Grep\n  - WebSearch\n  - WebFetch\n---\n\n# Grill With Docs — Deep Requirements Alignment\n\nInspired by Matt Pocock's `grill-with-docs` and `domain-modeling` skills. Before writing code, run a structured interview to align on requirements, establish shared language, and record architectural decisions.\n\n## When to Use\n\n- Before any non-trivial feature implementation\n- When requirements are fuzzy (\"make it faster\", \"add X\")\n- When you need to establish project terminology\n- When architectural decisions need to be recorded\n- User says: \"plan X\", \"design Y\", \"what should we do about Z\"\n\n## When NOT to Use\n\n- Trivial bug fixes with clear expected behavior\n- One-line changes\n- Tasks where the requirements are already crystal clear\n\n---\n\n## The Interview Flow\n\n### Phase 1: Understand the Intent\n\nStart by understanding what the user actually wants. Don't ask \"what should I build?\" — ask about their goal.\n\n**Core Questions:**\n\n1. What problem are you solving? (Not what feature you're building)\n2. Who is this for? (End user, developer, internal tool?)\n3. What does success look like? (How will you know when it's done?)\n4. What's the deadline or priority context?\n\n**Anti-pattern**: Jumping to implementation questions (\"Do you want REST or GraphQL?\") before understanding the problem.\n\n### Phase 2: Sharpen the Language\n\nIdentify vague or overloaded terms and pin them down **immediately**. This is the single highest-leverage activity — shared language reduces token waste and prevents misunderstandings.\n\n**Technique: The Canonical Term**\n\n- When the user uses multiple words for the same thing, pick one as canonical\n- List rejected alternatives under `_Avoid_`\n- Be opinionated — the glossary is prescriptive, not descriptive\n\n```\nUser: \"We need a way for users to save articles for later.\"\nYou: \"Let's pin that down. 'Save for later' could mean bookmarking, or a reading list, or offline download. Which one?\"\nUser: \"Like a reading list — they can come back to it.\"\nYou: \"Got it. Let's call it a **Reading List**. Avoid 'bookmark', 'save', 'favorites'.\"\n→ Write to CONTEXT.md immediately.\n```\n\n**Technique: The Boundary Test**\n\n- When a term is proposed, test its boundaries with edge cases\n- \"Does X include Y? What about Z?\"\n\n**Technique: The Code Cross-Reference**\n\n- When the user describes how something works, check if existing code agrees\n- Surface contradictions immediately\n\n### Phase 3: Probe Edge Cases\n\nBefore accepting any requirement, stress-test it with edge cases.\n\n**Edge Case Inventory:**\n\n- **Empty state**: What does the user see when there's nothing yet?\n- **Error state**: What happens when things go wrong?\n- **Extreme values**: What about 0? What about 10,000?\n- **Concurrency**: What if two people do this at the same time?\n- **Permissions**: Who can do this? Who cannot?\n- **Scale**: What changes at 10x the current volume?\n\n**Technique: The 5 Whys**\nWhen a requirement seems odd, dig deeper:\n\n```\nUser: \"We need real-time updates.\"\nYou: \"Why real-time?\"\nUser: \"Because users need to see changes immediately.\"\nYou: \"Why do they need to see changes immediately?\"\nUser: \"Because they're collaborating on the same document.\"\n→ Now you know the REAL requirement is collaboration, not real-time.\n```\n\n### Phase 4: Make Architecture Decisions\n\nWhen a design decision meets ALL three criteria, offer to record it as an ADR:\n\n1. **Hard to reverse** — changing your mind later has real cost\n2. **Surprising without context** — a future reader would wonder \"why?\"\n3. **The result of a real trade-off** — there were genuine alternatives\n\n**What qualifies for an ADR:**\n\n- Architecture shape (monorepo vs polyrepo, event sourcing vs CRUD)\n- Integration patterns between contexts\n- Technology choices with lock-in (database, message bus, auth provider)\n- Deliberate deviations from convention (\"we use raw SQL because...\")\n- Constraints not visible in code (\"we can't use X because compliance\")\n\n**ADR Format** (write to `docs/adr/NNNN-slug.md`):\n\n```markdown\n# {Short title of the decision}\n\n{1-3 sentences: context, decision, and why.}\n```\n\nOnly add optional sections (Status, Considered Options, Consequences) when they add genuine value. Most ADRs are a single paragraph.\n\n### Phase 5: Write the CONTEXT.md\n\nAfter the interview, synthesize everything into `CONTEXT.md`.\n\n**Format** (`CONTEXT.md` at project root):\n\n```markdown\n# {Project Name} Context\n\n{One or two sentence description of the project domain.}\n\n## Language\n\n**{Term}**:\n{One or two sentence definition of what it IS.}\n_Avoid_: {alternative terms that should not be used}\n\n## Decisions\n\n- [ADR 0001: {Title}](docs/adr/0001-slug.md) — {one-line summary}\n```\n\n**Rules:**\n\n- Be opinionated — pick the best term, ban the rest\n- Only include domain-specific terms (not general programming concepts)\n- Keep definitions tight — one or two sentences\n- Update inline during the conversation, don't batch\n- CONTEXT.md is a glossary, NOT a spec or implementation plan\n\n---\n\n## During the Conversation\n\n### DO\n\n- Challenge the user when they use vague terms — \"What do you mean by 'fast'?\"\n- Propose canonical terms and write them down immediately\n- Invent edge cases and probe boundaries\n- Offer ADRs sparingly (only when all 3 criteria are met)\n- Cross-reference with existing code if available\n- Call out contradictions between what the user says and what the code does\n\n### DON'T\n\n- Rush to implementation questions before understanding the problem\n- Write ADRs for trivial decisions\n- Let fuzzy language slide — pin it down now or pay later\n- Treat CONTEXT.md as a spec or scratch pad\n- Ask yes/no questions when open-ended ones would reveal more\n\n---\n\n## Output\n\nAfter the interview, the user should have:\n\n1. **CONTEXT.md** — shared language glossary (created or updated)\n2. **ADRs** (if needed) — architectural decisions in `docs/adr/`\n3. **Clear requirements** — edge cases explored, assumptions surfaced\n4. **Shared understanding** — you and the user now mean the same thing by the same words\n\n---\n\n## Integration with Mipham Code\n\n- **Memory System**: Key terms go to project memory for persistence across sessions\n- **Critical Thinking Layer**: Apply the 5-dimension self-check (evidence standard, equivalence verification, counter-example search, confidence calibration, depth check) to your own interview questions\n- **Workflow**: For complex projects, the output of this skill feeds directly into `/implement`\n" },
   { type: 'standard', raw: "---\nname: implement\ndescription: Build work from a spec or tickets with systematic discipline — TDD at pre-agreed seams, incremental verification, code review before commit. Use when implementing features, bugfixes, or any planned work.\nversion: 1.0.0\nuser-invocable: true\n---\n\n# Implement — Structured Build Execution\n\n融合 Superpowers executing-plans（计划审阅 + 隔离工作区）+ Matt Pocock implement（TDD 接缝 + 增量验证 + 提交前审查）。\n\n## When to Use\n\n- Implementing work from a written spec or ticket set\n- Executing a development plan with clear deliverables\n- Building a feature with predefined success criteria\n\n## When NOT to Use\n\n- Exploratory coding / prototyping → use `prototype` skill\n- Quick one-line fixes → just fix it\n- No spec or tickets exist → use `to-tickets` or `to-spec` first\n\n---\n\n## Step 1: Load and Review\n\n### 1.1 Ensure isolated workspace\n\nUse git worktree or a feature branch. Never implement on main/master without explicit consent.\n\n### 1.2 Read the plan/spec/tickets\n\nRead the full spec or ticket set. Understand:\n\n- What is being built?\n- What are the acceptance criteria?\n- What are the pre-agreed seams (where TDD should be applied)?\n\n### 1.3 Review critically\n\nBefore writing any code:\n\n- Are there gaps or ambiguities in the spec?\n- Are the success criteria testable?\n- Do you understand every instruction?\n\n**If concerns exist, raise them before starting.** Don't guess.\n\n---\n\n## Step 2: Execute Tasks\n\nFor each task in order:\n\n### 2.1 At pre-agreed seams: TDD\n\nWhere the spec specifies (or where interfaces are well-defined):\n\n1. Write a **failing test** that asserts the expected behavior\n2. Watch it fail (red)\n3. Write the **minimum code** to make it pass (green)\n4. Refactor if needed, keeping tests green\n\nUse the `tdd` skill for full red-green-refactor discipline.\n\n### 2.2 Incremental verification\n\nDuring implementation:\n\n- **Run typecheck** after each significant change: `pnpm typecheck`\n- **Run relevant test file** after each task: `pnpm test -- <file>`\n- **Don't wait** until everything is done to discover type errors\n\n### 2.3 One task at a time\n\n- Follow each step exactly — the plan has bite-sized steps for a reason\n- One change at a time. No \"while I'm here\" improvements.\n- Mark tasks as complete after verification passes\n\n---\n\n## Step 3: Final Verification\n\nAfter all tasks are complete:\n\n### 3.1 Full test suite\n\n```bash\npnpm test\n```\n\nAll tests must pass. If any fail, fix before proceeding.\n\n### 3.2 Lint and format\n\n```bash\npnpm lint\npnpm format\n```\n\nCI must be green.\n\n---\n\n## Step 4: Code Review\n\n**Before committing**, run code review:\n\nUse the `code-review` skill for a two-axis review:\n\n- **Standards**: Does the diff follow the repo's coding standards?\n- **Spec**: Does it faithfully implement the originating issue/spec?\n\nFix any findings before committing.\n\n---\n\n## Step 5: Commit\n\nCommit your work to the current branch.\n\n```bash\ngit add -A\ngit commit -m \"<type>: <description>\"\n```\n\n- Follow Conventional Commits\n- Reference the spec/ticket in the commit message\n- **Do NOT commit unless explicitly asked** (per CLAUDE.md §关键约束)\n\n---\n\n## When to Stop and Ask\n\n**STOP immediately when:**\n\n- A task is blocked (missing dependency, unclear instruction, verification fails repeatedly)\n- The spec has a critical gap that prevents starting\n- You don't understand an instruction\n- 3+ fix attempts fail — this may be an architectural issue\n\n**Ask for clarification rather than guessing.**\n\n---\n\n## Quick Reference\n\n| Step           | Key Activities                                               | Done When                        |\n| -------------- | ------------------------------------------------------------ | -------------------------------- |\n| **1. Review**  | Load spec, isolate workspace, review critically              | All concerns raised and resolved |\n| **2. Execute** | TDD at seams, incremental typecheck/test, one task at a time | All tasks complete and verified  |\n| **3. Verify**  | Full test suite, lint, format                                | CI-ready (all green)             |\n| **4. Review**  | Two-axis code review (standards + spec)                      | Findings addressed               |\n| **5. Commit**  | Conventional Commits, reference spec/ticket                  | Work committed to branch         |\n" },
   { type: 'standard', raw: "---\nname: memory\ndescription: Read and write persistent memory files for context retention across sessions — one fact per file with frontmatter\nversion: 2.0.0\n---\n\n# Memory Skill\n\nManage persistent memory stored as markdown files with YAML frontmatter.\n\n## File Format\n\nEach memory is one `.md` file under the `memory/` directory:\n\n```markdown\n---\nname: <kebab-case-slug>\ndescription: <one-line summary>\nmetadata:\n  type: user | feedback | project | reference\n---\n\n<the fact body>\n\n**Why:** <rationale>\n**How to apply:** <practical guidance>\n```\n\n## File Path Conventions\n\n- Directory: `~/.mipham/memory/` (user-level) or `./.mipham/memory/` (project-level)\n- Filename: `<name-slug>.md` (lowercase, hyphens)\n- Index: `MEMORY.md` — one line per memory file, maintained automatically\n\n## Operations\n\n### List Memories\n\nScan `MEMORY.md` index for available memories. The index has one line per memory:\n\n```markdown\n- [Title](file.md) — brief hook\n```\n\n### Read Memory\n\nRead the full markdown file including frontmatter. Parse YAML frontmatter for metadata.\n\n### Write Memory\n\n1. Check for existing file with same `name:` slug — update if found\n2. Create new file if no match\n3. Add/update entry in `MEMORY.md` index\n4. Never write what the repo already records (code structure, git history, CLAUDE.md)\n\n### Delete Memory\n\nRemove the file and its index entry. Use when a memory is incorrect or superseded.\n\n## Best Practices\n\n- **One fact per file** — atomic, focused, easy to find\n- **Descriptive slugs** — `npm-publish-workflow` not `memory-1`\n- **Link related memories** — use `[[slug-name]]` wikilinks in body\n- **Check before writing** — search existing memories to avoid duplicates\n- **Types matter**: `user` (who), `feedback` (corrections), `project` (goals), `reference` (external)\n\n## Example\n\n```markdown\n---\nname: api-rate-limit\ndescription: OpenAI API has 500 RPM limit on our tier\nmetadata:\n  type: reference\n---\n\nThe OpenAI API key for production has a hard 500 requests/minute limit.\nExceeding it returns HTTP 429 with a Retry-After header.\n\n**Why:** We hit this in production during peak usage\n**How to apply:** Use exponential backoff; batch requests where possible\n```\n" },
-  { type: 'standard', raw: "---\nname: mipham-code-setup\ndescription: Install, configure, diagnose, and troubleshoot Mipham Code — the multi-model open-core intelligent coding terminal. Covers setup wizard, API keys, providers, models, skills, permissions, workspace trust, shell/IDE integration, and first-run onboarding.\nversion: 2.0.0\nuser-invocable: true\nallowed-tools:\n  - Read\n  - Write\n  - Edit\n  - Bash\n  - Skill\n---\n\n# Mipham Code Setup — Executable Setup Workflow\n\n**Type**: Rigid — follow the decision tree exactly. Don't skip diagnostic phases.\n\n**Purpose**: Guide users from zero to fully configured Mipham Code. This skill is BOTH:\n\n1. A self-contained diagnostic + configuration workflow the AI can execute\n2. A reference for `/setup` command behavior and slash commands\n\n**Triggers**: \"setup mipham\", \"configure mipham\", \"install mipham code\", \"mipham not working\", \"mipham setup\", \"first time using mipham\", \"help me set up\", \"getting started\", `/setup`\n\n---\n\n## Phase 0: Environment Detection (ALWAYS RUN FIRST)\n\nBefore doing anything, run these diagnostic checks. Report results in a status table.\n\n### 0.1 — Detect Installation\n\n```bash\nwhich mipham 2>/dev/null\nmipham --version 2>/dev/null\nbun --version 2>/dev/null\nnode --version 2>/dev/null\n```\n\n### 0.2 — Detect Configuration\n\n```bash\nls -la .mipham/config.yml 2>/dev/null\nls -la ~/.mipham/config.yml 2>/dev/null\nls -la MIPHAM.md 2>/dev/null\nls -la CLAUDE.md 2>/dev/null\n```\n\n### 0.3 — Detect API Keys\n\n```bash\nenv | grep -E 'ANTHROPIC_API_KEY|OPENAI_API_KEY|DEEPSEEK_API_KEY|QWEN_API_KEY|DOUBAO_API_KEY|HUNYUAN_API_KEY|GEMINI_API_KEY' | cut -d= -f1\n```\n\n### 0.4 — Detect Skills & Permissions\n\n```bash\nls .mipham/skills/ 2>/dev/null\ncat .mipham/config.yml 2>/dev/null | grep -E 'permission|trust' || echo \"no config\"\n```\n\n### 0.5 — Detect Workspace Trust\n\n```bash\ncat ~/.mipham/trusted-workspaces.json 2>/dev/null || echo \"no trust store\"\n```\n\n### Status Report Format\n\nAfter detection, present results as:\n\n```\n── Mipham Code Status ──\n\nInstallation:  [✅/⬜] mipham CLI  [✅/⬜] Bun  [✅/⬜] Node.js\nProject:       [✅/⬜] .mipham/  [✅/⬜] config.yml  [✅/⬜] MIPHAM.md\nUser Config:   [✅/⬜] ~/.mipham/config.yml\nAPI Keys:      [N] set (list names or \"none\")\nSkills:        [N] installed\nPermissions:   [mode] (default/acceptEdits/plan/auto/dontAsk/bypass)\nTrust:         [✅/⬜] workspace trusted\n```\n\nThen proceed to ONLY the phases where something is missing. Don't re-run already-configured steps unless asked.\n\n---\n\n## Phase 1: Installation\n\n**Trigger**: `mipham --version` fails.\n\n### Option A: Quick Install (recommended)\n\n```bash\ncurl -fsSL https://mipham.ai/install.sh | bash\n```\n\nThen restart the shell or run:\n\n```bash\nexport PATH=\"$HOME/.mipham/bin:$PATH\"\n```\n\n### Option B: npm Global Install\n\n```bash\nnpm install -g @miphamai/cli\nmipham\n```\n\n### Option C: From Source (developers)\n\n```bash\ngit clone https://github.com/One-Mipham/mipham-code\ncd mipham-code/apps/cli\nbun install && bun run bin/mipham\n```\n\n### ✅ Verification\n\n```bash\nmipham --version   # Should print version ≥ 0.24.0\nmipham --help      # Should print usage\n```\n\n---\n\n## Phase 2: Project Initialization\n\n**Trigger**: Missing `.mipham/` directory or `MIPHAM.md`.\n\n### 2.1 — Create .mipham/ directory\n\n```bash\nmkdir -p .mipham\n```\n\n### 2.2 — Create .mipham/config.yml\n\nWrite a minimal config. Ask the user which provider they want to use first, or pick a sensible default:\n\n```yaml\ndefaultProvider: anthropic\ndefaultModel: claude-sonnet-4-6\npermission: default\n```\n\n**Providers available** (alphabetical):\n\n| Provider  | Type          | Example Models                         |\n| --------- | ------------- | -------------------------------------- |\n| anthropic | Native SDK    | Claude Haiku 4.5, Sonnet 4.6, Opus 4.8 |\n| deepseek  | OpenAI Compat | V4 Flash, V4 Pro                       |\n| doubao    | OpenAI Compat | Seed 1.6, Seed 2.0                     |\n| gemini    | OpenAI Compat | 3.0 Flash, 3.0 Pro, 2.5 Pro            |\n| hunyuan   | OpenAI Compat | Lite, TurboS, 2.0, T1                  |\n| openai    | OpenAI Compat | GPT-5.4 Mini, GPT-5.4, GPT-5.5, Codex  |\n| qwen      | OpenAI Compat | Qwen Plus, Qwen Max                    |\n\n### 2.3 — Create MIPHAM.md (optional but recommended)\n\nCreate `MIPHAM.md` in project root to define AI personality:\n\n```markdown\n# MIPHAM.md\n\n## Project Context\n\n- **Project**: [name]\n- **Language**: [zh-CN / en]\n- **Stack**: [TypeScript / Python / etc.]\n\n## Preferences\n\n- Code style: [e.g., functional, OOP]\n- Comment language: [e.g., English]\n- Test framework: [e.g., Vitest]\n```\n\n### ✅ Verification\n\n```bash\nls -la .mipham/config.yml MIPHAM.md\n```\n\n---\n\n## Phase 3: API Key Configuration\n\n**Trigger**: Missing API keys in environment.\n\n### 3.1 — Identify Required Providers\n\nAsk the user which providers they plan to use. For each, set the env var.\n\n### 3.2 — Set API Keys\n\n**Recommended: Environment variables** (not in config files — avoids accidental commits):\n\n```bash\nexport ANTHROPIC_API_KEY=\"sk-ant-...\"\nexport OPENAI_API_KEY=\"sk-...\"\nexport DEEPSEEK_API_KEY=\"sk-...\"\nexport QWEN_API_KEY=\"sk-...\"\nexport DOUBAO_API_KEY=\"...\"\nexport HUNYUAN_API_KEY=\"...\"\nexport GEMINI_API_KEY=\"...\"\n```\n\nAdd these to `~/.zshrc` or `~/.bashrc` for persistence:\n\n```bash\necho 'export ANTHROPIC_API_KEY=\"sk-ant-...\"' >> ~/.zshrc\nsource ~/.zshrc\n```\n\n**Alternative**: Store in `~/.mipham/config.yml`:\n\n```yaml\nproviders:\n  - id: anthropic\n    apiKey: $ANTHROPIC_API_KEY\n  - id: openai\n    apiKey: $OPENAI_API_KEY\n```\n\n### 3.3 — Verify Keys\n\n```bash\nenv | grep API_KEY\n```\n\n### ❗Security Rules\n\n- NEVER hardcode API keys in project config files (`.mipham/config.yml` in project root should use `$ENV_VAR` references, not raw keys)\n- NEVER commit API keys to git\n- Add to `.gitignore`: `.mipham/config.yml` (if it contains keys), `.env`, `*.pem`\n\n---\n\n## Phase 4: Provider & Model Configuration\n\n**Trigger**: Need to set default or enable/disable providers.\n\n### 4.1 — Set Default Provider & Model\n\nIn `.mipham/config.yml`:\n\n```yaml\ndefaultProvider: anthropic\ndefaultModel: claude-sonnet-4-6\n```\n\nOr use slash commands:\n\n```\n/model          # Interactive model picker (Ctrl+P)\n/switch         # Switch provider\n/providers      # List all configured providers\n```\n\n### 4.2 — Enable/Disable Providers\n\n```yaml\nproviders:\n  - id: anthropic\n    status: active\n  - id: openai\n    status: active\n  - id: deepseek\n    status: disabled\n```\n\n### ✅ Verification\n\n```\n/model    # Should show available models\n/providers # Should list active providers\n```\n\n---\n\n## Phase 5: Skills Installation\n\n**Trigger**: No or few skills installed.\n\n### 5.1 — Built-in Skills\n\nMipham Code ships with 17 built-in skills loaded automatically:\n\n- **Standard (14)**: code-review, compassionate-communication, doc-generator, github-ops, memory, mipham-code-setup, security-review, self-review, superpower, systematic-debugging, tdd, test-driven-development, web-access, web-search\n- **Mipham (3)**: om-artifact, om-model-optimize, om-security\n\n### 5.2 — Community Skills\n\nInstall from the community registry:\n\n```\n/setup 4     # Guided skill browser\n```\n\nOr directly:\n\n```bash\n# Skills are loaded from:\n# - apps/cli/skills/standard/     (built-in standard)\n# - apps/cli/skills/mipham/       (built-in mipham)\n# - ~/.mipham/skills/             (user-installed)\n# - .mipham/skills/               (project-local)\n```\n\n### 5.3 — Install Specific Skills\n\n```\n/skills install <name>    # Install from registry\n/skills list              # List available\n/skills search <query>    # Search registry\n```\n\n### ✅ Verification\n\n```\n/skills list   # Should show installed skills with counts\n```\n\n---\n\n## Phase 6: Permissions Configuration\n\n**Trigger**: Permission mode not configured or wrong for use case.\n\n### 6.1 — Permission Modes\n\n| Mode                | Behavior                        | Use Case                            |\n| ------------------- | ------------------------------- | ----------------------------------- |\n| `default`           | Prompt for each tool            | Normal development (recommended)    |\n| `acceptEdits`       | Auto-allow edits, prompt others | Active coding sessions              |\n| `plan`              | Plan-only, no tool execution    | Design & architecture work          |\n| `auto`              | Auto-allow all                  | Trusted, frequent use               |\n| `dontAsk`           | Never auto-allow                | CI/CD safety                        |\n| `bypassPermissions` | Skip all checks                 | ⚠️ Only for fully trusted codebases |\n\n### 6.2 — Configure\n\nIn `.mipham/config.yml`:\n\n```yaml\npermission: auto\n```\n\nOr via slash command:\n\n```\n/permissions           # View current settings\n/setup 5               # Permission setup wizard\n```\n\n### 6.3 — CI/CD Safety\n\nFor CI/CD environments, use `dontAsk` mode to prevent the AI from executing tools without explicit approval:\n\n```yaml\npermission: dontAsk\n```\n\n### ✅ Verification\n\n```\n/permissions   # Should show current mode\n```\n\n---\n\n## Phase 7: Workspace Trust\n\n**Trigger**: Untrusted workspace (prompted on startup in v0.24.3+).\n\n### 7.1 — Understanding Workspace Trust\n\nWorkspace trust is a security mechanism that prevents AI from operating in untrusted directories. Trust is **hierarchical**: trusting `/Users/me/Projects` implicitly trusts all subdirectories.\n\n### 7.2 — Trust a Workspace\n\n**Interactive**: Accept the trust prompt when launching Mipham Code in a new directory.\n\n**Manual**:\n\n```\n/trust              # Show trust status\n/trust add <dir>    # Trust a directory\n/trust remove <dir> # Revoke trust\n```\n\n### 7.3 — Trust Store\n\n```\n~/.mipham/trusted-workspaces.json\n```\n\n### 7.4 — Auto-Trust for Worktrees\n\nWhen using git worktrees, Mipham Code automatically trusts worktree directories if the parent workspace is already trusted (via `EnterWorktree`).\n\n### ✅ Verification\n\n```\n/trust   # Should show \"✅ Yes\" for current directory\n```\n\n---\n\n## Phase 8: Shell & IDE Integration\n\n**Trigger**: Want terminal integration, aliases, or IDE plugins.\n\n### 8.1 — Shell Alias\n\nAdd to `~/.zshrc` or `~/.bashrc`:\n\n```bash\nalias mipham='cd ~/your-project && bun run ~/path/to/mipham-code/apps/cli/bin/mipham.ts'\n# Or if installed globally:\nalias mipham='mipham'\n```\n\n### 8.2 — VS Code Integration\n\nRun `/ide` to auto-generate `.vscode/` config files:\n\n- `settings.json` — terminal profile \"mipham\" using Bun\n- `keybindings.json` — Cmd+Esc to focus terminal, Cmd+Shift+M for new terminal\n- `extensions.json` — recommends `miphamai.mipham-code` extension\n\nTo use after generation:\n\n1. Restart VS Code (or Cmd+Shift+P → Reload Window)\n2. Open terminal: Ctrl+` or Cmd+Esc\n3. Select \"mipham\" profile from terminal dropdown\n\nInstall the VS Code extension:\n\n```bash\ncode --install-extension miphamai.mipham-code\n```\n\n### 8.3 — JetBrains Integration\n\nSettings → Tools → Terminal → Shell path → `bun run mipham`\n\n### 8.4 — Terminal Setup\n\n```\n/terminal-setup    # Shell & terminal config wizard\n/setup 6           # Shell integration (part of full wizard)\n```\n\n### ✅ Verification\n\n```bash\nwhich mipham       # Should resolve\n# In VS Code: Ctrl+` → select \"mipham\" profile\n```\n\n---\n\n## Phase 9: Full Verification\n\nRun after all configuration phases complete.\n\n### 9.1 — System Diagnostics\n\n```\n/doctor            # System diagnostics check\n```\n\n### 9.2 — End-to-End Test\n\nStart a conversation and verify:\n\n1. Model responds (not stuck on \"connecting...\")\n2. File tools work: \"read CLAUDE.md\"\n3. Bash works: \"list files in current directory\"\n4. Skills load: `/skills list`\n\n### 9.3 — Common Issues & Fixes\n\n| Symptom                   | Diagnosis                              | Fix                                              |\n| ------------------------- | -------------------------------------- | ------------------------------------------------ |\n| \"Provider not registered\" | Missing or invalid API key             | `env \\| grep API_KEY`; check key format          |\n| \"Model not found\"         | Model ID mismatch or disabled provider | `/models` to list available; `/switch` to change |\n| Slow responses            | Large model, network, or context full  | `/fast on` or switch to Flash model; `/compact`  |\n| Context full              | Too many messages in history           | `/compact` to compress; `/clear` to reset        |\n| Permission denied         | Tool blocked by permission mode        | `/permissions` to check; adjust mode             |\n| \"Workspace not trusted\"   | New directory, not yet trusted         | Accept startup prompt or run `/trust`            |\n| MCP tools not available   | Server not connected                   | `/mcp connect <name>` or check config            |\n| Update not applying       | Cached binary                          | `mipham update --force` then restart             |\n| Config changes ignored    | YAML syntax error                      | Validate with `mipham --check-config`            |\n\n### 9.4 — Get Help\n\n```\n/help              # Full command reference\n/setup             # Re-run setup wizard\n/doctor            # Run diagnostics\n```\n\nChat-based help: \"help me configure X\" or \"why isn't Y working?\"\n\n---\n\n## Quick Reference: Essential Slash Commands\n\n| Category      | Command           | Purpose                                                |\n| ------------- | ----------------- | ------------------------------------------------------ |\n| **Setup**     | `/setup`          | Full 6-step setup wizard                               |\n|               | `/setup 1`        | Initialize project (.mipham/ + MIPHAM.md + config.yml) |\n|               | `/setup 2`        | Configure providers & API keys                         |\n|               | `/setup 3`        | Choose default model                                   |\n|               | `/setup 4`        | Browse & install skills                                |\n|               | `/setup 5`        | Configure permissions                                  |\n|               | `/setup 6`        | Shell & IDE integration                                |\n| **Diagnosis** | `/doctor`         | System diagnostics                                     |\n|               | `/trust`          | Workspace trust status                                 |\n|               | `/permissions`    | Tool permission settings                               |\n| **Model**     | `/model`          | Interactive model picker (Ctrl+P)                      |\n|               | `/switch`         | Switch provider                                        |\n|               | `/models`         | List available models                                  |\n| **Session**   | `/clear`          | Reset conversation                                     |\n|               | `/compact`        | Compress context                                       |\n|               | `/rename`         | Rename session                                         |\n| **Workflow**  | `/plan`           | Enter plan mode                                        |\n|               | `/review`         | Code review                                            |\n|               | `/todos`          | Task list                                              |\n| **IDE**       | `/ide`            | Generate VS Code integration files                     |\n|               | `/terminal-setup` | Shell & terminal config                                |\n| **Skills**    | `/skills list`    | List installed skills                                  |\n|               | `/skills search`  | Search skill registry                                  |\n|               | `/skills install` | Install a skill                                        |\n\n---\n\n## Post-Setup: What to Do Next\n\nAfter configuration is verified:\n\n1. **Initialize your project**: \"help me understand this codebase\"\n2. **Set up CLAUDE.md**: `/init` to generate project documentation for the AI\n3. **Install relevant skills**: `/setup 4` or `/skills search`\n4. **Configure MCP servers**: `/mcp connect` for external tool integration\n5. **Start coding**: Just start a conversation — the AI will use tools and skills automatically\n" },
+  { type: 'standard', raw: "---\nname: mipham-code-setup\ndescription: Install, configure, diagnose, and troubleshoot Mipham Code — the multi-model open-core intelligent coding terminal. Covers setup wizard, API keys, providers, models, skills, permissions, workspace trust, shell/IDE integration, and first-run onboarding.\nversion: 2.0.0\nuser-invocable: true\nallowed-tools:\n  - Read\n  - Write\n  - Edit\n  - Bash\n  - Skill\n---\n\n# Mipham Code Setup — Executable Setup Workflow\n\n**Type**: Rigid — follow the decision tree exactly. Don't skip diagnostic phases.\n\n**Purpose**: Guide users from zero to fully configured Mipham Code. This skill is BOTH:\n\n1. A self-contained diagnostic + configuration workflow the AI can execute\n2. A reference for `/setup` command behavior and slash commands\n\n**Triggers**: \"setup mipham\", \"configure mipham\", \"install mipham code\", \"mipham not working\", \"mipham setup\", \"first time using mipham\", \"help me set up\", \"getting started\", `/setup`\n\n---\n\n## Phase 0: Environment Detection (ALWAYS RUN FIRST)\n\nBefore doing anything, run these diagnostic checks. Report results in a status table.\n\n### 0.1 — Detect Installation\n\n```bash\nwhich mipham 2>/dev/null\nmipham --version 2>/dev/null\nbun --version 2>/dev/null\nnode --version 2>/dev/null\n```\n\n### 0.2 — Detect Configuration\n\n```bash\nls -la .mipham/config.yml 2>/dev/null\nls -la ~/.mipham/config.yml 2>/dev/null\nls -la MIPHAM.md 2>/dev/null\nls -la CLAUDE.md 2>/dev/null\n```\n\n### 0.3 — Detect API Keys\n\n```bash\nenv | grep -E 'ANTHROPIC_API_KEY|OPENAI_API_KEY|DEEPSEEK_API_KEY|QWEN_API_KEY|DOUBAO_API_KEY|HUNYUAN_API_KEY|GEMINI_API_KEY' | cut -d= -f1\n```\n\n### 0.4 — Detect Skills & Permissions\n\n```bash\nls .mipham/skills/ 2>/dev/null\ncat .mipham/config.yml 2>/dev/null | grep -E 'permission|trust' || echo \"no config\"\n```\n\n### 0.5 — Detect Workspace Trust\n\n```bash\ncat ~/.mipham/trusted-workspaces.json 2>/dev/null || echo \"no trust store\"\n```\n\n### Status Report Format\n\nAfter detection, present results as:\n\n```\n── Mipham Code Status ──\n\nInstallation:  [✅/⬜] mipham CLI  [✅/⬜] Bun  [✅/⬜] Node.js\nProject:       [✅/⬜] .mipham/  [✅/⬜] config.yml  [✅/⬜] MIPHAM.md\nUser Config:   [✅/⬜] ~/.mipham/config.yml\nAPI Keys:      [N] set (list names or \"none\")\nSkills:        [N] installed\nPermissions:   [mode] (default/acceptEdits/plan/bypassPermissions)\nTrust:         [✅/⬜] workspace trusted\n```\n\nThen proceed to ONLY the phases where something is missing. Don't re-run already-configured steps unless asked.\n\n---\n\n## Phase 1: Installation\n\n**Trigger**: `mipham --version` fails.\n\n### Option A: Quick Install (recommended)\n\n```bash\ncurl -fsSL https://mipham.ai/install.sh | bash\n```\n\nThen restart the shell or run:\n\n```bash\nexport PATH=\"$HOME/.mipham/bin:$PATH\"\n```\n\n### Option B: npm Global Install\n\n```bash\nnpm install -g @miphamai/cli\nmipham\n```\n\n### Option C: From Source (developers)\n\n```bash\ngit clone https://github.com/One-Mipham/mipham-code\ncd mipham-code/apps/cli\nbun install && bun run bin/mipham\n```\n\n### ✅ Verification\n\n```bash\nmipham --version   # Should print version ≥ 0.24.0\nmipham --help      # Should print usage\n```\n\n---\n\n## Phase 2: Project Initialization\n\n**Trigger**: Missing `.mipham/` directory or `MIPHAM.md`.\n\n### 2.1 — Create .mipham/ directory\n\n```bash\nmkdir -p .mipham\n```\n\n### 2.2 — Create .mipham/config.yml\n\nWrite a minimal config. Ask the user which provider they want to use first, or pick a sensible default:\n\n```yaml\ndefaultProvider: anthropic\ndefaultModel: claude-sonnet-4-6\npermission: default\n```\n\n**Providers available** (alphabetical):\n\n| Provider  | Type          | Example Models                         |\n| --------- | ------------- | -------------------------------------- |\n| anthropic | Native SDK    | Claude Haiku 4.5, Sonnet 4.6, Opus 4.8 |\n| deepseek  | OpenAI Compat | V4 Flash, V4 Pro                       |\n| doubao    | OpenAI Compat | Seed 1.6, Seed 2.0                     |\n| gemini    | OpenAI Compat | 3.0 Flash, 3.0 Pro, 2.5 Pro            |\n| hunyuan   | OpenAI Compat | Lite, TurboS, 2.0, T1                  |\n| openai    | OpenAI Compat | GPT-5.4 Mini, GPT-5.4, GPT-5.5, Codex  |\n| qwen      | OpenAI Compat | Qwen Plus, Qwen Max                    |\n\n### 2.3 — Create MIPHAM.md (optional but recommended)\n\nCreate `MIPHAM.md` in project root to define AI personality:\n\n```markdown\n# MIPHAM.md\n\n## Project Context\n\n- **Project**: [name]\n- **Language**: [zh-CN / en]\n- **Stack**: [TypeScript / Python / etc.]\n\n## Preferences\n\n- Code style: [e.g., functional, OOP]\n- Comment language: [e.g., English]\n- Test framework: [e.g., Vitest]\n```\n\n### ✅ Verification\n\n```bash\nls -la .mipham/config.yml MIPHAM.md\n```\n\n---\n\n## Phase 3: API Key Configuration\n\n**Trigger**: Missing API keys in environment.\n\n### 3.1 — Identify Required Providers\n\nAsk the user which providers they plan to use. For each, set the env var.\n\n### 3.2 — Set API Keys\n\n**Recommended: Environment variables** (not in config files — avoids accidental commits):\n\n```bash\nexport ANTHROPIC_API_KEY=\"sk-ant-...\"\nexport OPENAI_API_KEY=\"sk-...\"\nexport DEEPSEEK_API_KEY=\"sk-...\"\nexport QWEN_API_KEY=\"sk-...\"\nexport DOUBAO_API_KEY=\"...\"\nexport HUNYUAN_API_KEY=\"...\"\nexport GEMINI_API_KEY=\"...\"\n```\n\nAdd these to `~/.zshrc` or `~/.bashrc` for persistence:\n\n```bash\necho 'export ANTHROPIC_API_KEY=\"sk-ant-...\"' >> ~/.zshrc\nsource ~/.zshrc\n```\n\n**Alternative**: Store in `~/.mipham/config.yml`:\n\n```yaml\nproviders:\n  - id: anthropic\n    apiKey: $ANTHROPIC_API_KEY\n  - id: openai\n    apiKey: $OPENAI_API_KEY\n```\n\n### 3.3 — Verify Keys\n\n```bash\nenv | grep API_KEY\n```\n\n### ❗Security Rules\n\n- NEVER hardcode API keys in project config files (`.mipham/config.yml` in project root should use `$ENV_VAR` references, not raw keys)\n- NEVER commit API keys to git\n- Add to `.gitignore`: `.mipham/config.yml` (if it contains keys), `.env`, `*.pem`\n\n---\n\n## Phase 4: Provider & Model Configuration\n\n**Trigger**: Need to set default or enable/disable providers.\n\n### 4.1 — Set Default Provider & Model\n\nIn `.mipham/config.yml`:\n\n```yaml\ndefaultProvider: anthropic\ndefaultModel: claude-sonnet-4-6\n```\n\nOr use slash commands:\n\n```\n/model          # Interactive model picker (Ctrl+P)\n/switch         # Switch provider\n/providers      # List all configured providers\n```\n\n### 4.2 — Enable/Disable Providers\n\n```yaml\nproviders:\n  - id: anthropic\n    status: active\n  - id: openai\n    status: active\n  - id: deepseek\n    status: disabled\n```\n\n### ✅ Verification\n\n```\n/model    # Should show available models\n/providers # Should list active providers\n```\n\n---\n\n## Phase 5: Skills Installation\n\n**Trigger**: No or few skills installed.\n\n### 5.1 — Built-in Skills\n\nMipham Code ships with 17 built-in skills loaded automatically:\n\n- **Standard (14)**: code-review, compassionate-communication, doc-generator, github-ops, memory, mipham-code-setup, security-review, self-review, superpower, systematic-debugging, tdd, test-driven-development, web-access, web-search\n- **Mipham (3)**: om-artifact, om-model-optimize, om-security\n\n### 5.2 — Community Skills\n\nInstall from the community registry:\n\n```\n/setup 4     # Guided skill browser\n```\n\nOr directly:\n\n```bash\n# Skills are loaded from:\n# - apps/cli/skills/standard/     (built-in standard)\n# - apps/cli/skills/mipham/       (built-in mipham)\n# - ~/.mipham/skills/             (user-installed)\n# - .mipham/skills/               (project-local)\n```\n\n### 5.3 — Install Specific Skills\n\n```\n/skills install <name>    # Install from registry\n/skills list              # List available\n/skills search <query>    # Search registry\n```\n\n### ✅ Verification\n\n```\n/skills list   # Should show installed skills with counts\n```\n\n---\n\n## Phase 6: Permissions Configuration\n\n**Trigger**: Permission mode not configured or wrong for use case.\n\n### 6.1 — Permission Modes\n\n| Mode                | Behavior                        | Use Case                            |\n| ------------------- | ------------------------------- | ----------------------------------- |\n| `default`           | Prompt for each tool            | Normal development (recommended)    |\n| `acceptEdits`       | Auto-allow edits, prompt others | Active coding sessions              |\n| `plan`              | Plan-only, no tool execution    | Design & architecture work          |\n| `bypassPermissions` | Skip all checks                 | ⚠️ Only for fully trusted codebases |\n\n### 6.2 — Configure\n\nIn `.mipham/config.yml`:\n\n```yaml\npermission: default\n```\n\nOr via slash command:\n\n```\n/permissions           # View current settings\n/setup 5               # Permission setup wizard\n```\n\n### 6.3 — CI/CD Safety\n\nFor CI/CD environments, use the `default` mode (the daemon default): headless\nsessions never prompt, so `ask`-level tools (Bash/Write/Edit) are blocked rather\nthan auto-approved.\n\n### ✅ Verification\n\n```\n/permissions   # Should show current mode\n```\n\n---\n\n## Phase 7: Workspace Trust\n\n**Trigger**: Untrusted workspace (prompted on startup in v0.24.3+).\n\n### 7.1 — Understanding Workspace Trust\n\nWorkspace trust is a security mechanism that prevents AI from operating in untrusted directories. Trust is **hierarchical**: trusting `/Users/me/Projects` implicitly trusts all subdirectories.\n\n### 7.2 — Trust a Workspace\n\n**Interactive**: Accept the trust prompt when launching Mipham Code in a new directory.\n\n**Manual**:\n\n```\n/trust              # Show trust status\n/trust add <dir>    # Trust a directory\n/trust remove <dir> # Revoke trust\n```\n\n### 7.3 — Trust Store\n\n```\n~/.mipham/trusted-workspaces.json\n```\n\n### 7.4 — Auto-Trust for Worktrees\n\nWhen using git worktrees, Mipham Code automatically trusts worktree directories if the parent workspace is already trusted (via `EnterWorktree`).\n\n### ✅ Verification\n\n```\n/trust   # Should show \"✅ Yes\" for current directory\n```\n\n---\n\n## Phase 8: Shell & IDE Integration\n\n**Trigger**: Want terminal integration, aliases, or IDE plugins.\n\n### 8.1 — Shell Alias\n\nAdd to `~/.zshrc` or `~/.bashrc`:\n\n```bash\nalias mipham='cd ~/your-project && bun run ~/path/to/mipham-code/apps/cli/bin/mipham.ts'\n# Or if installed globally:\nalias mipham='mipham'\n```\n\n### 8.2 — VS Code Integration\n\nRun `/ide` to auto-generate `.vscode/` config files:\n\n- `settings.json` — terminal profile \"mipham\" using Bun\n- `keybindings.json` — Cmd+Esc to focus terminal, Cmd+Shift+M for new terminal\n- `extensions.json` — recommends `miphamai.mipham-code` extension\n\nTo use after generation:\n\n1. Restart VS Code (or Cmd+Shift+P → Reload Window)\n2. Open terminal: Ctrl+` or Cmd+Esc\n3. Select \"mipham\" profile from terminal dropdown\n\nInstall the VS Code extension:\n\n```bash\ncode --install-extension miphamai.mipham-code\n```\n\n### 8.3 — JetBrains Integration\n\nSettings → Tools → Terminal → Shell path → `bun run mipham`\n\n### 8.4 — Terminal Setup\n\n```\n/terminal-setup    # Shell & terminal config wizard\n/setup 6           # Shell integration (part of full wizard)\n```\n\n### ✅ Verification\n\n```bash\nwhich mipham       # Should resolve\n# In VS Code: Ctrl+` → select \"mipham\" profile\n```\n\n---\n\n## Phase 9: Full Verification\n\nRun after all configuration phases complete.\n\n### 9.1 — System Diagnostics\n\n```\n/doctor            # System diagnostics check\n```\n\n### 9.2 — End-to-End Test\n\nStart a conversation and verify:\n\n1. Model responds (not stuck on \"connecting...\")\n2. File tools work: \"read CLAUDE.md\"\n3. Bash works: \"list files in current directory\"\n4. Skills load: `/skills list`\n\n### 9.3 — Common Issues & Fixes\n\n| Symptom                   | Diagnosis                              | Fix                                              |\n| ------------------------- | -------------------------------------- | ------------------------------------------------ |\n| \"Provider not registered\" | Missing or invalid API key             | `env \\| grep API_KEY`; check key format          |\n| \"Model not found\"         | Model ID mismatch or disabled provider | `/models` to list available; `/switch` to change |\n| Slow responses            | Large model, network, or context full  | `/fast on` or switch to Flash model; `/compact`  |\n| Context full              | Too many messages in history           | `/compact` to compress; `/clear` to reset        |\n| Permission denied         | Tool blocked by permission mode        | `/permissions` to check; adjust mode             |\n| \"Workspace not trusted\"   | New directory, not yet trusted         | Accept startup prompt or run `/trust`            |\n| MCP tools not available   | Server not connected                   | `/mcp connect <name>` or check config            |\n| Update not applying       | Cached binary                          | `mipham update --force` then restart             |\n| Config changes ignored    | YAML syntax error                      | Validate with `mipham --check-config`            |\n\n### 9.4 — Get Help\n\n```\n/help              # Full command reference\n/setup             # Re-run setup wizard\n/doctor            # Run diagnostics\n```\n\nChat-based help: \"help me configure X\" or \"why isn't Y working?\"\n\n---\n\n## Quick Reference: Essential Slash Commands\n\n| Category      | Command           | Purpose                                                |\n| ------------- | ----------------- | ------------------------------------------------------ |\n| **Setup**     | `/setup`          | Full 6-step setup wizard                               |\n|               | `/setup 1`        | Initialize project (.mipham/ + MIPHAM.md + config.yml) |\n|               | `/setup 2`        | Configure providers & API keys                         |\n|               | `/setup 3`        | Choose default model                                   |\n|               | `/setup 4`        | Browse & install skills                                |\n|               | `/setup 5`        | Configure permissions                                  |\n|               | `/setup 6`        | Shell & IDE integration                                |\n| **Diagnosis** | `/doctor`         | System diagnostics                                     |\n|               | `/trust`          | Workspace trust status                                 |\n|               | `/permissions`    | Tool permission settings                               |\n| **Model**     | `/model`          | Interactive model picker (Ctrl+P)                      |\n|               | `/switch`         | Switch provider                                        |\n|               | `/models`         | List available models                                  |\n| **Session**   | `/clear`          | Reset conversation                                     |\n|               | `/compact`        | Compress context                                       |\n|               | `/rename`         | Rename session                                         |\n| **Workflow**  | `/plan`           | Enter plan mode                                        |\n|               | `/review`         | Code review                                            |\n|               | `/todos`          | Task list                                              |\n| **IDE**       | `/ide`            | Generate VS Code integration files                     |\n|               | `/terminal-setup` | Shell & terminal config                                |\n| **Skills**    | `/skills list`    | List installed skills                                  |\n|               | `/skills search`  | Search skill registry                                  |\n|               | `/skills install` | Install a skill                                        |\n\n---\n\n## Post-Setup: What to Do Next\n\nAfter configuration is verified:\n\n1. **Initialize your project**: \"help me understand this codebase\"\n2. **Set up CLAUDE.md**: `/init` to generate project documentation for the AI\n3. **Install relevant skills**: `/setup 4` or `/skills search`\n4. **Configure MCP servers**: `/mcp connect` for external tool integration\n5. **Start coding**: Just start a conversation — the AI will use tools and skills automatically\n" },
   { type: 'standard', raw: "---\nname: research\ndescription: Deep research against primary sources, executed as a background agent. Collects findings into a single cited Markdown file. Use for investigation that requires reading official docs, source code, specs, or first-party APIs — not secondary summaries.\nversion: 1.0.0\nuser-invocable: true\nallowed-tools:\n  - WebSearch\n  - WebFetch\n  - Agent\n  - Bash\n  - Write\n  - Read\n---\n\n# Research — Background Deep Research\n\n融合 Mipham web-search v3.0（查询构建+验证）+ Matt Pocock research（后台代理+一手来源+Markdown 报告）。\n\n## When to Use\n\n- \"Research X for me\"\n- \"Find out everything about Y from primary sources\"\n- \"Investigate Z and write up findings\"\n- Any question where googling + reading multiple sources is the right answer\n\n## When NOT to Use\n\n- Quick fact lookup → use `/web-search` directly\n- Question answerable from code already in context\n- Pure logic/algorithmic question\n\n---\n\n## Phase 0: Route\n\n```\nResearch task is...\n├── Quick (1-2 sources, immediate answer)?\n│   └── → Use web-search skill directly (Phase 0-4)\n│\n├── Deep (multiple sources, needs synthesis)?\n│   └── → THIS SKILL — background agent\n│\n└── Login-walled / SPA-only sources?\n    └── → web-access skill (ComputerUse browser)\n```\n\n---\n\n## Phase 1: Spin Up Background Agent\n\nLaunch a **background agent** to do the heavy reading, so you keep working while it researches.\n\nThe agent's instructions:\n\n```\nYou are a research agent. Your task:\n\n1. Investigate the question against PRIMARY SOURCES ONLY:\n   - Official documentation (docs.*.com, *.org)\n   - Source code repositories (GitHub, GitLab)\n   - Technical specifications (RFCs, standards)\n   - First-party API references\n   - NOT: blog posts, Medium articles, forum threads, secondary summaries\n\n2. For every claim, follow it back to the source that owns it.\n   If a secondary source makes a claim, find the primary source and cite that.\n\n3. Use WebSearch to find sources.\n   Use WebFetch to deep-read promising pages.\n   Cross-reference critical claims across 2+ independent primary sources.\n\n4. Write findings to a SINGLE Markdown file.\n   - Cite every claim with its primary source URL\n   - Distinguish between facts (needs citation) and reasoning (your own)\n   - Flag outdated content (\"article from 2024, may be stale\")\n   - Note if a source is official docs vs community\n\n5. Save the file where the repo already keeps such notes.\n   Match existing conventions. If none exist, put it in docs/research/.\n```\n\n---\n\n## Phase 2: Report Format\n\nThe agent writes findings in this structure:\n\n```markdown\n# [Research Topic]\n\n**Date**: YYYY-MM-DD\n**Sources**: N primary, M cross-references\n\n## Key Findings\n\n- [Finding 1] — [Source](URL)\n- [Finding 2] — [Source](URL)\n\n## Detailed Analysis\n\n### [Subtopic A]\n\n[Claim and citation]\n\n### [Subtopic B]\n\n[Claim and citation]\n\n## Source Evaluation\n\n| Source      | Type          | Authority | Notes                 |\n| ----------- | ------------- | --------- | --------------------- |\n| [Name](URL) | Official docs | High      | Current as of YYYY-MM |\n| [Name](URL) | Source code   | High      | Tag vX.Y.Z            |\n\n## Open Questions\n\n- [Question 1]\n- [Question 2]\n\nSources:\n\n- [Title](URL) — brief note\n```\n\n---\n\n## Phase 3: Review\n\nWhen the background agent completes:\n\n1. Read the output file\n2. Spot-check: did it follow the chain back to primary sources?\n3. Flag any claims that need further verification\n4. Surface uncertainties to the user\n\n---\n\n## Research Quality Checklist\n\n- [ ] Every factual claim has a primary source citation\n- [ ] At least one critical claim is cross-referenced (2+ sources)\n- [ ] Source type is clearly identified (official docs / source code / spec / community)\n- [ ] Outdated content is flagged with publication year\n- [ ] Reasoning vs facts are clearly distinguished\n- [ ] File saved in repo-appropriate location\n" },
   { type: 'standard', raw: "---\nname: security-review\ndescription: Security audit skill — vulnerability scanning, OWASP Top 10, secrets detection, supply chain analysis, and compliance checking\nversion: 1.0.0\n---\n\n# Security Review\n\nComprehensive security audit for codebases. Covers vulnerability detection, compliance, and hardening recommendations.\n\n## Audit Checklist\n\n### 1. Secrets & Credentials\n\n- [ ] No hardcoded API keys, tokens, or passwords in source files\n- [ ] `.env` and `*.pem` files in `.gitignore`\n- [ ] API keys use environment variables or secret managers\n- [ ] No credentials in git history (check `git log -p`)\n- [ ] CI/CD secrets stored securely (not in workflow files)\n\n### 2. OWASP Top 10\n\n- [ ] **Injection**: SQL, NoSQL, OS command, LDAP injection points\n- [ ] **Broken Authentication**: Weak password policies, missing MFA\n- [ ] **Sensitive Data Exposure**: Unencrypted PII, missing TLS\n- [ ] **XXE**: XML external entity processing\n- [ ] **Broken Access Control**: Missing authorization checks\n- [ ] **Security Misconfiguration**: Default credentials, verbose errors\n- [ ] **XSS**: Reflected, stored, DOM-based cross-site scripting\n- [ ] **Insecure Deserialization**: Untrusted data deserialization\n- [ ] **Using Vulnerable Components**: Outdated dependencies with CVEs\n- [ ] **Insufficient Logging**: Missing audit trails for auth events\n\n### 3. Supply Chain\n\n- [ ] All dependencies have known licenses (no copyleft/GPL)\n- [ ] No dependencies with critical CVEs\n- [ ] Lock files committed (pnpm-lock.yaml, package-lock.json)\n- [ ] Dependency update policy in place\n- [ ] SBOM (Software Bill of Materials) available\n\n### 4. Network & API Security\n\n- [ ] TLS 1.3 enforced for all external communications\n- [ ] API endpoints have rate limiting\n- [ ] CORS configured with explicit origins (not `*`)\n- [ ] SSRF protections in place (URL validation, IP filtering)\n- [ ] WebSocket connections use WSS\n- [ ] GraphQL endpoints have query depth limits\n\n### 5. File System & Path Security\n\n- [ ] Path traversal protections (no `../../../etc/passwd`)\n- [ ] File upload validation (type, size, content inspection)\n- [ ] Symlink attacks prevented\n- [ ] Sensitive directories blocked (`/etc`, `/proc`, `/sys`)\n- [ ] Temporary files cleaned up after use\n\n### 6. Code-Level Security\n\n- [ ] No `eval()` or `Function()` with user input\n- [ ] No `child_process.exec()` with unsanitized input\n- [ ] Regex patterns safe from ReDoS\n- [ ] Prototype pollution prevented\n- [ ] No `dangerouslySetInnerHTML` without sanitization (React)\n- [ ] SQL queries use parameterized statements\n\n### 7. Authentication & Sessions\n\n- [ ] Passwords hashed with bcrypt/argon2 (not MD5/SHA1)\n- [ ] Session tokens use `httpOnly`, `secure`, `SameSite=Strict`\n- [ ] JWT tokens have reasonable expiration\n- [ ] Account lockout after failed attempts\n- [ ] Password reset tokens expire and are single-use\n\n### 8. Data Protection\n\n- [ ] PII data encrypted at rest (AES-256-GCM)\n- [ ] Data encrypted in transit (TLS 1.3)\n- [ ] Logs do not contain sensitive data\n- [ ] Database backups encrypted\n- [ ] Data retention policies defined\n\n### 9. Infrastructure\n\n- [ ] Infrastructure as Code (Terraform/Pulumi) used\n- [ ] Cloud resources not publicly exposed unless intended\n- [ ] Security groups / firewalls restrict inbound traffic\n- [ ] Container images scanned for vulnerabilities\n- [ ] Kubernetes pods run as non-root\n\n### 10. Logging & Monitoring\n\n- [ ] Authentication events logged\n- [ ] Failed access attempts logged and alerted\n- [ ] Structured logging format (JSON)\n- [ ] No PII in log messages\n- [ ] Alert thresholds configured for critical events\n\n## Report Format\n\n```\nSecurity Review Report\n======================\nDate: YYYY-MM-DD\nSeverity: Critical | High | Medium | Low\n\nFinding #N: [Title]\nSeverity: Critical/High/Medium/Low\nLocation: file:line\nDescription: [What was found]\nRisk: [What could happen]\nFix: [How to resolve]\n```\n\n## Compliance Standards\n\n- OWASP ASVS Level 2\n- PCI DSS (if handling payment data)\n- GDPR (if handling EU personal data)\n- SOC 2 Type II\n- ISO 27001\n" },
   { type: 'standard', raw: "---\nname: self-review\ndescription: Self-review of staged or recently changed code — reuse, simplification, efficiency, and architectural alignment\nversion: 2.0.0\n---\n\n# Self Review\n\nReview your own code changes before committing or merging. Focus on quality improvements, not bug hunting.\n\n## When to Run\n\n- Before committing changes\n- After completing a feature or fix\n- Before requesting a peer review\n- As the final step before merging\n\n## Review Passes\n\n### Pass 1: Reuse\n\n- Is there existing code that does the same thing?\n- Are there utility functions or shared libraries you missed?\n- Could this be solved with a standard library method?\n- Are you reimplementing something the framework provides?\n\n### Pass 2: Simplification\n\n- Can a complex function be split into smaller, named functions?\n- Are there unnecessary abstractions (interfaces with one impl, unused generics)?\n- Can nested conditionals be flattened with early returns?\n- Is there dead code, unused imports, or commented-out blocks?\n\n### Pass 3: Efficiency\n\n- Are you looping over data multiple times when once would suffice?\n- Are large objects being copied unnecessarily?\n- Could a synchronous operation be made async/non-blocking?\n- Are regex patterns compiled once or on every call?\n\n### Pass 4: Altitude (Architectural Alignment)\n\n- Does this code belong where it is?\n- Is it in the right layer (UI / business logic / data access)?\n- Does it follow existing patterns in the codebase?\n- Would a new developer understand where to find this?\n\n## Output\n\nAfter each pass, either:\n\n- Apply the improvement directly (for clear wins)\n- Note the observation with a recommendation (for trade-off decisions)\n\n## Anti-Patterns\n\n- ❌ Rewriting working code for style preference\n- ❌ Adding abstractions \"just in case\"\n- ❌ Changing code outside the scope of your changes\n- ❌ \"This could be a microservice\" — no it couldn't\n" },

package/src/tools/exec/bash.ts

@@ -29,10 +29,10 @@ const BLOCKED_PATTERNS = [
   />\s*\/dev\/sd[a-z]/,
   // SSH private key theft
   /\bcat\s+.*\/\.ssh\/id_/,
-  // Shell command substitution (commonly used for obfuscation/evasion)
-  /\$\(/,
-  // Backtick command substitution
-  /`[^`]+`/,
+  // NOTE: command substitution ($( … ) / `…`) is a legitimate Bash feature, so it is
+  // NOT blocked wholesale. The dangerous content inside a substitution (curl|sh,
+  // base64 -d, python -c, eval, bash -c, source, …) is still caught by the specific
+  // patterns below, which test the whole command string including inside $().
   // Interpreter code execution (bypass vector) — covers python, python2, python3
   /\bpython[23]?\s+-c\b/,
   /\bpython[23]?\s+-m\b/,

package/src/ui/app.tsx

@@ -90,25 +90,14 @@ interface AgentProgress {
 // Version is read fresh from package.json at startup via runApp prop
 // (bypasses Bun module caching after npm update)
 
-// Cycle order: Claude Code modes first (manual → accept edits → bypass),
-// then Mipham-specific modes (plan → auto → dont ask).
-const PERMISSION_MODES: PermissionMode[] = [
-  'default',
-  'acceptEdits',
-  'bypassPermissions',
-  'plan',
-  'auto',
-  'dontAsk',
-]
+// Cycle order: Claude Code modes (manual → accept edits → plan → bypass).
+const PERMISSION_MODES: PermissionMode[] = ['default', 'acceptEdits', 'plan', 'bypassPermissions']
 // Labels aligned with Claude Code terminology: describe behavior, not capability.
-// Claude Code modes: manual mode → accept edits on → bypass
-// Mipham extends with 3 extra modes (plan, auto, dontAsk) for finer control.
+// Claude Code modes: manual mode → accept edits on → plan → bypass.
 const PERMISSION_COLORS: Record<PermissionMode, string> = {
   default: 'white',
   acceptEdits: 'blue',
   plan: 'yellow',
-  auto: 'green',
-  dontAsk: 'cyan',
   bypassPermissions: 'red',
 }
 
@@ -165,8 +154,6 @@ export function App({
       default: t('ui.permission.manual'),
       acceptEdits: t('ui.permission.accept_edits'),
       plan: t('ui.permission.plan_mode'),
-      auto: t('ui.permission.auto'),
-      dontAsk: t('ui.permission.dont_ask'),
       bypassPermissions: t('ui.permission.bypass'),
     }),
     [t],
@@ -191,6 +178,9 @@ export function App({
   const [goalText, setGoalText] = useState('')
   const [permissionMode, setPermissionMode] = useState<PermissionMode>('default')
   const abortRef = useRef<AbortController | null>(null)
+  // Monotonic turn id — lets a stale turn's finally() skip resetting shared UI
+  // state (isLoading/abortRef/progress) after a newer turn has already started.
+  const turnIdRef = useRef(0)
   // Stream buffer: accumulate text chunks and throttle state updates to ~16fps.
   // Without this, every SSE chunk triggers setMessages → copies full array →
   // re-renders ChatPanel → re-runs compactToolGroups O(n). At 20-50 chunks/sec
@@ -200,6 +190,11 @@ export function App({
     isFirst: boolean
     timer: ReturnType<typeof setTimeout> | null
   }>({ turnContent: '', isFirst: true, timer: null })
+  // Reasoning/thinking transparency: accumulate reasoning tokens and surface them
+  // as a live "thinking" indicator instead of silently dropping them.
+  const [thinkingText, setThinkingText] = useState('')
+  const thinkingRef = useRef('')
+  const thinkingTimerRef = useRef<ReturnType<typeof setTimeout> | null>(null)
   const [agentProgress, setAgentProgress] = useState<AgentProgress | null>(null)
   // Multi-agent tracking: keyed by agent/task ID, shows all running + recently completed agents
   const [runningAgents, setRunningAgents] = useState<Record<string, AgentEntry>>({})
@@ -345,6 +340,7 @@ export function App({
   const handleSubmit = useCallback(
     async (input: string) => {
       if (!input.trim()) return
+      const turnId = ++turnIdRef.current
 
       // ── @mention: direct cross-session message — only when the name resolves
       // to a live session; otherwise fall through to normal AI processing so a
@@ -585,15 +581,36 @@ export function App({
           emotionPrefix ? emotionPrefix + input : input,
           controller.signal,
         )) {
-          // Reasoning content (DeepSeek V4 thinking mode) — silently consumed,
-          // not shown to user to avoid noise.
+          // Reasoning content (DeepSeek V4 thinking mode) — surface as a live
+          // "thinking" indicator so long reasoning passes don't look like a stall.
           if (chunk.reasoning_content) {
+            thinkingRef.current += chunk.reasoning_content
+            if (!thinkingTimerRef.current) {
+              thinkingTimerRef.current = setTimeout(() => {
+                thinkingTimerRef.current = null
+                setThinkingText(thinkingRef.current)
+              }, 60)
+            }
             continue
           }
 
           if (chunk.type === 'text' && chunk.content) {
             // New turn: push fresh assistant message, reset stream buffer
             if (isNewTurn) {
+              // Flush any accumulated reasoning as a collapsed history line
+              if (thinkingRef.current) {
+                const thought = thinkingRef.current
+                thinkingRef.current = ''
+                setThinkingText('')
+                if (thinkingTimerRef.current) {
+                  clearTimeout(thinkingTimerRef.current)
+                  thinkingTimerRef.current = null
+                }
+                setMessages((prev) => [
+                  ...prev,
+                  { role: 'system' as const, content: `💭 ${thought}` },
+                ])
+              }
               turnContent = chunk.content
               isNewTurn = false
               streamBufferRef.current = { turnContent: chunk.content, isFirst: false, timer: null }
@@ -768,16 +785,20 @@ export function App({
       } catch (err) {
         setMessages((prev) => [...prev, { role: 'system', content: `Error: ${String(err)}` }])
       } finally {
-        // Flush any remaining stream buffer before finishing
-        flushStreamBuffer()
-        setIsLoading(false)
-        abortRef.current = null
-        // Clear all progress/tool indicators
-        agentProgressRef.current = null
-        setAgentProgress(null)
-        activeToolRef.current = null
-        setActiveTool(null)
-        setAgentTick((t) => t + 1)
+        // Only the latest turn resets shared UI state — a stale turn's finally
+        // must not clobber a newer turn's isLoading/abortRef/progress.
+        if (turnIdRef.current === turnId) {
+          // Flush any remaining stream buffer before finishing
+          flushStreamBuffer()
+          setIsLoading(false)
+          abortRef.current = null
+          // Clear all progress/tool indicators
+          agentProgressRef.current = null
+          setAgentProgress(null)
+          activeToolRef.current = null
+          setActiveTool(null)
+          setAgentTick((t) => t + 1)
+        }
         // Auto-save checkpoint after each AI response
         if (assistantContent) {
           engine.getContext().saveCheckpoint('post-turn')
@@ -791,7 +812,6 @@ export function App({
 
   useInput((_input, key) => {
     // Escape: close apiKeyPrompt → close picker → abort loading (does NOT exit app)
-    // Vim mode toggle is handled by InputBar
     if (key.escape) {
       if (apiKeyPrompt) {
         setApiKeyPrompt(null)
@@ -806,8 +826,7 @@ export function App({
         abortRef.current.abort()
         return
       }
-      // When input is empty and not loading, let InputBar handle Escape
-      // (it toggles vim mode or clears pending sequences)
+      // Otherwise let InputBar handle Escape (clear draft)
       return
     }
     // All other global hotkeys (Shift+Tab, Ctrl+P, Ctrl+F, Ctrl+O)
@@ -883,6 +902,7 @@ export function App({
           <>
             {/* Chat panel */}
             <ChatPanel messages={messages} focusMode={focusMode} />
+            {thinkingText ? <Text dimColor>💭 {thinkingText.slice(-200)}</Text> : null}
 
             {/* Input with separator lines */}
             {pickerOpen ? (
@@ -989,9 +1009,8 @@ export function App({
                 <Text dimColor>
                   {' '}
                   ({t('ui.status.shift_tab_cycle')}: {PERMISSION_LABELS.default} ·{' '}
-                  {PERMISSION_LABELS.acceptEdits} · {PERMISSION_LABELS.bypassPermissions} ·{' '}
-                  {PERMISSION_LABELS.plan} · {PERMISSION_LABELS.auto} · {PERMISSION_LABELS.dontAsk})
-                  {' · '}
+                  {PERMISSION_LABELS.acceptEdits} · {PERMISSION_LABELS.plan} ·{' '}
+                  {PERMISSION_LABELS.bypassPermissions}){' · '}
                   {t('ui.status.esc_to_interrupt')}
                   {' · '}
                   {t('ui.status.left_for_agents')}

package/src/ui/graft-status.tsx

@@ -1,7 +1,7 @@
 import React, { useState } from 'react'
 import { Box, Text } from 'ink'
 import { basename } from 'node:path'
-import { readGraftStats, type GraftStats } from '../shared/graft-stats'
+import { findGraftStats, type GraftStats } from '../shared/graft-stats'
 import { getGraftSavings } from '../shared/graft-savings'
 
 /** Freshness segment mirroring graft's own statusline (see @nanonets/graft format.js). */
@@ -17,16 +17,18 @@ function freshnessSegment(stats: GraftStats): { label: string; color: string } {
  * Bottom-of-screen graft status line — mirrors graft's own "◤ graft · …" bar:
  *   ◤ graft · N nodes / E edges · ✓ synced · ~T tok saved
  *   ▸ ctx X% · last: file
- * Reads `graft/.cache/stats.json` once at mount; the session's tok-saved total
- * is read live each render (the app re-renders on the agent tick). Returns
- * null (renders nothing) when graft isn't built here.
+ * Reads `graft/.cache/stats.json` (walking up to the repo root) once at mount;
+ * the session's tok-saved total is read live each render (the app re-renders on
+ * the agent tick). Renders nothing only when there's no graft graph AND no known
+ * ctx% — the ctx% line shows even when graft isn't built in this directory.
  */
 export function GraftStatusLine({ cwd, ctxPct }: { cwd: string; ctxPct?: number }) {
-  const [stats] = useState(() => readGraftStats(cwd))
-  if (!stats) return null
-  const fresh = freshnessSegment(stats)
+  const [stats] = useState(() => findGraftStats(cwd))
+  const showCtx = typeof ctxPct === 'number'
+  if (!stats && !showCtx) return null
+  const fresh = stats ? freshnessSegment(stats) : null
   const saved = getGraftSavings()
-  const lastFile = stats.lastFile ? basename(stats.lastFile) : null
+  const lastFile = stats?.lastFile ? basename(stats.lastFile) : null
 
   const bottom: string[] = []
   if (typeof ctxPct === 'number') bottom.push(`ctx ${ctxPct}%`)
@@ -34,21 +36,23 @@ export function GraftStatusLine({ cwd, ctxPct }: { cwd: string; ctxPct?: number
 
   return (
     <Box flexDirection="column">
-      <Box>
-        <Text dimColor>◤ </Text>
-        <Text color="blue">graft</Text>
-        <Text dimColor>
-          {' '}
-          · {stats.nodeCount} nodes / {stats.edgeCount} edges ·{' '}
-        </Text>
-        <Text color={fresh.color}>{fresh.label}</Text>
-        {saved > 0 && (
-          <>
-            <Text dimColor> · </Text>
-            <Text color="blue">~{saved.toLocaleString()} tok saved</Text>
-          </>
-        )}
-      </Box>
+      {stats && fresh && (
+        <Box>
+          <Text dimColor>◤ </Text>
+          <Text color="blue">graft</Text>
+          <Text dimColor>
+            {' '}
+            · {stats.nodeCount} nodes / {stats.edgeCount} edges ·{' '}
+          </Text>
+          <Text color={fresh.color}>{fresh.label}</Text>
+          {saved > 0 && (
+            <>
+              <Text dimColor> · </Text>
+              <Text color="blue">~{saved.toLocaleString()} tok saved</Text>
+            </>
+          )}
+        </Box>
+      )}
       {bottom.length > 0 && (
         <Box>
           <Text dimColor>▸ {bottom.join(' · ')}</Text>