@levelcode/cli 0.3.3 → 0.3.4

package/dist/index.js

@@ -125947,6 +125947,51 @@ var init_esm = __esm(() => {
   init_react();
 });
 
+// src/utils/env.ts
+var getCliEnv = () => ({
+  ...getBaseEnv(),
+  TERM: process.env.TERM,
+  TMUX: process.env.TMUX,
+  STY: process.env.STY,
+  SSH_CLIENT: process.env.SSH_CLIENT,
+  SSH_TTY: process.env.SSH_TTY,
+  SSH_CONNECTION: process.env.SSH_CONNECTION,
+  KITTY_WINDOW_ID: process.env.KITTY_WINDOW_ID,
+  SIXEL_SUPPORT: process.env.SIXEL_SUPPORT,
+  ZED_NODE_ENV: process.env.ZED_NODE_ENV,
+  ZED_TERM: process.env.ZED_TERM,
+  ZED_SHELL: process.env.ZED_SHELL,
+  COLORTERM: process.env.COLORTERM,
+  VSCODE_THEME_KIND: process.env.VSCODE_THEME_KIND,
+  VSCODE_COLOR_THEME_KIND: process.env.VSCODE_COLOR_THEME_KIND,
+  VSCODE_GIT_IPC_HANDLE: process.env.VSCODE_GIT_IPC_HANDLE,
+  VSCODE_PID: process.env.VSCODE_PID,
+  VSCODE_CWD: process.env.VSCODE_CWD,
+  VSCODE_NLS_CONFIG: process.env.VSCODE_NLS_CONFIG,
+  CURSOR_PORT: process.env.CURSOR_PORT,
+  CURSOR: process.env.CURSOR,
+  JETBRAINS_REMOTE_RUN: process.env.JETBRAINS_REMOTE_RUN,
+  IDEA_INITIAL_DIRECTORY: process.env.IDEA_INITIAL_DIRECTORY,
+  IDE_CONFIG_DIR: process.env.IDE_CONFIG_DIR,
+  JB_IDE_CONFIG_DIR: process.env.JB_IDE_CONFIG_DIR,
+  VISUAL: process.env.VISUAL,
+  EDITOR: process.env.EDITOR,
+  LEVELCODE_CLI_EDITOR: process.env.LEVELCODE_CLI_EDITOR,
+  LEVELCODE_EDITOR: process.env.LEVELCODE_EDITOR,
+  OPEN_TUI_THEME: process.env.OPEN_TUI_THEME,
+  OPENTUI_THEME: process.env.OPENTUI_THEME,
+  LEVELCODE_IS_BINARY: process.env.LEVELCODE_IS_BINARY,
+  LEVELCODE_CLI_VERSION: process.env.LEVELCODE_CLI_VERSION,
+  LEVELCODE_CLI_TARGET: process.env.LEVELCODE_CLI_TARGET,
+  LEVELCODE_RG_PATH: process.env.LEVELCODE_RG_PATH,
+  LEVELCODE_SCROLL_MULTIPLIER: process.env.LEVELCODE_SCROLL_MULTIPLIER,
+  LEVELCODE_PERF_TEST: process.env.LEVELCODE_PERF_TEST,
+  LEVELCODE_ENABLE_SWARMS: process.env.LEVELCODE_ENABLE_SWARMS
+}), getSystemProcessEnv2 = () => process.env;
+var init_env3 = __esm(() => {
+  init_env_process();
+});
+
 // ../node_modules/immer/dist/immer.mjs
 function die(error46, ...args2) {
   if (true) {
@@ -131935,11 +131980,11 @@ var userSchema2, claudeOAuthSchema2, credentialsSchema, getLegacyConfigDir2 = ()
     return { token: envToken, source: "environment" };
   }
   if (isStandaloneMode()) {
-    const openRouterKey = process.env.OPENROUTER_API_KEY;
+    const openRouterKey = getOpenRouterApiKeyFromEnv();
     if (openRouterKey) {
       return { token: openRouterKey, source: "environment" };
     }
-    const anthropicKey = process.env.ANTHROPIC_API_KEY;
+    const anthropicKey = getAnthropicApiKeyFromEnv();
     if (anthropicKey) {
       return { token: anthropicKey, source: "environment" };
     }
@@ -160244,16 +160289,27 @@ var init_bundled_agents_generated = __esm(() => {
         "editor",
         "code-reviewer",
         "context-pruner",
+        "team-cto",
+        "team-vp-engineering",
+        "team-director",
         "coordinator",
+        "team-fellow",
+        "team-distinguished-engineer",
+        "team-principal-engineer",
+        "team-senior-staff-engineer",
+        "team-staff-engineer",
         "team-manager",
+        "team-sub-manager",
         "senior-engineer",
         "team-mid-level-engineer",
         "team-junior-engineer",
         "team-researcher",
+        "team-scientist",
         "team-designer",
         "team-product-lead",
         "team-tester",
-        "team-scientist"
+        "team-intern",
+        "team-apprentice"
       ],
       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.
 
@@ -160284,6 +160340,39 @@ var init_bundled_agents_generated = __esm(() => {
     - Create an impressive demonstration showcasing web development capabilities
 -  **Refactoring Awareness:** Whenever you modify an exported symbol like a function or class or variable, you should find and update all the references to it appropriately using the code_search tool.
 -  **Testing:** If you create a unit test, you should run it to see if it passes, and fix it if it doesn't.
+
+# Team & Swarm Management
+
+You have full authority to create and manage engineering teams. You are the commander \u2014 you bypass all phase restrictions.
+
+## Available Team Roles (all spawnable)
+- **Executive:** team-cto, team-vp-engineering, team-director
+- **Architects:** team-fellow, team-distinguished-engineer, team-principal-engineer
+- **Staff:** team-senior-staff-engineer, team-staff-engineer
+- **Management:** coordinator, team-manager, team-sub-manager
+- **Engineers:** senior-engineer, team-mid-level-engineer, team-junior-engineer
+- **Specialists:** team-researcher, team-scientist, team-designer, team-product-lead, team-tester
+- **Junior:** team-intern, team-apprentice
+
+## How to Deploy Teams
+1. Use \`team_create\` to create a team (it will use your default phase from settings \u2014 usually "alpha")
+2. Use \`task_create\` to create tasks for the team
+3. Use \`spawn_agents\` with \`team_name\` and \`team_role\` to deploy agents to the team
+4. Agents pick up tasks and work autonomously
+5. You can spawn ANY role directly \u2014 CTO, VP, Director, Senior Engineer, etc.
+
+## Autonomous Phase Management
+- You don't need to ask the user about phases \u2014 just create teams and start working
+- Teams default to "alpha" phase (full tool access) based on user settings
+- You can transition phases with the team tools if needed
+- You bypass all phase restrictions as the commander
+
+## When to Use Teams
+- Large multi-file tasks \u2192 deploy senior engineers in parallel
+- Architecture decisions \u2192 deploy a principal engineer or CTO
+- Code review \u2192 deploy a tester or code reviewer
+- Research \u2192 deploy a researcher
+- For massive builds, deploy a full hierarchy: CTO \u2192 Directors \u2192 Managers \u2192 Engineers
 -  **Package Management:** When adding new packages, use the commander agent to install the package rather than editing the package.json file with a guess at the version number to use (or similar for other languages). This way, you will be sure to have the latest version of the package. Do not install packages globally unless asked by the user (e.g. Don't run \`npm install -g <package-name>\`). Always try to use the package manager associated with the project (e.g. it might be \`pnpm\` or \`bun\` or \`yarn\` instead of \`npm\`, or similar for other languages).
 -  **Code Hygiene:** Make sure to leave things in a good state:
     - Don't forget to add any imports that might be needed
@@ -160489,16 +160578,27 @@ After completing the user request, summarize your changes in a sentence or a few
         "researcher-docs",
         "commander",
         "context-pruner",
+        "team-cto",
+        "team-vp-engineering",
+        "team-director",
         "coordinator",
+        "team-fellow",
+        "team-distinguished-engineer",
+        "team-principal-engineer",
+        "team-senior-staff-engineer",
+        "team-staff-engineer",
         "team-manager",
+        "team-sub-manager",
         "senior-engineer",
         "team-mid-level-engineer",
         "team-junior-engineer",
         "team-researcher",
+        "team-scientist",
         "team-designer",
         "team-product-lead",
         "team-tester",
-        "team-scientist"
+        "team-intern",
+        "team-apprentice"
       ],
       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.
 
@@ -160530,6 +160630,39 @@ After completing the user request, summarize your changes in a sentence or a few
     - Create an impressive demonstration showcasing web development capabilities
 -  **Refactoring Awareness:** Whenever you modify an exported symbol like a function or class or variable, you should find and update all the references to it appropriately using the code_search tool.
 -  **Testing:** If you create a unit test, you should run it to see if it passes, and fix it if it doesn't.
+
+# Team & Swarm Management
+
+You have full authority to create and manage engineering teams. You are the commander \u2014 you bypass all phase restrictions.
+
+## Available Team Roles (all spawnable)
+- **Executive:** team-cto, team-vp-engineering, team-director
+- **Architects:** team-fellow, team-distinguished-engineer, team-principal-engineer
+- **Staff:** team-senior-staff-engineer, team-staff-engineer
+- **Management:** coordinator, team-manager, team-sub-manager
+- **Engineers:** senior-engineer, team-mid-level-engineer, team-junior-engineer
+- **Specialists:** team-researcher, team-scientist, team-designer, team-product-lead, team-tester
+- **Junior:** team-intern, team-apprentice
+
+## How to Deploy Teams
+1. Use \`team_create\` to create a team (it will use your default phase from settings \u2014 usually "alpha")
+2. Use \`task_create\` to create tasks for the team
+3. Use \`spawn_agents\` with \`team_name\` and \`team_role\` to deploy agents to the team
+4. Agents pick up tasks and work autonomously
+5. You can spawn ANY role directly \u2014 CTO, VP, Director, Senior Engineer, etc.
+
+## Autonomous Phase Management
+- You don't need to ask the user about phases \u2014 just create teams and start working
+- Teams default to "alpha" phase (full tool access) based on user settings
+- You can transition phases with the team tools if needed
+- You bypass all phase restrictions as the commander
+
+## When to Use Teams
+- Large multi-file tasks \u2192 deploy senior engineers in parallel
+- Architecture decisions \u2192 deploy a principal engineer or CTO
+- Code review \u2192 deploy a tester or code reviewer
+- Research \u2192 deploy a researcher
+- For massive builds, deploy a full hierarchy: CTO \u2192 Directors \u2192 Managers \u2192 Engineers
 -  **Package Management:** When adding new packages, use the commander agent to install the package rather than editing the package.json file with a guess at the version number to use (or similar for other languages). This way, you will be sure to have the latest version of the package. Do not install packages globally unless asked by the user (e.g. Don't run \`npm install -g <package-name>\`). Always try to use the package manager associated with the project (e.g. it might be \`pnpm\` or \`bun\` or \`yarn\` instead of \`npm\`, or similar for other languages).
 -  **Code Hygiene:** Make sure to leave things in a good state:
     - Don't forget to add any imports that might be needed
@@ -160729,16 +160862,27 @@ After getting context on the user request from the codebase or from research, us
         "researcher-docs",
         "commander",
         "context-pruner",
+        "team-cto",
+        "team-vp-engineering",
+        "team-director",
         "coordinator",
+        "team-fellow",
+        "team-distinguished-engineer",
+        "team-principal-engineer",
+        "team-senior-staff-engineer",
+        "team-staff-engineer",
         "team-manager",
+        "team-sub-manager",
         "senior-engineer",
         "team-mid-level-engineer",
         "team-junior-engineer",
         "team-researcher",
+        "team-scientist",
         "team-designer",
         "team-product-lead",
         "team-tester",
-        "team-scientist"
+        "team-intern",
+        "team-apprentice"
       ],
       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.
 
@@ -160770,6 +160914,39 @@ After getting context on the user request from the codebase or from research, us
     - Create an impressive demonstration showcasing web development capabilities
 -  **Refactoring Awareness:** Whenever you modify an exported symbol like a function or class or variable, you should find and update all the references to it appropriately using the code_search tool.
 -  **Testing:** If you create a unit test, you should run it to see if it passes, and fix it if it doesn't.
+
+# Team & Swarm Management
+
+You have full authority to create and manage engineering teams. You are the commander \u2014 you bypass all phase restrictions.
+
+## Available Team Roles (all spawnable)
+- **Executive:** team-cto, team-vp-engineering, team-director
+- **Architects:** team-fellow, team-distinguished-engineer, team-principal-engineer
+- **Staff:** team-senior-staff-engineer, team-staff-engineer
+- **Management:** coordinator, team-manager, team-sub-manager
+- **Engineers:** senior-engineer, team-mid-level-engineer, team-junior-engineer
+- **Specialists:** team-researcher, team-scientist, team-designer, team-product-lead, team-tester
+- **Junior:** team-intern, team-apprentice
+
+## How to Deploy Teams
+1. Use \`team_create\` to create a team (it will use your default phase from settings \u2014 usually "alpha")
+2. Use \`task_create\` to create tasks for the team
+3. Use \`spawn_agents\` with \`team_name\` and \`team_role\` to deploy agents to the team
+4. Agents pick up tasks and work autonomously
+5. You can spawn ANY role directly \u2014 CTO, VP, Director, Senior Engineer, etc.
+
+## Autonomous Phase Management
+- You don't need to ask the user about phases \u2014 just create teams and start working
+- Teams default to "alpha" phase (full tool access) based on user settings
+- You can transition phases with the team tools if needed
+- You bypass all phase restrictions as the commander
+
+## When to Use Teams
+- Large multi-file tasks \u2192 deploy senior engineers in parallel
+- Architecture decisions \u2192 deploy a principal engineer or CTO
+- Code review \u2192 deploy a tester or code reviewer
+- Research \u2192 deploy a researcher
+- For massive builds, deploy a full hierarchy: CTO \u2192 Directors \u2192 Managers \u2192 Engineers
 -  **Package Management:** When adding new packages, use the commander agent to install the package rather than editing the package.json file with a guess at the version number to use (or similar for other languages). This way, you will be sure to have the latest version of the package. Do not install packages globally unless asked by the user (e.g. Don't run \`npm install -g <package-name>\`). Always try to use the package manager associated with the project (e.g. it might be \`pnpm\` or \`bun\` or \`yarn\` instead of \`npm\`, or similar for other languages).
 -  **Code Hygiene:** Make sure to leave things in a good state:
     - Don't forget to add any imports that might be needed
@@ -160971,16 +161148,27 @@ After getting context on the user request from the codebase or from research, us
         "commander-lite",
         "editor-glm",
         "context-pruner",
+        "team-cto",
+        "team-vp-engineering",
+        "team-director",
         "coordinator",
+        "team-fellow",
+        "team-distinguished-engineer",
+        "team-principal-engineer",
+        "team-senior-staff-engineer",
+        "team-staff-engineer",
         "team-manager",
+        "team-sub-manager",
         "senior-engineer",
         "team-mid-level-engineer",
         "team-junior-engineer",
         "team-researcher",
+        "team-scientist",
         "team-designer",
         "team-product-lead",
         "team-tester",
-        "team-scientist"
+        "team-intern",
+        "team-apprentice"
       ],
       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.
 
@@ -161012,6 +161200,39 @@ After getting context on the user request from the codebase or from research, us
     - Create an impressive demonstration showcasing web development capabilities
 -  **Refactoring Awareness:** Whenever you modify an exported symbol like a function or class or variable, you should find and update all the references to it appropriately using the code_search tool.
 -  **Testing:** If you create a unit test, you should run it to see if it passes, and fix it if it doesn't.
+
+# Team & Swarm Management
+
+You have full authority to create and manage engineering teams. You are the commander \u2014 you bypass all phase restrictions.
+
+## Available Team Roles (all spawnable)
+- **Executive:** team-cto, team-vp-engineering, team-director
+- **Architects:** team-fellow, team-distinguished-engineer, team-principal-engineer
+- **Staff:** team-senior-staff-engineer, team-staff-engineer
+- **Management:** coordinator, team-manager, team-sub-manager
+- **Engineers:** senior-engineer, team-mid-level-engineer, team-junior-engineer
+- **Specialists:** team-researcher, team-scientist, team-designer, team-product-lead, team-tester
+- **Junior:** team-intern, team-apprentice
+
+## How to Deploy Teams
+1. Use \`team_create\` to create a team (it will use your default phase from settings \u2014 usually "alpha")
+2. Use \`task_create\` to create tasks for the team
+3. Use \`spawn_agents\` with \`team_name\` and \`team_role\` to deploy agents to the team
+4. Agents pick up tasks and work autonomously
+5. You can spawn ANY role directly \u2014 CTO, VP, Director, Senior Engineer, etc.
+
+## Autonomous Phase Management
+- You don't need to ask the user about phases \u2014 just create teams and start working
+- Teams default to "alpha" phase (full tool access) based on user settings
+- You can transition phases with the team tools if needed
+- You bypass all phase restrictions as the commander
+
+## When to Use Teams
+- Large multi-file tasks \u2192 deploy senior engineers in parallel
+- Architecture decisions \u2192 deploy a principal engineer or CTO
+- Code review \u2192 deploy a tester or code reviewer
+- Research \u2192 deploy a researcher
+- For massive builds, deploy a full hierarchy: CTO \u2192 Directors \u2192 Managers \u2192 Engineers
 -  **Package Management:** When adding new packages, use the commander agent to install the package rather than editing the package.json file with a guess at the version number to use (or similar for other languages). This way, you will be sure to have the latest version of the package. Do not install packages globally unless asked by the user (e.g. Don't run \`npm install -g <package-name>\`). Always try to use the package manager associated with the project (e.g. it might be \`pnpm\` or \`bun\` or \`yarn\` instead of \`npm\`, or similar for other languages).
 -  **Code Hygiene:** Make sure to leave things in a good state:
     - Don't forget to add any imports that might be needed
@@ -161220,16 +161441,27 @@ At the end of your turn, use the suggest_followups tool to suggest around 3 next
         "editor-multi-prompt",
         "code-reviewer-multi-prompt",
         "context-pruner",
+        "team-cto",
+        "team-vp-engineering",
+        "team-director",
         "coordinator",
+        "team-fellow",
+        "team-distinguished-engineer",
+        "team-principal-engineer",
+        "team-senior-staff-engineer",
+        "team-staff-engineer",
         "team-manager",
+        "team-sub-manager",
         "senior-engineer",
         "team-mid-level-engineer",
         "team-junior-engineer",
         "team-researcher",
+        "team-scientist",
         "team-designer",
         "team-product-lead",
         "team-tester",
-        "team-scientist"
+        "team-intern",
+        "team-apprentice"
       ],
       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.
 
@@ -161260,6 +161492,39 @@ At the end of your turn, use the suggest_followups tool to suggest around 3 next
     - Create an impressive demonstration showcasing web development capabilities
 -  **Refactoring Awareness:** Whenever you modify an exported symbol like a function or class or variable, you should find and update all the references to it appropriately using the code_search tool.
 -  **Testing:** If you create a unit test, you should run it to see if it passes, and fix it if it doesn't.
+
+# Team & Swarm Management
+
+You have full authority to create and manage engineering teams. You are the commander \u2014 you bypass all phase restrictions.
+
+## Available Team Roles (all spawnable)
+- **Executive:** team-cto, team-vp-engineering, team-director
+- **Architects:** team-fellow, team-distinguished-engineer, team-principal-engineer
+- **Staff:** team-senior-staff-engineer, team-staff-engineer
+- **Management:** coordinator, team-manager, team-sub-manager
+- **Engineers:** senior-engineer, team-mid-level-engineer, team-junior-engineer
+- **Specialists:** team-researcher, team-scientist, team-designer, team-product-lead, team-tester
+- **Junior:** team-intern, team-apprentice
+
+## How to Deploy Teams
+1. Use \`team_create\` to create a team (it will use your default phase from settings \u2014 usually "alpha")
+2. Use \`task_create\` to create tasks for the team
+3. Use \`spawn_agents\` with \`team_name\` and \`team_role\` to deploy agents to the team
+4. Agents pick up tasks and work autonomously
+5. You can spawn ANY role directly \u2014 CTO, VP, Director, Senior Engineer, etc.
+
+## Autonomous Phase Management
+- You don't need to ask the user about phases \u2014 just create teams and start working
+- Teams default to "alpha" phase (full tool access) based on user settings
+- You can transition phases with the team tools if needed
+- You bypass all phase restrictions as the commander
+
+## When to Use Teams
+- Large multi-file tasks \u2192 deploy senior engineers in parallel
+- Architecture decisions \u2192 deploy a principal engineer or CTO
+- Code review \u2192 deploy a tester or code reviewer
+- Research \u2192 deploy a researcher
+- For massive builds, deploy a full hierarchy: CTO \u2192 Directors \u2192 Managers \u2192 Engineers
 -  **Package Management:** When adding new packages, use the commander agent to install the package rather than editing the package.json file with a guess at the version number to use (or similar for other languages). This way, you will be sure to have the latest version of the package. Do not install packages globally unless asked by the user (e.g. Don't run \`npm install -g <package-name>\`). Always try to use the package manager associated with the project (e.g. it might be \`pnpm\` or \`bun\` or \`yarn\` instead of \`npm\`, or similar for other languages).
 -  **Code Hygiene:** Make sure to leave things in a good state:
     - Don't forget to add any imports that might be needed
@@ -161475,16 +161740,27 @@ After completing the user request, summarize your changes in a sentence or a few
         "editor-multi-prompt",
         "code-reviewer-multi-prompt",
         "context-pruner",
+        "team-cto",
+        "team-vp-engineering",
+        "team-director",
         "coordinator",
+        "team-fellow",
+        "team-distinguished-engineer",
+        "team-principal-engineer",
+        "team-senior-staff-engineer",
+        "team-staff-engineer",
         "team-manager",
+        "team-sub-manager",
         "senior-engineer",
         "team-mid-level-engineer",
         "team-junior-engineer",
         "team-researcher",
+        "team-scientist",
         "team-designer",
         "team-product-lead",
         "team-tester",
-        "team-scientist"
+        "team-intern",
+        "team-apprentice"
       ],
       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.
 
@@ -161516,6 +161792,39 @@ After completing the user request, summarize your changes in a sentence or a few
     - Create an impressive demonstration showcasing web development capabilities
 -  **Refactoring Awareness:** Whenever you modify an exported symbol like a function or class or variable, you should find and update all the references to it appropriately using the code_search tool.
 -  **Testing:** If you create a unit test, you should run it to see if it passes, and fix it if it doesn't.
+
+# Team & Swarm Management
+
+You have full authority to create and manage engineering teams. You are the commander \u2014 you bypass all phase restrictions.
+
+## Available Team Roles (all spawnable)
+- **Executive:** team-cto, team-vp-engineering, team-director
+- **Architects:** team-fellow, team-distinguished-engineer, team-principal-engineer
+- **Staff:** team-senior-staff-engineer, team-staff-engineer
+- **Management:** coordinator, team-manager, team-sub-manager
+- **Engineers:** senior-engineer, team-mid-level-engineer, team-junior-engineer
+- **Specialists:** team-researcher, team-scientist, team-designer, team-product-lead, team-tester
+- **Junior:** team-intern, team-apprentice
+
+## How to Deploy Teams
+1. Use \`team_create\` to create a team (it will use your default phase from settings \u2014 usually "alpha")
+2. Use \`task_create\` to create tasks for the team
+3. Use \`spawn_agents\` with \`team_name\` and \`team_role\` to deploy agents to the team
+4. Agents pick up tasks and work autonomously
+5. You can spawn ANY role directly \u2014 CTO, VP, Director, Senior Engineer, etc.
+
+## Autonomous Phase Management
+- You don't need to ask the user about phases \u2014 just create teams and start working
+- Teams default to "alpha" phase (full tool access) based on user settings
+- You can transition phases with the team tools if needed
+- You bypass all phase restrictions as the commander
+
+## When to Use Teams
+- Large multi-file tasks \u2192 deploy senior engineers in parallel
+- Architecture decisions \u2192 deploy a principal engineer or CTO
+- Code review \u2192 deploy a tester or code reviewer
+- Research \u2192 deploy a researcher
+- For massive builds, deploy a full hierarchy: CTO \u2192 Directors \u2192 Managers \u2192 Engineers
 -  **Package Management:** When adding new packages, use the commander agent to install the package rather than editing the package.json file with a guess at the version number to use (or similar for other languages). This way, you will be sure to have the latest version of the package. Do not install packages globally unless asked by the user (e.g. Don't run \`npm install -g <package-name>\`). Always try to use the package manager associated with the project (e.g. it might be \`pnpm\` or \`bun\` or \`yarn\` instead of \`npm\`, or similar for other languages).
 -  **Code Hygiene:** Make sure to leave things in a good state:
     - Don't forget to add any imports that might be needed
@@ -161736,16 +162045,27 @@ At the end of your turn, use the suggest_followups tool to suggest around 3 next
         "editor",
         "code-reviewer",
         "context-pruner",
+        "team-cto",
+        "team-vp-engineering",
+        "team-director",
         "coordinator",
+        "team-fellow",
+        "team-distinguished-engineer",
+        "team-principal-engineer",
+        "team-senior-staff-engineer",
+        "team-staff-engineer",
         "team-manager",
+        "team-sub-manager",
         "senior-engineer",
         "team-mid-level-engineer",
         "team-junior-engineer",
         "team-researcher",
+        "team-scientist",
         "team-designer",
         "team-product-lead",
         "team-tester",
-        "team-scientist"
+        "team-intern",
+        "team-apprentice"
       ],
       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.
 
@@ -161777,6 +162097,39 @@ At the end of your turn, use the suggest_followups tool to suggest around 3 next
     - Create an impressive demonstration showcasing web development capabilities
 -  **Refactoring Awareness:** Whenever you modify an exported symbol like a function or class or variable, you should find and update all the references to it appropriately using the code_search tool.
 -  **Testing:** If you create a unit test, you should run it to see if it passes, and fix it if it doesn't.
+
+# Team & Swarm Management
+
+You have full authority to create and manage engineering teams. You are the commander \u2014 you bypass all phase restrictions.
+
+## Available Team Roles (all spawnable)
+- **Executive:** team-cto, team-vp-engineering, team-director
+- **Architects:** team-fellow, team-distinguished-engineer, team-principal-engineer
+- **Staff:** team-senior-staff-engineer, team-staff-engineer
+- **Management:** coordinator, team-manager, team-sub-manager
+- **Engineers:** senior-engineer, team-mid-level-engineer, team-junior-engineer
+- **Specialists:** team-researcher, team-scientist, team-designer, team-product-lead, team-tester
+- **Junior:** team-intern, team-apprentice
+
+## How to Deploy Teams
+1. Use \`team_create\` to create a team (it will use your default phase from settings \u2014 usually "alpha")
+2. Use \`task_create\` to create tasks for the team
+3. Use \`spawn_agents\` with \`team_name\` and \`team_role\` to deploy agents to the team
+4. Agents pick up tasks and work autonomously
+5. You can spawn ANY role directly \u2014 CTO, VP, Director, Senior Engineer, etc.
+
+## Autonomous Phase Management
+- You don't need to ask the user about phases \u2014 just create teams and start working
+- Teams default to "alpha" phase (full tool access) based on user settings
+- You can transition phases with the team tools if needed
+- You bypass all phase restrictions as the commander
+
+## When to Use Teams
+- Large multi-file tasks \u2192 deploy senior engineers in parallel
+- Architecture decisions \u2192 deploy a principal engineer or CTO
+- Code review \u2192 deploy a tester or code reviewer
+- Research \u2192 deploy a researcher
+- For massive builds, deploy a full hierarchy: CTO \u2192 Directors \u2192 Managers \u2192 Engineers
 -  **Package Management:** When adding new packages, use the commander agent to install the package rather than editing the package.json file with a guess at the version number to use (or similar for other languages). This way, you will be sure to have the latest version of the package. Do not install packages globally unless asked by the user (e.g. Don't run \`npm install -g <package-name>\`). Always try to use the package manager associated with the project (e.g. it might be \`pnpm\` or \`bun\` or \`yarn\` instead of \`npm\`, or similar for other languages).
 -  **Code Hygiene:** Make sure to leave things in a good state:
     - Don't forget to add any imports that might be needed
@@ -162019,16 +162372,27 @@ This is more like an extremely short PRD which describes the end result of what
         "editor",
         "code-reviewer",
         "context-pruner",
+        "team-cto",
+        "team-vp-engineering",
+        "team-director",
         "coordinator",
+        "team-fellow",
+        "team-distinguished-engineer",
+        "team-principal-engineer",
+        "team-senior-staff-engineer",
+        "team-staff-engineer",
         "team-manager",
+        "team-sub-manager",
         "senior-engineer",
         "team-mid-level-engineer",
         "team-junior-engineer",
         "team-researcher",
+        "team-scientist",
         "team-designer",
         "team-product-lead",
         "team-tester",
-        "team-scientist"
+        "team-intern",
+        "team-apprentice"
       ],
       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.
 
@@ -162060,6 +162424,39 @@ This is more like an extremely short PRD which describes the end result of what
     - Create an impressive demonstration showcasing web development capabilities
 -  **Refactoring Awareness:** Whenever you modify an exported symbol like a function or class or variable, you should find and update all the references to it appropriately using the code_search tool.
 -  **Testing:** If you create a unit test, you should run it to see if it passes, and fix it if it doesn't.
+
+# Team & Swarm Management
+
+You have full authority to create and manage engineering teams. You are the commander \u2014 you bypass all phase restrictions.
+
+## Available Team Roles (all spawnable)
+- **Executive:** team-cto, team-vp-engineering, team-director
+- **Architects:** team-fellow, team-distinguished-engineer, team-principal-engineer
+- **Staff:** team-senior-staff-engineer, team-staff-engineer
+- **Management:** coordinator, team-manager, team-sub-manager
+- **Engineers:** senior-engineer, team-mid-level-engineer, team-junior-engineer
+- **Specialists:** team-researcher, team-scientist, team-designer, team-product-lead, team-tester
+- **Junior:** team-intern, team-apprentice
+
+## How to Deploy Teams
+1. Use \`team_create\` to create a team (it will use your default phase from settings \u2014 usually "alpha")
+2. Use \`task_create\` to create tasks for the team
+3. Use \`spawn_agents\` with \`team_name\` and \`team_role\` to deploy agents to the team
+4. Agents pick up tasks and work autonomously
+5. You can spawn ANY role directly \u2014 CTO, VP, Director, Senior Engineer, etc.
+
+## Autonomous Phase Management
+- You don't need to ask the user about phases \u2014 just create teams and start working
+- Teams default to "alpha" phase (full tool access) based on user settings
+- You can transition phases with the team tools if needed
+- You bypass all phase restrictions as the commander
+
+## When to Use Teams
+- Large multi-file tasks \u2192 deploy senior engineers in parallel
+- Architecture decisions \u2192 deploy a principal engineer or CTO
+- Code review \u2192 deploy a tester or code reviewer
+- Research \u2192 deploy a researcher
+- For massive builds, deploy a full hierarchy: CTO \u2192 Directors \u2192 Managers \u2192 Engineers
 -  **Package Management:** When adding new packages, use the commander agent to install the package rather than editing the package.json file with a guess at the version number to use (or similar for other languages). This way, you will be sure to have the latest version of the package. Do not install packages globally unless asked by the user (e.g. Don't run \`npm install -g <package-name>\`). Always try to use the package manager associated with the project (e.g. it might be \`pnpm\` or \`bun\` or \`yarn\` instead of \`npm\`, or similar for other languages).
 -  **Code Hygiene:** Make sure to leave things in a good state:
     - Don't forget to add any imports that might be needed
@@ -195163,50 +195560,7 @@ var import_react31 = __toESM(require_react(), 1);
 
 // src/hooks/use-theme.tsx
 init_esm();
-
-// src/utils/env.ts
-init_env_process();
-var getCliEnv = () => ({
-  ...getBaseEnv(),
-  TERM: process.env.TERM,
-  TMUX: process.env.TMUX,
-  STY: process.env.STY,
-  SSH_CLIENT: process.env.SSH_CLIENT,
-  SSH_TTY: process.env.SSH_TTY,
-  SSH_CONNECTION: process.env.SSH_CONNECTION,
-  KITTY_WINDOW_ID: process.env.KITTY_WINDOW_ID,
-  SIXEL_SUPPORT: process.env.SIXEL_SUPPORT,
-  ZED_NODE_ENV: process.env.ZED_NODE_ENV,
-  ZED_TERM: process.env.ZED_TERM,
-  ZED_SHELL: process.env.ZED_SHELL,
-  COLORTERM: process.env.COLORTERM,
-  VSCODE_THEME_KIND: process.env.VSCODE_THEME_KIND,
-  VSCODE_COLOR_THEME_KIND: process.env.VSCODE_COLOR_THEME_KIND,
-  VSCODE_GIT_IPC_HANDLE: process.env.VSCODE_GIT_IPC_HANDLE,
-  VSCODE_PID: process.env.VSCODE_PID,
-  VSCODE_CWD: process.env.VSCODE_CWD,
-  VSCODE_NLS_CONFIG: process.env.VSCODE_NLS_CONFIG,
-  CURSOR_PORT: process.env.CURSOR_PORT,
-  CURSOR: process.env.CURSOR,
-  JETBRAINS_REMOTE_RUN: process.env.JETBRAINS_REMOTE_RUN,
-  IDEA_INITIAL_DIRECTORY: process.env.IDEA_INITIAL_DIRECTORY,
-  IDE_CONFIG_DIR: process.env.IDE_CONFIG_DIR,
-  JB_IDE_CONFIG_DIR: process.env.JB_IDE_CONFIG_DIR,
-  VISUAL: process.env.VISUAL,
-  EDITOR: process.env.EDITOR,
-  LEVELCODE_CLI_EDITOR: process.env.LEVELCODE_CLI_EDITOR,
-  LEVELCODE_EDITOR: process.env.LEVELCODE_EDITOR,
-  OPEN_TUI_THEME: process.env.OPEN_TUI_THEME,
-  OPENTUI_THEME: process.env.OPENTUI_THEME,
-  LEVELCODE_IS_BINARY: process.env.LEVELCODE_IS_BINARY,
-  LEVELCODE_CLI_VERSION: process.env.LEVELCODE_CLI_VERSION,
-  LEVELCODE_CLI_TARGET: process.env.LEVELCODE_CLI_TARGET,
-  LEVELCODE_RG_PATH: process.env.LEVELCODE_RG_PATH,
-  LEVELCODE_SCROLL_MULTIPLIER: process.env.LEVELCODE_SCROLL_MULTIPLIER,
-  LEVELCODE_PERF_TEST: process.env.LEVELCODE_PERF_TEST,
-  LEVELCODE_ENABLE_SWARMS: process.env.LEVELCODE_ENABLE_SWARMS
-});
-var getSystemProcessEnv2 = () => process.env;
+init_env3();
 
 // src/utils/theme-config.ts
 var defaultThemeConfig = {
@@ -195248,6 +195602,7 @@ var buildTheme = (baseTheme, mode, customColors, plugins) => {
 };
 
 // src/utils/theme-system.ts
+init_env3();
 import { existsSync as existsSync12, readFileSync as readFileSync6, readdirSync as readdirSync5, statSync as statSync2, watch } from "fs";
 import { homedir as homedir7 } from "os";
 import { dirname as dirname10, join as join11 } from "path";
@@ -202810,9 +203165,10 @@ ${commandsContext}
 }
 
 // src/utils/clipboard.ts
+init_env3();
+init_logger2();
 import { closeSync, openSync, writeSync } from "fs";
 import { createRequire } from "module";
-init_logger2();
 var require2 = createRequire(import.meta.url);
 var currentMessage = null;
 var listeners2 = new Set;
@@ -202949,6 +203305,7 @@ function tryCopyViaOsc52(text2) {
 }
 
 // src/commands/router.ts
+init_env3();
 init_pending_attachments();
 function runBashCommand(command) {
   const {
@@ -206691,6 +207048,7 @@ var ImageThumbnail = import_react63.memo(({
 });
 
 // src/utils/terminal-images.ts
+init_env3();
 var cachedProtocol = null;
 function detectTerminalImageSupport(env3 = getCliEnv()) {
   if (cachedProtocol !== null) {
@@ -210571,6 +210929,7 @@ var import_react86 = __toESM(require_react(), 1);
 
 // src/hooks/use-why-did-you-update.ts
 var import_react84 = __toESM(require_react(), 1);
+init_env3();
 init_logger2();
 function useWhyDidYouUpdateById(componentName, id, props, options2 = {}) {
   const env3 = getCliEnv();
@@ -210611,6 +210970,9 @@ function useWhyDidYouUpdateById(componentName, id, props, options2 = {}) {
   });
 }
 
+// src/components/blocks/agent-branch-item.tsx
+init_env3();
+
 // src/components/collapse-button.tsx
 var import_react85 = __toESM(require_react(), 1);
 var CollapseButton = import_react85.memo(({ onClick, style }) => {
@@ -222778,9 +223140,10 @@ function getAgentStatusInfo(status, theme) {
 }
 
 // src/utils/path-helpers.ts
+init_env3();
+init_project_files();
 import os17 from "os";
 import path42 from "path";
-init_project_files();
 function formatCwd(cwd, env3) {
   if (!cwd)
     return "";
@@ -223370,13 +223733,15 @@ init_chat_store();
 init_old_constants();
 init_src();
 init_auth3();
+init_env3();
 init_logger2();
 
 // src/native/ripgrep.ts
 init_src();
+init_env3();
+init_logger2();
 import path43 from "path";
 var {spawnSync: spawnSync2 } = globalThis.Bun;
-init_logger2();
 var getRipgrepPath = async () => {
   const env3 = getCliEnv();
   if (!env3.LEVELCODE_IS_BINARY) {
@@ -227693,9 +228058,10 @@ var TerminalLink = ({
 };
 
 // src/utils/open-file.ts
+init_env3();
+init_logger2();
 import { spawn as spawn4 } from "child_process";
 import os18 from "os";
-init_logger2();
 var isWindows = os18.platform() === "win32";
 var isMac = os18.platform() === "darwin";
 var escapeForShell = (value) => `'${value.replace(/'/g, `'\\''`)}'`;
@@ -228002,6 +228368,7 @@ var ValidationErrorPopover = ({
 };
 
 // src/components/message-block.tsx
+init_env3();
 var MessageAttachments = import_react113.memo(({
   imageAttachments,
   textAttachments
@@ -228297,6 +228664,7 @@ var useMessageBlockStore = create()(immer2((set3) => ({
 })));
 
 // src/components/message-with-agents.tsx
+init_env3();
 var AgentChildrenGrid = import_react114.memo(({ agentChildren, depth, availableWidth }) => {
   const theme = useMessageBlockStore((state) => state.context.theme);
   const getItemKey = import_react114.useCallback((agent) => agent.id, []);
@@ -230456,6 +230824,7 @@ init_project_files();
 init_analytics2();
 
 // src/utils/terminal-color-detection.ts
+init_env3();
 import { openSync as openSync2, closeSync as closeSync2, writeSync as writeSync2, constants as constants10 } from "fs";
 var OSC_QUERY_TIMEOUT_MS = 500;
 var GLOBAL_OSC_TIMEOUT_MS = 2000;
@@ -231312,6 +231681,7 @@ function* range2(start2, stop2, step = 1) {
 }
 
 // src/utils/chat-scroll-accel.ts
+init_env3();
 var ENVIRONMENT_TYPE_VARS = [
   "TERM_PROGRAM",
   "TERMINAL_EMULATOR",
@@ -233681,6 +234051,7 @@ var getStatusIndicatorState = ({
 };
 
 // src/utils/terminal-title.ts
+init_env3();
 import { closeSync as closeSync3, constants as constants11, openSync as openSync3, writeSync as writeSync3 } from "fs";
 var MAX_TITLE_LENGTH = 60;
 var TITLE_PREFIX = "LevelCode: ";
@@ -237393,6 +237764,7 @@ init_project_files();
 init_analytics2();
 init_src();
 init_auth3();
+init_env3();
 init_logger2();
 
 // src/utils/project-picker.ts

package/package.json

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