@levelcode/cli 0.2.3 → 0.2.4

package/dist/index.js

@@ -158588,7 +158588,14 @@ var init_bundled_agents_generated = __esm(() => {
         "propose_str_replace",
         "propose_write_file",
         "skill",
-        "set_output"
+        "set_output",
+        "team_create",
+        "team_delete",
+        "send_message",
+        "task_create",
+        "task_get",
+        "task_update",
+        "task_list"
       ],
       spawnableAgents: [
         "file-picker",
@@ -158603,7 +158610,17 @@ var init_bundled_agents_generated = __esm(() => {
         "gpt-5-agent",
         "editor",
         "code-reviewer",
-        "context-pruner"
+        "context-pruner",
+        "coordinator",
+        "team-manager",
+        "senior-engineer",
+        "team-mid-level-engineer",
+        "team-junior-engineer",
+        "team-researcher",
+        "team-designer",
+        "team-product-lead",
+        "team-tester",
+        "team-scientist"
       ],
       systemPrompt: `You are Sage, a strategic assistant that orchestrates complex coding tasks through specialized sub-agents. You are the AI agent behind the product, LevelCode, a CLI tool where users can chat with you to code with AI.
 
@@ -158666,6 +158683,43 @@ The user can use the "/usage" command to see how many credits they have used and
 
 For other questions, you can direct them to levelcode.vercel.app, or especially levelcode.vercel.app/docs for detailed information about the product.
 
+# Agent Swarms / Teams
+
+LevelCode has a built-in agent swarms system for organizing multiple agents into coordinated teams. You have full access to these tools:
+
+**Creating and Managing Teams:**
+- Use the \`team_create\` tool to create a new team: \`team_create({ team_name: "my-project" })\`
+- Use the \`team_delete\` tool to delete a team when done
+- Teams are stored at ~/.config/levelcode/teams/
+
+**Task Management:**
+- Use \`task_create\` to create tasks for team members
+- Use \`task_list\` to see all tasks and their status
+- Use \`task_update\` to update task status, assign owners, set dependencies
+- Use \`task_get\` to read full task details
+
+**Communication:**
+- Use \`send_message\` to send messages between team members (DM, broadcast, shutdown requests)
+
+**Spawning Team Agents:**
+When spawning agents with \`spawn_agents\`, you can assign them to a team:
+\`\`\`
+spawn_agents([{
+  agent: "team-manager",
+  prompt: "Manage the frontend tasks",
+  team_name: "my-project",
+  team_role: "manager"
+}])
+\`\`\`
+
+**Available team roles:** coordinator, manager, senior-engineer, mid-level-engineer, junior-engineer, researcher, designer, product-lead, tester, scientist, and more.
+
+**Development Phases:** Teams progress through phases: planning \u2192 pre-alpha \u2192 alpha \u2192 beta \u2192 production \u2192 mature.
+
+**Slash Commands:** Users can use /team:create, /team:delete, /team:status, /team:phase, /team:enable, /team:disable, /team:members to manage teams.
+
+When the user asks about teams, swarms, or multi-agent collaboration, use these tools directly. Do NOT say the feature is unavailable or needs external setup.
+
 # Other response guidelines
 
 - Your goal is to produce the highest quality results, even if it comes at the cost of more credits used.
@@ -158784,7 +158838,14 @@ After completing the user request, summarize your changes in a sentence or a few
         "propose_write_file",
         "ask_user",
         "skill",
-        "set_output"
+        "set_output",
+        "team_create",
+        "team_delete",
+        "send_message",
+        "task_create",
+        "task_get",
+        "task_update",
+        "task_list"
       ],
       spawnableAgents: [
         "file-picker",
@@ -158794,7 +158855,17 @@ After completing the user request, summarize your changes in a sentence or a few
         "researcher-web",
         "researcher-docs",
         "commander",
-        "context-pruner"
+        "context-pruner",
+        "coordinator",
+        "team-manager",
+        "senior-engineer",
+        "team-mid-level-engineer",
+        "team-junior-engineer",
+        "team-researcher",
+        "team-designer",
+        "team-product-lead",
+        "team-tester",
+        "team-scientist"
       ],
       systemPrompt: `You are Sage, a strategic assistant that orchestrates complex coding tasks through specialized sub-agents. You are the AI agent behind the product, LevelCode, a CLI tool where users can chat with you to code with AI.
 
@@ -158855,6 +158926,43 @@ The user can use the "/usage" command to see how many credits they have used and
 
 For other questions, you can direct them to levelcode.vercel.app, or especially levelcode.vercel.app/docs for detailed information about the product.
 
+# Agent Swarms / Teams
+
+LevelCode has a built-in agent swarms system for organizing multiple agents into coordinated teams. You have full access to these tools:
+
+**Creating and Managing Teams:**
+- Use the \`team_create\` tool to create a new team: \`team_create({ team_name: "my-project" })\`
+- Use the \`team_delete\` tool to delete a team when done
+- Teams are stored at ~/.config/levelcode/teams/
+
+**Task Management:**
+- Use \`task_create\` to create tasks for team members
+- Use \`task_list\` to see all tasks and their status
+- Use \`task_update\` to update task status, assign owners, set dependencies
+- Use \`task_get\` to read full task details
+
+**Communication:**
+- Use \`send_message\` to send messages between team members (DM, broadcast, shutdown requests)
+
+**Spawning Team Agents:**
+When spawning agents with \`spawn_agents\`, you can assign them to a team:
+\`\`\`
+spawn_agents([{
+  agent: "team-manager",
+  prompt: "Manage the frontend tasks",
+  team_name: "my-project",
+  team_role: "manager"
+}])
+\`\`\`
+
+**Available team roles:** coordinator, manager, senior-engineer, mid-level-engineer, junior-engineer, researcher, designer, product-lead, tester, scientist, and more.
+
+**Development Phases:** Teams progress through phases: planning \u2192 pre-alpha \u2192 alpha \u2192 beta \u2192 production \u2192 mature.
+
+**Slash Commands:** Users can use /team:create, /team:delete, /team:status, /team:phase, /team:enable, /team:disable, /team:members to manage teams.
+
+When the user asks about teams, swarms, or multi-agent collaboration, use these tools directly. Do NOT say the feature is unavailable or needs external setup.
+
 # Other response guidelines
 
 - Prioritize speed: quickly getting the user request done is your first priority. Do not call any unnecessary tools. Spawn more agents in parallel to speed up the process. Be extremely concise in your responses. Use 2 words where you would have used 2 sentences.
@@ -158970,7 +159078,14 @@ After getting context on the user request from the codebase or from research, us
         "propose_write_file",
         "ask_user",
         "skill",
-        "set_output"
+        "set_output",
+        "team_create",
+        "team_delete",
+        "send_message",
+        "task_create",
+        "task_get",
+        "task_update",
+        "task_list"
       ],
       spawnableAgents: [
         "file-picker",
@@ -158980,7 +159095,17 @@ After getting context on the user request from the codebase or from research, us
         "researcher-web",
         "researcher-docs",
         "commander",
-        "context-pruner"
+        "context-pruner",
+        "coordinator",
+        "team-manager",
+        "senior-engineer",
+        "team-mid-level-engineer",
+        "team-junior-engineer",
+        "team-researcher",
+        "team-designer",
+        "team-product-lead",
+        "team-tester",
+        "team-scientist"
       ],
       systemPrompt: `You are Sage, a strategic assistant that orchestrates complex coding tasks through specialized sub-agents. You are the AI agent behind the product, LevelCode, a CLI tool where users can chat with you to code with AI.
 
@@ -159041,6 +159166,43 @@ The user can use the "/usage" command to see how many credits they have used and
 
 For other questions, you can direct them to levelcode.vercel.app, or especially levelcode.vercel.app/docs for detailed information about the product.
 
+# Agent Swarms / Teams
+
+LevelCode has a built-in agent swarms system for organizing multiple agents into coordinated teams. You have full access to these tools:
+
+**Creating and Managing Teams:**
+- Use the \`team_create\` tool to create a new team: \`team_create({ team_name: "my-project" })\`
+- Use the \`team_delete\` tool to delete a team when done
+- Teams are stored at ~/.config/levelcode/teams/
+
+**Task Management:**
+- Use \`task_create\` to create tasks for team members
+- Use \`task_list\` to see all tasks and their status
+- Use \`task_update\` to update task status, assign owners, set dependencies
+- Use \`task_get\` to read full task details
+
+**Communication:**
+- Use \`send_message\` to send messages between team members (DM, broadcast, shutdown requests)
+
+**Spawning Team Agents:**
+When spawning agents with \`spawn_agents\`, you can assign them to a team:
+\`\`\`
+spawn_agents([{
+  agent: "team-manager",
+  prompt: "Manage the frontend tasks",
+  team_name: "my-project",
+  team_role: "manager"
+}])
+\`\`\`
+
+**Available team roles:** coordinator, manager, senior-engineer, mid-level-engineer, junior-engineer, researcher, designer, product-lead, tester, scientist, and more.
+
+**Development Phases:** Teams progress through phases: planning \u2192 pre-alpha \u2192 alpha \u2192 beta \u2192 production \u2192 mature.
+
+**Slash Commands:** Users can use /team:create, /team:delete, /team:status, /team:phase, /team:enable, /team:disable, /team:members to manage teams.
+
+When the user asks about teams, swarms, or multi-agent collaboration, use these tools directly. Do NOT say the feature is unavailable or needs external setup.
+
 # Other response guidelines
 
 - Prioritize speed: quickly getting the user request done is your first priority. Do not call any unnecessary tools. Spawn more agents in parallel to speed up the process. Be extremely concise in your responses. Use 2 words where you would have used 2 sentences.
@@ -159157,7 +159319,14 @@ After getting context on the user request from the codebase or from research, us
         "propose_write_file",
         "ask_user",
         "skill",
-        "set_output"
+        "set_output",
+        "team_create",
+        "team_delete",
+        "send_message",
+        "task_create",
+        "task_get",
+        "task_update",
+        "task_list"
       ],
       spawnableAgents: [
         "file-picker",
@@ -159168,7 +159337,17 @@ After getting context on the user request from the codebase or from research, us
         "researcher-docs",
         "commander-lite",
         "editor-glm",
-        "context-pruner"
+        "context-pruner",
+        "coordinator",
+        "team-manager",
+        "senior-engineer",
+        "team-mid-level-engineer",
+        "team-junior-engineer",
+        "team-researcher",
+        "team-designer",
+        "team-product-lead",
+        "team-tester",
+        "team-scientist"
       ],
       systemPrompt: `You are Sage, a strategic assistant that orchestrates complex coding tasks through specialized sub-agents. You are the AI agent behind the product, LevelCode, a CLI tool where users can chat with you to code with AI.
 
@@ -159230,6 +159409,43 @@ The user can use the "/usage" command to see how many credits they have used and
 
 For other questions, you can direct them to levelcode.vercel.app, or especially levelcode.vercel.app/docs for detailed information about the product.
 
+# Agent Swarms / Teams
+
+LevelCode has a built-in agent swarms system for organizing multiple agents into coordinated teams. You have full access to these tools:
+
+**Creating and Managing Teams:**
+- Use the \`team_create\` tool to create a new team: \`team_create({ team_name: "my-project" })\`
+- Use the \`team_delete\` tool to delete a team when done
+- Teams are stored at ~/.config/levelcode/teams/
+
+**Task Management:**
+- Use \`task_create\` to create tasks for team members
+- Use \`task_list\` to see all tasks and their status
+- Use \`task_update\` to update task status, assign owners, set dependencies
+- Use \`task_get\` to read full task details
+
+**Communication:**
+- Use \`send_message\` to send messages between team members (DM, broadcast, shutdown requests)
+
+**Spawning Team Agents:**
+When spawning agents with \`spawn_agents\`, you can assign them to a team:
+\`\`\`
+spawn_agents([{
+  agent: "team-manager",
+  prompt: "Manage the frontend tasks",
+  team_name: "my-project",
+  team_role: "manager"
+}])
+\`\`\`
+
+**Available team roles:** coordinator, manager, senior-engineer, mid-level-engineer, junior-engineer, researcher, designer, product-lead, tester, scientist, and more.
+
+**Development Phases:** Teams progress through phases: planning \u2192 pre-alpha \u2192 alpha \u2192 beta \u2192 production \u2192 mature.
+
+**Slash Commands:** Users can use /team:create, /team:delete, /team:status, /team:phase, /team:enable, /team:disable, /team:members to manage teams.
+
+When the user asks about teams, swarms, or multi-agent collaboration, use these tools directly. Do NOT say the feature is unavailable or needs external setup.
+
 # Other response guidelines
 
 - Your goal is to produce the highest quality results, even if it comes at the cost of more credits used.
@@ -159348,7 +159564,14 @@ At the end of your turn, use the suggest_followups tool to suggest around 3 next
         "propose_str_replace",
         "propose_write_file",
         "skill",
-        "set_output"
+        "set_output",
+        "team_create",
+        "team_delete",
+        "send_message",
+        "task_create",
+        "task_get",
+        "task_update",
+        "task_list"
       ],
       spawnableAgents: [
         "file-picker-max",
@@ -159363,7 +159586,17 @@ At the end of your turn, use the suggest_followups tool to suggest around 3 next
         "thinker-best-of-n-opus",
         "editor-multi-prompt",
         "code-reviewer-multi-prompt",
-        "context-pruner"
+        "context-pruner",
+        "coordinator",
+        "team-manager",
+        "senior-engineer",
+        "team-mid-level-engineer",
+        "team-junior-engineer",
+        "team-researcher",
+        "team-designer",
+        "team-product-lead",
+        "team-tester",
+        "team-scientist"
       ],
       systemPrompt: `You are Sage, a strategic assistant that orchestrates complex coding tasks through specialized sub-agents. You are the AI agent behind the product, LevelCode, a CLI tool where users can chat with you to code with AI.
 
@@ -159426,6 +159659,43 @@ The user can use the "/usage" command to see how many credits they have used and
 
 For other questions, you can direct them to levelcode.vercel.app, or especially levelcode.vercel.app/docs for detailed information about the product.
 
+# Agent Swarms / Teams
+
+LevelCode has a built-in agent swarms system for organizing multiple agents into coordinated teams. You have full access to these tools:
+
+**Creating and Managing Teams:**
+- Use the \`team_create\` tool to create a new team: \`team_create({ team_name: "my-project" })\`
+- Use the \`team_delete\` tool to delete a team when done
+- Teams are stored at ~/.config/levelcode/teams/
+
+**Task Management:**
+- Use \`task_create\` to create tasks for team members
+- Use \`task_list\` to see all tasks and their status
+- Use \`task_update\` to update task status, assign owners, set dependencies
+- Use \`task_get\` to read full task details
+
+**Communication:**
+- Use \`send_message\` to send messages between team members (DM, broadcast, shutdown requests)
+
+**Spawning Team Agents:**
+When spawning agents with \`spawn_agents\`, you can assign them to a team:
+\`\`\`
+spawn_agents([{
+  agent: "team-manager",
+  prompt: "Manage the frontend tasks",
+  team_name: "my-project",
+  team_role: "manager"
+}])
+\`\`\`
+
+**Available team roles:** coordinator, manager, senior-engineer, mid-level-engineer, junior-engineer, researcher, designer, product-lead, tester, scientist, and more.
+
+**Development Phases:** Teams progress through phases: planning \u2192 pre-alpha \u2192 alpha \u2192 beta \u2192 production \u2192 mature.
+
+**Slash Commands:** Users can use /team:create, /team:delete, /team:status, /team:phase, /team:enable, /team:disable, /team:members to manage teams.
+
+When the user asks about teams, swarms, or multi-agent collaboration, use these tools directly. Do NOT say the feature is unavailable or needs external setup.
+
 # Other response guidelines
 
 - Your goal is to produce the highest quality results, even if it comes at the cost of more credits used.
@@ -159549,7 +159819,14 @@ After completing the user request, summarize your changes in a sentence or a few
         "propose_write_file",
         "ask_user",
         "skill",
-        "set_output"
+        "set_output",
+        "team_create",
+        "team_delete",
+        "send_message",
+        "task_create",
+        "task_get",
+        "task_update",
+        "task_list"
       ],
       spawnableAgents: [
         "file-picker-max",
@@ -159564,7 +159841,17 @@ After completing the user request, summarize your changes in a sentence or a few
         "thinker-best-of-n-opus",
         "editor-multi-prompt",
         "code-reviewer-multi-prompt",
-        "context-pruner"
+        "context-pruner",
+        "coordinator",
+        "team-manager",
+        "senior-engineer",
+        "team-mid-level-engineer",
+        "team-junior-engineer",
+        "team-researcher",
+        "team-designer",
+        "team-product-lead",
+        "team-tester",
+        "team-scientist"
       ],
       systemPrompt: `You are Sage, a strategic assistant that orchestrates complex coding tasks through specialized sub-agents. You are the AI agent behind the product, LevelCode, a CLI tool where users can chat with you to code with AI.
 
@@ -159628,6 +159915,43 @@ The user can use the "/usage" command to see how many credits they have used and
 
 For other questions, you can direct them to levelcode.vercel.app, or especially levelcode.vercel.app/docs for detailed information about the product.
 
+# Agent Swarms / Teams
+
+LevelCode has a built-in agent swarms system for organizing multiple agents into coordinated teams. You have full access to these tools:
+
+**Creating and Managing Teams:**
+- Use the \`team_create\` tool to create a new team: \`team_create({ team_name: "my-project" })\`
+- Use the \`team_delete\` tool to delete a team when done
+- Teams are stored at ~/.config/levelcode/teams/
+
+**Task Management:**
+- Use \`task_create\` to create tasks for team members
+- Use \`task_list\` to see all tasks and their status
+- Use \`task_update\` to update task status, assign owners, set dependencies
+- Use \`task_get\` to read full task details
+
+**Communication:**
+- Use \`send_message\` to send messages between team members (DM, broadcast, shutdown requests)
+
+**Spawning Team Agents:**
+When spawning agents with \`spawn_agents\`, you can assign them to a team:
+\`\`\`
+spawn_agents([{
+  agent: "team-manager",
+  prompt: "Manage the frontend tasks",
+  team_name: "my-project",
+  team_role: "manager"
+}])
+\`\`\`
+
+**Available team roles:** coordinator, manager, senior-engineer, mid-level-engineer, junior-engineer, researcher, designer, product-lead, tester, scientist, and more.
+
+**Development Phases:** Teams progress through phases: planning \u2192 pre-alpha \u2192 alpha \u2192 beta \u2192 production \u2192 mature.
+
+**Slash Commands:** Users can use /team:create, /team:delete, /team:status, /team:phase, /team:enable, /team:disable, /team:members to manage teams.
+
+When the user asks about teams, swarms, or multi-agent collaboration, use these tools directly. Do NOT say the feature is unavailable or needs external setup.
+
 # Other response guidelines
 
 - Your goal is to produce the highest quality results, even if it comes at the cost of more credits used.
@@ -159756,7 +160080,14 @@ At the end of your turn, use the suggest_followups tool to suggest around 3 next
         "propose_write_file",
         "ask_user",
         "skill",
-        "set_output"
+        "set_output",
+        "team_create",
+        "team_delete",
+        "send_message",
+        "task_create",
+        "task_get",
+        "task_update",
+        "task_list"
       ],
       spawnableAgents: [
         "file-picker",
@@ -159771,7 +160102,17 @@ At the end of your turn, use the suggest_followups tool to suggest around 3 next
         "gpt-5-agent",
         "editor",
         "code-reviewer",
-        "context-pruner"
+        "context-pruner",
+        "coordinator",
+        "team-manager",
+        "senior-engineer",
+        "team-mid-level-engineer",
+        "team-junior-engineer",
+        "team-researcher",
+        "team-designer",
+        "team-product-lead",
+        "team-tester",
+        "team-scientist"
       ],
       systemPrompt: `You are Sage, a strategic assistant that orchestrates complex coding tasks through specialized sub-agents. You are the AI agent behind the product, LevelCode, a CLI tool where users can chat with you to code with AI.
 
@@ -159835,6 +160176,43 @@ The user can use the "/usage" command to see how many credits they have used and
 
 For other questions, you can direct them to levelcode.vercel.app, or especially levelcode.vercel.app/docs for detailed information about the product.
 
+# Agent Swarms / Teams
+
+LevelCode has a built-in agent swarms system for organizing multiple agents into coordinated teams. You have full access to these tools:
+
+**Creating and Managing Teams:**
+- Use the \`team_create\` tool to create a new team: \`team_create({ team_name: "my-project" })\`
+- Use the \`team_delete\` tool to delete a team when done
+- Teams are stored at ~/.config/levelcode/teams/
+
+**Task Management:**
+- Use \`task_create\` to create tasks for team members
+- Use \`task_list\` to see all tasks and their status
+- Use \`task_update\` to update task status, assign owners, set dependencies
+- Use \`task_get\` to read full task details
+
+**Communication:**
+- Use \`send_message\` to send messages between team members (DM, broadcast, shutdown requests)
+
+**Spawning Team Agents:**
+When spawning agents with \`spawn_agents\`, you can assign them to a team:
+\`\`\`
+spawn_agents([{
+  agent: "team-manager",
+  prompt: "Manage the frontend tasks",
+  team_name: "my-project",
+  team_role: "manager"
+}])
+\`\`\`
+
+**Available team roles:** coordinator, manager, senior-engineer, mid-level-engineer, junior-engineer, researcher, designer, product-lead, tester, scientist, and more.
+
+**Development Phases:** Teams progress through phases: planning \u2192 pre-alpha \u2192 alpha \u2192 beta \u2192 production \u2192 mature.
+
+**Slash Commands:** Users can use /team:create, /team:delete, /team:status, /team:phase, /team:enable, /team:disable, /team:members to manage teams.
+
+When the user asks about teams, swarms, or multi-agent collaboration, use these tools directly. Do NOT say the feature is unavailable or needs external setup.
+
 # Other response guidelines
 
 - Your goal is to produce the highest quality results, even if it comes at the cost of more credits used.
@@ -159985,7 +160363,14 @@ This is more like an extremely short PRD which describes the end result of what
         "propose_write_file",
         "ask_user",
         "skill",
-        "set_output"
+        "set_output",
+        "team_create",
+        "team_delete",
+        "send_message",
+        "task_create",
+        "task_get",
+        "task_update",
+        "task_list"
       ],
       spawnableAgents: [
         "file-picker",
@@ -160000,7 +160385,17 @@ This is more like an extremely short PRD which describes the end result of what
         "gpt-5-agent",
         "editor",
         "code-reviewer",
-        "context-pruner"
+        "context-pruner",
+        "coordinator",
+        "team-manager",
+        "senior-engineer",
+        "team-mid-level-engineer",
+        "team-junior-engineer",
+        "team-researcher",
+        "team-designer",
+        "team-product-lead",
+        "team-tester",
+        "team-scientist"
       ],
       systemPrompt: `You are Sage, a strategic assistant that orchestrates complex coding tasks through specialized sub-agents. You are the AI agent behind the product, LevelCode, a CLI tool where users can chat with you to code with AI.
 
@@ -160064,6 +160459,43 @@ The user can use the "/usage" command to see how many credits they have used and
 
 For other questions, you can direct them to levelcode.vercel.app, or especially levelcode.vercel.app/docs for detailed information about the product.
 
+# Agent Swarms / Teams
+
+LevelCode has a built-in agent swarms system for organizing multiple agents into coordinated teams. You have full access to these tools:
+
+**Creating and Managing Teams:**
+- Use the \`team_create\` tool to create a new team: \`team_create({ team_name: "my-project" })\`
+- Use the \`team_delete\` tool to delete a team when done
+- Teams are stored at ~/.config/levelcode/teams/
+
+**Task Management:**
+- Use \`task_create\` to create tasks for team members
+- Use \`task_list\` to see all tasks and their status
+- Use \`task_update\` to update task status, assign owners, set dependencies
+- Use \`task_get\` to read full task details
+
+**Communication:**
+- Use \`send_message\` to send messages between team members (DM, broadcast, shutdown requests)
+
+**Spawning Team Agents:**
+When spawning agents with \`spawn_agents\`, you can assign them to a team:
+\`\`\`
+spawn_agents([{
+  agent: "team-manager",
+  prompt: "Manage the frontend tasks",
+  team_name: "my-project",
+  team_role: "manager"
+}])
+\`\`\`
+
+**Available team roles:** coordinator, manager, senior-engineer, mid-level-engineer, junior-engineer, researcher, designer, product-lead, tester, scientist, and more.
+
+**Development Phases:** Teams progress through phases: planning \u2192 pre-alpha \u2192 alpha \u2192 beta \u2192 production \u2192 mature.
+
+**Slash Commands:** Users can use /team:create, /team:delete, /team:status, /team:phase, /team:enable, /team:disable, /team:members to manage teams.
+
+When the user asks about teams, swarms, or multi-agent collaboration, use these tools directly. Do NOT say the feature is unavailable or needs external setup.
+
 # Other response guidelines
 
 - Your goal is to produce the highest quality results, even if it comes at the cost of more credits used.
@@ -165957,6 +166389,31 @@ var require_extend = __commonJS((exports3, module3) => {
   };
 });
 
+// ../sdk/dist/vendor/ripgrep/arm64-darwin/rg
+var require_rg = __commonJS((exports3, module3) => {
+  module3.exports = "./rg-r6ev1ksc.";
+});
+
+// ../sdk/dist/vendor/ripgrep/x64-darwin/rg
+var require_rg2 = __commonJS((exports3, module3) => {
+  module3.exports = "./rg-ch8fa8g7.";
+});
+
+// ../sdk/dist/vendor/ripgrep/arm64-linux/rg
+var require_rg3 = __commonJS((exports3, module3) => {
+  module3.exports = "./rg-3agys64c.";
+});
+
+// ../sdk/dist/vendor/ripgrep/x64-linux/rg
+var require_rg4 = __commonJS((exports3, module3) => {
+  module3.exports = "./rg-0p18sjte.";
+});
+
+// ../sdk/dist/vendor/ripgrep/x64-win32/rg.exe
+var require_rg5 = __commonJS((exports3, module3) => {
+  module3.exports = "./rg-maqk0g78.exe";
+});
+
 // src/index.tsx
 import fs34 from "fs";
 import { createRequire as createRequire2 } from "module";
@@ -217682,15 +218139,15 @@ var getRipgrepPath = async () => {
   try {
     let embeddedRgPath;
     if (process.platform === "darwin" && process.arch === "arm64") {
-      embeddedRgPath = (()=>{throw new Error("Cannot require module "+"../../../sdk/dist/vendor/ripgrep/arm64-darwin/rg");})();
+      embeddedRgPath = require_rg();
     } else if (process.platform === "darwin" && process.arch === "x64") {
-      embeddedRgPath = (()=>{throw new Error("Cannot require module "+"../../../sdk/dist/vendor/ripgrep/x64-darwin/rg");})();
+      embeddedRgPath = require_rg2();
     } else if (process.platform === "linux" && process.arch === "arm64") {
-      embeddedRgPath = (()=>{throw new Error("Cannot require module "+"../../../sdk/dist/vendor/ripgrep/arm64-linux/rg");})();
+      embeddedRgPath = require_rg3();
     } else if (process.platform === "linux" && process.arch === "x64") {
-      embeddedRgPath = (()=>{throw new Error("Cannot require module "+"../../../sdk/dist/vendor/ripgrep/x64-linux/rg");})();
+      embeddedRgPath = require_rg4();
     } else if (process.platform === "win32" && process.arch === "x64") {
-      embeddedRgPath = (()=>{throw new Error("Cannot require module "+"../../../sdk/dist/vendor/ripgrep/x64-win32/rg.exe");})();
+      embeddedRgPath = require_rg5();
     } else {
       throw new Error(`Unsupported platform: ${process.platform}-${process.arch}`);
     }

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@levelcode/cli",
-  "version": "0.2.3",
+  "version": "0.2.4",
   "description": "LevelCode CLI - Terminal-based AI coding agent that outperforms Claude Code",
   "author": {
     "name": "Yethikrishna R",