oh-my-copilot 4.13.2 → 4.13.21

package/skills/omc-setup/phases/02-configure.md

@@ -2,28 +2,16 @@
 
 **Skip condition**: If resuming and `lastCompletedStep >= 4`, skip this entire phase.
 
-## Quick Mode Behavior
-
-If `SETUP_MODE=quick`, apply all defaults non-interactively:
-- **Step 2.1 (HUD)**: Run HUD setup automatically (no prompt needed — it doesn't ask questions)
-- **Step 2.2 (Cache)**: Run cache cleanup automatically
-- **Step 2.3 (Updates)**: Run update check automatically
-- **Step 2.4 (Execution mode)**: Set `ultrawork` automatically (it's the only option)
-- **Step 2.5 (CLI install)**: Auto-install if not already present. Before installing, inform the user: "Installing the OMC CLI (`omcp`) — this enables standalone commands like `omcp team`, `omcp ask`, and `omcp status`." Then run `npm i -g oh-my-copilot` without prompting.
-- **Step 2.6 (Task tool)**: Set `builtin` automatically (only prompt if beads/beads-rust is detected)
-
-Then save progress and continue to Phase 3. The rest of this file documents the **interactive mode** behavior.
-
----
-
 ## Step 2.1: Setup HUD Statusline
 
 **Note**: If resuming and `lastCompletedStep >= 3`, skip to Step 2.2.
 
-The HUD shows real-time status in Copilot CLI's status bar. Invoke the hud skill to set up and configure:
+The HUD shows real-time status in Claude Code's status bar. Delegate all HUD/statusLine setup to the `hud` skill:
 
 Use the Skill tool to invoke: `hud` with args: `setup`
 
+Do not generate, normalize, or patch `statusLine` paths inline in this phase. This is especially important on Windows, where backslash path handling must stay inside the `hud` skill.
+
 This will:
 1. Install the HUD wrapper script to `~/.copilot/hud/omcp-hud.mjs`
 2. Configure `statusLine` in `~/.copilot/settings.json`
@@ -32,7 +20,7 @@ This will:
 After HUD setup completes, save progress:
 ```bash
 CONFIG_TYPE=$(jq -r '.configType // "unknown"' ".omcp/state/setup-state.json" 2>/dev/null || echo "unknown")
-bash "${COPILOT_PLUGIN_ROOT}/scripts/setup-progress.sh" save 3 "$CONFIG_TYPE"
+bash "${CLAUDE_PLUGIN_ROOT}/scripts/setup-progress.sh" save 3 "$CONFIG_TYPE"
 ```
 
 ## Step 2.2: Clear Stale Plugin Cache
@@ -56,13 +44,13 @@ const b=p.join(d,'plugins','cache','omc','oh-my-copilot');
 try{const vs=f.readdirSync(b).filter(x=>/^\d/.test(x)).sort((a,c)=>a.localeCompare(c,void 0,{numeric:true}));if(vs.length)v=vs[vs.length-1]}catch{}
 // Try .omc-version.json second
 if(v==='')try{const j=JSON.parse(f.readFileSync('.omc-version.json','utf-8'));v=j.version||''}catch{}
-// Try copilot-instructions.md header third
-if(v==='')for(const c of['.copilot/copilot-instructions.md',p.join(d,'copilot-instructions.md')]){try{const m=f.readFileSync(c,'utf-8').match(/^# oh-my-copilot.*?(v?\d+\.\d+\.\d+)/m);if(m){v=m[1].replace(/^v/,'');break}}catch{}}
+// Try CLAUDE.md header third
+if(v==='')for(const c of['.claude/CLAUDE.md',p.join(d,'CLAUDE.md')]){try{const m=f.readFileSync(c,'utf-8').match(/^# oh-my-copilot.*?(v?\d+\.\d+\.\d+)/m);if(m){v=m[1].replace(/^v/,'');break}}catch{}}
 console.log('Installed:',v||'(not found)');
 "
 
 # Check npm for latest version
-LATEST_VERSION=$(npm view oh-my-copilot version 2>/dev/null)
+LATEST_VERSION=$(npm view oh-my-claude-sisyphus version 2>/dev/null)
 
 if [ -n "$INSTALLED_VERSION" ] && [ -n "$LATEST_VERSION" ]; then
   if [ "$INSTALLED_VERSION" != "$LATEST_VERSION" ]; then
@@ -71,7 +59,7 @@ if [ -n "$INSTALLED_VERSION" ] && [ -n "$LATEST_VERSION" ]; then
     echo "  Installed: v$INSTALLED_VERSION"
     echo "  Latest:    v$LATEST_VERSION"
     echo ""
-    echo "To update, run: copilot /install-plugin oh-my-copilot"
+    echo "To update, run: claude /install-plugin oh-my-copilot"
   else
     echo "You're on the latest version: v$INSTALLED_VERSION"
   fi
@@ -89,7 +77,7 @@ Use the AskUserQuestion tool to prompt the user:
 **Options:**
 1. **ultrawork (maximum capability)** - Uses all agent tiers including Opus for complex tasks. Best for challenging work where quality matters most. (Recommended)
 
-Store the preference in `~/.copilot/.omc-config.json`:
+Store the preference in `~/.copilot/.omcp-config.json`:
 
 ```bash
 CONFIG_FILE="${COPILOT_CONFIG_DIR:-$HOME/.copilot}/.omc-config.json"
@@ -110,16 +98,13 @@ echo "Default execution mode set to: USER_CHOICE"
 
 ## Step 2.5: Install OMC CLI Tool
 
-The OMC CLI (`omcp` command) provides standalone monitoring and analytics commands.
-The `omcp` binary coexists with upstream's `omc` binary (oh-my-claudecode) — no conflict.
+The OMC CLI (`omc` command) provides standalone helper commands such as `omc hud`, `omc teleport`, and `omc team ...`.
 
 First, check if the CLI is already installed:
 
 ```bash
-OMC_CLI_INSTALLED="false"
-
-if command -v omcp &>/dev/null; then
-  OMC_CLI_VERSION=$(omcp --version 2>/dev/null | head -1 || echo "installed")
+if command -v omc &>/dev/null; then
+  OMC_CLI_VERSION=$(omc --version 2>/dev/null | head -1 || echo "installed")
   echo "OMC CLI already installed: $OMC_CLI_VERSION"
   OMC_CLI_INSTALLED="true"
 else
@@ -131,31 +116,31 @@ If `OMC_CLI_INSTALLED` is `"true"`, skip the rest of this step.
 
 If `OMC_CLI_INSTALLED` is `"false"`, use AskUserQuestion:
 
-**Question:** "Would you like to install the OMC CLI globally for standalone monitoring and analytics? (`omcp team`, `omcp ask`)"
+**Question:** "Would you like to install the OMC CLI globally for standalone helper commands? (`omc`, `omc hud`, `omc teleport`)"
 
 **Options:**
-1. **Yes (Recommended)** - Install `oh-my-copilot` via `npm install -g`
-2. **No - Skip** - Skip installation (can install manually later with `npm install -g oh-my-copilot`)
+1. **Yes (Recommended)** - Install `oh-my-claude-sisyphus` via `npm install -g`
+2. **No - Skip** - Skip installation (can install manually later with `npm install -g oh-my-claude-sisyphus`)
 
 If user chooses **Yes**:
 
 ```bash
 if ! command -v npm &>/dev/null; then
   echo "WARNING: npm not found. Cannot install OMC CLI automatically."
-  echo "Install Node.js/npm first, then run: npm install -g oh-my-copilot"
+  echo "Install Node.js/npm first, then run: npm install -g oh-my-claude-sisyphus"
 else
-  if npm install -g oh-my-copilot 2>&1; then
+  if npm install -g oh-my-claude-sisyphus 2>&1; then
     echo "OMC CLI installed successfully."
-    if command -v omcp &>/dev/null; then
-      OMC_CLI_VERSION=$(omcp --version 2>/dev/null | head -1 || echo "installed")
-      echo "Verified: omcp $OMC_CLI_VERSION"
+    if command -v omc &>/dev/null; then
+      OMC_CLI_VERSION=$(omc --version 2>/dev/null | head -1 || echo "installed")
+      echo "Verified: omc $OMC_CLI_VERSION"
     else
-      echo "Installed but 'omcp' not on PATH. You may need to restart your shell."
+      echo "Installed but 'omc' not on PATH. You may need to restart your shell."
     fi
   else
     echo "WARNING: Failed to install OMC CLI (permission issue or network error)."
-    echo "You can install manually later: npm install -g oh-my-copilot"
-    echo "Or with sudo: sudo npm install -g oh-my-copilot"
+    echo "You can install manually later: npm install -g oh-my-claude-sisyphus"
+    echo "Or with sudo: sudo npm install -g oh-my-claude-sisyphus"
   fi
 fi
 ```
@@ -195,7 +180,7 @@ If beads or beads-rust is detected, use AskUserQuestion:
 **Question:** "Which task management tool should I use for tracking work?"
 
 **Options:**
-1. **Built-in Tasks (default)** - Use Copilot CLI's native TaskCreate/TodoWrite. Tasks are session-only.
+1. **Built-in Tasks (default)** - Use Claude Code's native TaskCreate/TodoWrite. Tasks are session-only.
 2. **Beads (bd)** - Git-backed persistent tasks. Survives across sessions. [Only if detected]
 3. **Beads-Rust (br)** - Lightweight Rust port of beads. [Only if detected]
 
@@ -224,5 +209,5 @@ echo "Task tool set to: USER_CHOICE"
 
 ```bash
 CONFIG_TYPE=$(jq -r '.configType // "unknown"' ".omcp/state/setup-state.json" 2>/dev/null || echo "unknown")
-bash "${COPILOT_PLUGIN_ROOT}/scripts/setup-progress.sh" save 4 "$CONFIG_TYPE"
+bash "${CLAUDE_PLUGIN_ROOT}/scripts/setup-progress.sh" save 4 "$CONFIG_TYPE"
 ```

package/skills/omc-setup/phases/03-integrations.md

@@ -2,27 +2,15 @@
 
 **Skip condition**: If resuming and `lastCompletedStep >= 6`, skip this entire phase.
 
-## Quick Mode Behavior
-
-If `SETUP_MODE=quick`:
-- **Step 3.1 (Verify plugin)**: Run automatically (no prompt)
-- **Step 3.2 (MCP servers)**: **Always offer** — go straight to MCP configuration without asking "would you like to configure MCP servers?" (jump directly to invoking `/oh-my-copilot:mcp-setup`)
-- **Step 3.3 (Team defaults)**: **Skip** — use defaults (3 agents, executor type)
-- **Azure DevOps**: Still auto-detect and recommend if ADO repo detected
-
-Then save progress and continue to Phase 4. The rest of this file documents the **interactive mode** behavior.
-
----
-
 ## Step 3.1: Verify Plugin Installation
 
 ```bash
-grep -q "oh-my-copilot" ~/.copilot/settings.json && echo "Plugin verified" || echo "Plugin NOT found - run: copilot /install-plugin oh-my-copilot"
+grep -q "oh-my-copilot" "${COPILOT_CONFIG_DIR:-$HOME/.copilot}/settings.json" && echo "Plugin verified" || echo "Plugin NOT found - run: claude /install-plugin oh-my-copilot"
 ```
 
 ## Step 3.2: Offer MCP Server Configuration
 
-MCP servers extend Copilot CLI with additional tools (web search, GitHub, etc.).
+MCP servers extend Claude Code with additional tools (web search, GitHub, etc.).
 
 Use AskUserQuestion: "Would you like to configure MCP servers for enhanced capabilities? (Context7, Exa search, GitHub, etc.)"
 
@@ -35,20 +23,86 @@ If no, skip to next step.
 
 ## Step 3.3: Configure Agent Teams (Optional)
 
-Agent teams let you spawn N coordinated agents working on a shared task list with inter-agent messaging. **Teams are enabled by default** in oh-my-copilot — no additional configuration is needed to use them.
+Agent teams are an experimental Claude Code feature that lets you spawn N coordinated agents working on a shared task list with inter-agent messaging. **Teams are disabled by default** and require enabling via `settings.json`.
+
+Reference: https://code.claude.com/docs/en/agent-teams
+
+Use AskUserQuestion:
+
+**Question:** "Would you like to enable agent teams? Teams let you spawn coordinated agents (e.g., `/team 3:executor 'fix all errors'`). This is an experimental Claude Code feature."
+
+**Options:**
+1. **Yes, enable teams (Recommended)** - Enable the experimental feature and configure defaults
+2. **No, skip** - Leave teams disabled (can enable later)
+
+### If User Chooses YES:
+
+#### 3.3.1: Enable Agent Teams in settings.json
+
+**CRITICAL**: Agent teams require `CLAUDE_CODE_EXPERIMENTAL_AGENT_TEAMS` to be set in `~/.copilot/settings.json`. This must be done carefully to preserve existing user settings.
+
+First, read the current settings.json:
+
+```bash
+SETTINGS_FILE="${COPILOT_CONFIG_DIR:-$HOME/.copilot}/settings.json"
+
+if [ -f "$SETTINGS_FILE" ]; then
+  echo "Current settings.json found"
+  cat "$SETTINGS_FILE"
+else
+  echo "No settings.json found - will create one"
+fi
+```
+
+Then use the Read tool to read `${COPILOT_CONFIG_DIR:-~/.copilot}/settings.json` (if it exists). Use the Edit tool to merge the teams configuration while preserving ALL existing settings.
+
+Use jq to safely merge without overwriting existing settings:
+
+```bash
+SETTINGS_FILE="${COPILOT_CONFIG_DIR:-$HOME/.copilot}/settings.json"
+
+if [ -f "$SETTINGS_FILE" ]; then
+  TEMP_FILE=$(mktemp)
+  jq '.env = (.env // {} | . + {"CLAUDE_CODE_EXPERIMENTAL_AGENT_TEAMS": "1"})' "$SETTINGS_FILE" > "$TEMP_FILE" && mv "$TEMP_FILE" "$SETTINGS_FILE"
+  echo "Added CLAUDE_CODE_EXPERIMENTAL_AGENT_TEAMS to existing settings.json"
+else
+  mkdir -p "$(dirname "$SETTINGS_FILE")"
+  cat > "$SETTINGS_FILE" << 'SETTINGS_EOF'
+{
+  "env": {
+    "CLAUDE_CODE_EXPERIMENTAL_AGENT_TEAMS": "1"
+  }
+}
+SETTINGS_EOF
+  echo "Created settings.json with teams enabled"
+fi
+```
+
+**IMPORTANT**: The Edit tool is preferred for modifying settings.json when possible, since it preserves formatting and comments. The jq approach above is the fallback for when the file needs structural merging.
+
+#### 3.3.2: Configure Teammate Display Mode
 
 Use AskUserQuestion:
 
-**Question:** "Would you like to customize team defaults? (e.g., `/team 3:executor 'fix all errors'`)"
+**Question:** "How should teammates be displayed?"
 
 **Options:**
-1. **Keep defaults (Recommended)** - 3 agents, executor type
-2. **Customize** - Choose agent count and default type
-3. **Skip** - Move on
+1. **Auto (Recommended)** - Uses split panes if in tmux, otherwise in-process. Best for most users.
+2. **In-process** - All teammates in your main terminal. Use Shift+Up/Down to select. Works everywhere.
+3. **Split panes (tmux)** - Each teammate in its own pane. Requires tmux or iTerm2.
+
+If user chooses anything other than "Auto", add `teammateMode` to settings.json:
+
+```bash
+SETTINGS_FILE="${COPILOT_CONFIG_DIR:-$HOME/.copilot}/settings.json"
 
-### If User Chooses Customize:
+# TEAMMATE_MODE is "in-process" or "tmux" based on user choice
+# Skip this if user chose "Auto" (that's the default)
+jq --arg mode "TEAMMATE_MODE" '. + {teammateMode: $mode}' "$SETTINGS_FILE" > "${SETTINGS_FILE}.tmp" && mv "${SETTINGS_FILE}.tmp" "$SETTINGS_FILE"
+echo "Teammate display mode set to: TEAMMATE_MODE"
+```
 
-#### 3.3.1: Configure Team Defaults in omc-config
+#### 3.3.3: Configure Team Defaults in omc-config
 
 Use AskUserQuestion with multiple questions:
 
@@ -66,7 +120,7 @@ Use AskUserQuestion with multiple questions:
 2. **codex** - Use Codex CLI workers by default when installed
 3. **gemini** - Use Gemini CLI workers by default when installed
 
-Store the team configuration in `~/.copilot/.omc-config.json`:
+Store the team configuration in `~/.copilot/.omcp-config.json`:
 
 ```bash
 CONFIG_FILE="${COPILOT_CONFIG_DIR:-$HOME/.copilot}/.omc-config.json"
@@ -90,72 +144,49 @@ echo "  Default provider: AGENT_TYPE"
 echo "  Model: teammates inherit your session model"
 ```
 
-#### Verify Configuration
+**Note:** Teammates do not have a separate model default. Each teammate is a full Claude Code session that inherits your configured model. Subagents spawned by teammates can use any model tier.
 
-After modifications, verify the config is valid:
+#### Verify settings.json Integrity
+
+After all modifications, verify settings.json is valid JSON and contains the expected keys:
 
 ```bash
-CONFIG_FILE="${COPILOT_CONFIG_DIR:-$HOME/.copilot}/.omc-config.json"
+SETTINGS_FILE="${COPILOT_CONFIG_DIR:-$HOME/.copilot}/settings.json"
 
-if [ -f "$CONFIG_FILE" ]; then
-  echo "Team configuration:"
-  jq '.team' "$CONFIG_FILE"
+if jq empty "$SETTINGS_FILE" 2>/dev/null; then
+  echo "settings.json: valid JSON"
 else
-  echo "Using default team settings (3 agents, executor type)"
+  echo "ERROR: settings.json is invalid JSON! Restoring from backup..."
+  exit 1
 fi
-```
-
-### If User Chooses Keep Defaults or Skip:
 
-Skip this step. Default team configuration (3 agents, executor type) will be used. User can customize later by running `/oh-my-copilot:omc-setup --force`.
-
-## Azure DevOps Integrations (when ADO repo detected)
-
-If the current repository is hosted on Azure DevOps (detected via git remote URL containing `dev.azure.com` or `visualstudio.com`), recommend the following:
-
-### Azure DevOps MCP Server
-For enhanced ADO integration with MCP tools (work items, repos, pipelines, wiki, test plans):
+if jq -e '.env.CLAUDE_CODE_EXPERIMENTAL_AGENT_TEAMS' "$SETTINGS_FILE" > /dev/null 2>&1; then
+  echo "Agent teams: ENABLED"
+else
+  echo "WARNING: Agent teams env var not found in settings.json"
+fi
 
-```bash
-# Install azure-devops-mcp server
-# See: https://github.com/microsoft/azure-devops-mcp
+echo ""
+echo "Final settings.json:"
+jq '.' "$SETTINGS_FILE"
 ```
 
-Add to your `.mcp.json` or Copilot CLI MCP configuration:
+### If User Chooses NO:
+
+Skip this step. Agent teams will remain disabled. User can enable later by adding to `~/.copilot/settings.json`:
 ```json
 {
-  "mcpServers": {
-    "azure-devops": {
-      "command": "npx",
-      "args": ["-y", "@microsoft/azure-devops-mcp"],
-      "env": {
-        "AZURE_DEVOPS_ORG": "https://dev.azure.com/{your-org}",
-        "AZURE_DEVOPS_PROJECT": "{your-project}"
-      }
-    }
+  "env": {
+    "CLAUDE_CODE_EXPERIMENTAL_AGENT_TEAMS": "1"
   }
 }
 ```
 
-### Azure Skills Plugin (for Azure cloud operations)
-If you work with Azure cloud services beyond DevOps (compute, storage, AI, networking, security, deployment), install the azure-skills plugin:
-
-```bash
-# Install azure-skills plugin for Copilot CLI
-copilot plugin install microsoft/azure-skills
-```
-
-This provides 24 specialized skills for Azure cloud operations. oh-my-copilot handles ADO orchestration; azure-skills handles the Azure cloud layer. They are complementary.
-
-### Run ADO Setup
-After installing the MCP server, configure your project:
-```
-/oh-my-copilot:omc-ado-setup
-```
+Or by running `/oh-my-copilot:omc-setup --force` and choosing to enable teams.
 
 ## Save Progress
 
 ```bash
 CONFIG_TYPE=$(jq -r '.configType // "unknown"' ".omcp/state/setup-state.json" 2>/dev/null || echo "unknown")
-bash "${COPILOT_PLUGIN_ROOT}/scripts/setup-progress.sh" save 6 "$CONFIG_TYPE"
+bash "${CLAUDE_PLUGIN_ROOT}/scripts/setup-progress.sh" save 6 "$CONFIG_TYPE"
 ```

package/skills/omc-setup/phases/04-welcome.md

@@ -1,50 +1,108 @@
 # Phase 4: Completion
 
+## Detect Upgrade from 2.x
+
+Check if user has existing 2.x configuration:
+
+```bash
+ls "${COPILOT_CONFIG_DIR:-$HOME/.copilot}"/commands/ralph-loop.md 2>/dev/null || ls "${COPILOT_CONFIG_DIR:-$HOME/.copilot}"/commands/ultrawork.md 2>/dev/null
+```
+
+If found, this is an upgrade from 2.x. Set `IS_UPGRADE=true`.
+
 ## Show Welcome Message
 
-Display this exact output as a code block:
+### For New Users (IS_UPGRADE is not true):
 
 ```
-   ██████╗ ██╗  ██╗     ███╗   ███╗██╗   ██╗
-  ██╔═══██╗██║  ██║     ████╗ ████║╚██╗ ██╔╝
-  ██║   ██║███████║     ██╔████╔██║ ╚████╔╝
-  ██║   ██║██╔══██║     ██║╚██╔╝██║  ╚██╔╝
-  ╚██████╔╝██║  ██║     ██║ ╚═╝ ██║   ██║
-   ╚═════╝ ╚═╝  ╚═╝     ╚═╝     ╚═╝   ╚═╝
-             ██████╗ ██████╗ ██████╗ ██╗██╗      ██████╗ ████████╗
-            ██╔════╝██╔═══██╗██╔══██╗██║██║     ██╔═══██╗╚══██╔══╝
-            ██║     ██║   ██║██████╔╝██║██║     ██║   ██║   ██║
-            ██║     ██║   ██║██╔═══╝ ██║██║     ██║   ██║   ██║
-            ╚██████╗╚██████╔╝██║     ██║███████╗╚██████╔╝   ██║
-             ╚═════╝ ╚═════╝ ╚═╝     ╚═╝╚══════╝ ╚═════╝    ╚═╝
-     Turbocharge your Copilot CLI with multi-agent orchestration
-
-  ┌──────────────────────────────────────────────────────────────┐
-  │  /autopilot          Autonomous end-to-end execution       │
-  │  /plan               Strategic planning with interview      │
-  │  /team N             Parallel coordinated agents            │
-  │  /review             Run code review                       │
-  │  /ai-slop-cleaner    Clean AI-generated code slop           │
-  │  /simplify           Simplify the code, and fix issues      │
-  │  /ralph              Loop until task is complete            │
-  │  /deepinit           Deep codebase initialization           │
-  │  /cancel             Stop any active mode                   │
-  │  /omc-setup          Interactive setup wizard               │
-  └──────────────────────────────────────────────────────────────┘
-
-  Type '/autopilot create a todo-app' to engage the magic dust!
+OMC Setup Complete!
+
+You don't need to learn any commands. I now have intelligent behaviors that activate automatically.
+
+WHAT HAPPENS AUTOMATICALLY:
+- Complex tasks -> I parallelize and delegate to specialists
+- "plan this" -> I start a planning interview
+- "don't stop until done" -> I persist until verified complete
+- "stop" or "cancel" -> I intelligently stop current operation
+
+MAGIC KEYWORDS (optional power-user shortcuts):
+Just include these words naturally in your request:
+
+| Keyword | Effect | Example |
+|---------|--------|---------|
+| ralph | Persistence mode | "ralph: fix the auth bug" |
+| ralplan | Iterative planning | "ralplan this feature" |
+| ulw | Max parallelism | "ulw refactor the API" |
+| plan | Planning interview | "plan the new endpoints" |
+| team | Coordinated agents | "/team 3:executor fix errors" |
+
+**ralph includes ultrawork:** When you activate ralph mode, it automatically includes ultrawork's parallel execution. No need to combine keywords.
+
+TEAMS:
+Spawn coordinated agents with shared task lists and real-time messaging:
+- /oh-my-copilot:team 3:executor "fix all TypeScript errors"
+- /oh-my-copilot:team 5:debugger "fix build errors in src/"
+Teams use Claude Code native tools (TeamCreate/SendMessage/TaskCreate).
+
+MCP SERVERS:
+Run /oh-my-copilot:mcp-setup to add tools like web search, GitHub, etc.
+
+HUD STATUSLINE:
+The status bar now shows OMC state. Restart Claude Code to see it.
+
+OMC CLI HELPERS (if installed):
+- omc hud         - Render the current HUD statusline
+- omc teleport    - Create an isolated git worktree
+- omc team status - Inspect a running team job
+- Session summaries are written to `.omcp/sessions/*.json`
+
+That's it! Just use Claude Code normally.
 ```
 
-Then show this below the banner:
+### For Users Upgrading from 2.x (IS_UPGRADE is true):
 
 ```
+OMC Setup Complete! (Upgraded from 2.x)
+
+GOOD NEWS: Your existing commands still work!
+- /ralph, /ultrawork, /omc-plan, etc. all still function
+
+WHAT'S NEW in 3.0:
+You no longer NEED those commands. Everything is automatic now:
+- Just say "don't stop until done" instead of /ralph
+- Just say "fast" or "parallel" instead of /ultrawork
+- Just say "plan this" instead of /omc-plan
+- Just say "stop" instead of /cancel
+
+MAGIC KEYWORDS (power-user shortcuts):
+| Keyword | Same as old... | Example |
+|---------|----------------|---------|
+| ralph | /ralph | "ralph: fix the bug" |
+| ralplan | /ralplan | "ralplan this feature" |
+| ulw | /ultrawork | "ulw refactor API" |
+| omc-plan | /omc-plan | "plan the endpoints" |
+| team | (new!) | "/team 3:executor fix errors" |
+
+TEAMS (NEW!):
+Spawn coordinated agents with shared task lists and real-time messaging:
+- /oh-my-copilot:team 3:executor "fix all TypeScript errors"
+- Uses Claude Code native tools (TeamCreate/SendMessage/TaskCreate)
+
 HUD STATUSLINE:
-The status bar now shows OMC state. Restart Copilot CLI to see it.
+The status bar now shows OMC state. Restart Claude Code to see it.
+
+OMC CLI HELPERS (if installed):
+- omc hud         - Render the current HUD statusline
+- omc teleport    - Create an isolated git worktree
+- omc team status - Inspect a running team job
+- Session summaries are written to `.omcp/sessions/*.json`
+
+Your workflow won't break - it just got easier!
 ```
 
 ## Optional Rule Templates
 
-OMC includes rule templates you can copy to your project's `.copilot/rules/` directory for automatic context injection:
+OMC includes rule templates you can copy to your project's `.claude/rules/` directory for automatic context injection:
 
 | Template | Purpose |
 |----------|---------|
@@ -57,8 +115,8 @@ OMC includes rule templates you can copy to your project's `.copilot/rules/` dir
 
 Copy with:
 ```bash
-mkdir -p .copilot/rules
-cp "${COPILOT_PLUGIN_ROOT}/templates/rules/"*.md .copilot/rules/
+mkdir -p .claude/rules
+cp "${CLAUDE_PLUGIN_ROOT}/templates/rules/"*.md .claude/rules/
 ```
 
 See `templates/rules/README.md` for details.
@@ -76,7 +134,7 @@ gh auth status &>/dev/null
 **Before prompting, check if the repository is already starred:**
 
 ```bash
-gh api user/starred/RobinNorberg/oh-my-copilot &>/dev/null
+gh api user/starred/Yeachan-Heo/oh-my-copilot &>/dev/null
 ```
 
 **If already starred (exit code 0):**
@@ -97,7 +155,7 @@ Use AskUserQuestion:
 If user chooses "Yes, star it!":
 
 ```bash
-gh api -X PUT /user/starred/RobinNorberg/oh-my-copilot 2>/dev/null && echo "Thanks for starring!" || true
+gh api -X PUT /user/starred/Yeachan-Heo/oh-my-copilot 2>/dev/null && echo "Thanks for starring!" || true
 ```
 
 **Note:** Fail silently if the API call doesn't work - never block setup completion.
@@ -107,7 +165,7 @@ gh api -X PUT /user/starred/RobinNorberg/oh-my-copilot 2>/dev/null && echo "Than
 ```bash
 echo ""
 echo "If you enjoy oh-my-copilot, consider starring the repo:"
-echo "  https://github.com/RobinNorberg/oh-my-copilot"
+echo "  https://github.com/Yeachan-Heo/oh-my-copilot"
 echo ""
 ```
 
@@ -116,19 +174,19 @@ echo ""
 Get the current OMC version and mark setup complete:
 
 ```bash
-# Get current OMC version from copilot-instructions.md
+# Get current OMC version from CLAUDE.md
 OMC_VERSION=""
-if [ -f ".copilot/copilot-instructions.md" ]; then
-  OMC_VERSION=$(grep -m1 'OMC:VERSION:' .copilot/copilot-instructions.md 2>/dev/null | sed -E 's/.*OMC:VERSION:([^ ]+).*/\1/' || true)
-elif [ -f "${COPILOT_CONFIG_DIR:-$HOME/.copilot}/copilot-instructions.md" ]; then
-  OMC_VERSION=$(grep -m1 'OMC:VERSION:' "${COPILOT_CONFIG_DIR:-$HOME/.copilot}/copilot-instructions.md" 2>/dev/null | sed -E 's/.*OMC:VERSION:([^ ]+).*/\1/' || true)
+if [ -f ".claude/CLAUDE.md" ]; then
+  OMC_VERSION=$(grep -m1 'OMC:VERSION:' .claude/CLAUDE.md 2>/dev/null | sed -E 's/.*OMC:VERSION:([^ ]+).*/\1/' || true)
+elif [ -f "${COPILOT_CONFIG_DIR:-$HOME/.copilot}/CLAUDE.md" ]; then
+  OMC_VERSION=$(grep -m1 'OMC:VERSION:' "${COPILOT_CONFIG_DIR:-$HOME/.copilot}/CLAUDE.md" 2>/dev/null | sed -E 's/.*OMC:VERSION:([^ ]+).*/\1/' || true)
 fi
 if [ -z "$OMC_VERSION" ]; then
-  OMC_VERSION=$(omcp --version 2>/dev/null | head -1 || true)
+  OMC_VERSION=$(omc --version 2>/dev/null | head -1 || true)
 fi
 if [ -z "$OMC_VERSION" ]; then
   OMC_VERSION="unknown"
 fi
 
-bash "${COPILOT_PLUGIN_ROOT}/scripts/setup-progress.sh" complete "$OMC_VERSION"
+bash "${CLAUDE_PLUGIN_ROOT}/scripts/setup-progress.sh" complete "$OMC_VERSION"
 ```