@iloom/cli 0.1.19 → 0.3.0

package/README.md

@@ -10,13 +10,12 @@
 </div>
 
 <div align="center">
-  <img width="327" height="328" alt="iloom-ai-logo" src="https://raw.githubusercontent.com/iloom-ai/iloom-cli/main/assets/iloom-logo.png" />
-  <div>Scale understanding, not just output.</div>
-
+  <img width="600" alt="iloom-ai-screenshot" src="https://raw.githubusercontent.com/iloom-ai/iloom-cli/main/assets/iloom-screenshot.png" />
+  <div>iloom in action: Scale understanding, not just output.</div>
 </div>
 
 #### Links to key sections
-[How It Works](#how-it-works) • [Installation](#installation) • [Commands](#commands) • [Feedback](#providing-feedback) • [Limitations](#platform--integration-support) • [Configuration](#configuration)
+[How It Works](#how-it-works) • [Installation](#installation) • [Commands](#commands) • [Nested Looms](#child-looms-nested-looms) • [Limitations](#platform--integration-support) • [Configuration](#configuration) • [Feedback](#providing-feedback)
 
 
 ## Built For Modern Tools...
@@ -313,10 +312,22 @@ iloom start <issue-number | pr-number | issue-description | branch-name>
 #                        default: Standard behavior with prompts
 #                        noReview: Skip phase approval prompts
 #                        bypassPermissions: Full automation, skip all permission prompts. Be careful!
+#   --child-loom       - Force create as child loom (skip prompt, requires parent loom)
+#   --no-child-loom    - Force create as independent loom (skip prompt)
 
 iloom finish
 # AI assisted validation, commit, merge steps, as well as loom cleanup (run this from the loom directory)
+# Behavior depends on mergeBehavior.mode setting:
+#   local (default): Merge locally and cleanup
+#   github-pr: Push branch, create PR, prompt for cleanup
 # Alias: dn
+# Options:
+#   -f, --force        - Skip confirmation prompts
+#   -n, --dry-run      - Preview actions without executing
+#   --skip-build       - Skip post-merge build verification
+#   --no-browser       - Skip opening PR in browser (github-pr mode only)
+#   --cleanup          - Clean up worktree after PR creation (github-pr mode only)
+#   --no-cleanup       - Keep worktree after PR creation (github-pr mode only)
 
 iloom rebase
 # Rebase current branch on main with Claude-assisted conflict resolution (run this from a loom directory)
@@ -352,6 +363,100 @@ iloom enhance <issue-number>
 # Expands requirements, asks clarifying questions and adds implementation context
 ```
 
+## Child Looms (Nested Looms)
+
+Child looms let you create isolated workspaces from within an existing loom. This is useful when you need to work on a subtask, bug fix, or experiment while keeping your parent work intact.
+
+### When to Use Child Looms
+
+- **Break down complex issues**: Large features can spawn smaller issues that become child looms
+- **Fix bugs discovered during work**: Create a child loom to fix a bug without mixing commits
+- **Experiment safely**: Try different approaches in child looms without affecting parent work
+- **Handle interrupts**: Start urgent work from your current context without losing it
+
+### How Child Looms Work
+
+When you run `il start` from inside an existing loom, iloom detects the parent context and prompts you:
+
+```bash
+# Inside a loom working on issue #25
+> il start 42
+? Create as child loom of issue #25? (Y/n)
+```
+
+**Automatic inheritance:**
+- **Database branch**: Child looms branch from the parent's database state, not the main branch
+- **Base branch**: Git branch is created from the parent's branch
+- **Main branch config**: Child's `mainBranch` setting points to parent branch (for `il finish`)
+
+### CLI Flags
+
+Skip the prompt with explicit flags:
+
+```bash
+# Force child loom creation (no prompt)
+il start 42 --child-loom
+
+# Force independent loom (no prompt)
+il start 42 --no-child-loom
+```
+
+The `--child-loom` flag is ignored when not running from inside a loom.
+
+### Directory Structure
+
+Child looms are created in a dedicated subdirectory based on the parent branch name:
+
+```
+~/project-looms/
+├── feat-issue-25-auth-refactor/           # Parent loom
+├── feat-issue-25-auth-refactor-looms/     # Child looms directory
+│   ├── fix-issue-42-token-validation/     # Child loom 1
+│   └── feat-issue-43-oauth-support/       # Child loom 2
+```
+
+### Finishing Child Looms
+
+When finishing a parent loom, iloom warns about existing child looms:
+
+```bash
+> il finish
+⚠ Found 2 child loom(s) that should be cleaned up first:
+  - ~/project-looms/feat-issue-25-auth-refactor-looms/fix-issue-42-token-validation
+  - ~/project-looms/feat-issue-25-auth-refactor-looms/feat-issue-43-oauth-support
+
+To clean up child looms:
+  il cleanup 42
+  il cleanup 43
+```
+
+Child looms should typically be finished or cleaned up before finishing the parent.
+
+### Example Workflow
+
+```bash
+# Start working on a feature
+> il start 25
+# ... working on authentication refactor
+
+# Discover a bug that needs immediate attention
+> il start 42
+? Create as child loom of issue #25? Y
+# Creates child loom with parent's database state
+
+# Fix the bug in isolation
+> cd ~/project-looms/feat-issue-25-auth-refactor-looms/fix-issue-42-...
+
+# Finish the child work (merges to parent branch, not main)
+> il finish
+
+# Return to parent loom
+> cd ~/project-looms/feat-issue-25-auth-refactor
+
+# Continue feature work, then finish
+> il finish
+```
+
 ## Providing Feedback
 
 Found a bug, have a feature request, or want to contribute ideas to improve iloom CLI? Submit feedback directly from your terminal.
@@ -381,19 +486,6 @@ Your feedback helps make iloom better for everyone! Issues created through `iloo
 ### Maintenance
 
 ```bash
-iloom init
-# Interactive Claude-powered configuration wizard
-# Sets up settings.json, .gitignore, and guides you through all configuration options
-# Automatically detects multi-remote setups and helps you configure GitHub integration
-# Alias: il config
-# Run this once per project
-
-iloom contribute
-# Set up local development environment for contributing to iloom
-# Automatically forks the repository, clones it locally, configures upstream remote,
-# and runs il init to complete setup
-# Streamlines contributor onboarding with a single command
-
 iloom update
 # Update iloom-cli to the latest version
 ```
@@ -407,7 +499,7 @@ The recommended way to configure iloom:
 ```bash
 iloom init
 # or
-il config
+iloom config
 ```
 
 This Claude-powered assistant will guide you through all configuration options and automatically:
@@ -427,14 +519,18 @@ If you prefer manual configuration, iloom uses these files (highest to lowest pr
 1. **CLI arguments** - Command-line flags (e.g., `--one-shot bypassPermissions`)
 2. **`.iloom/settings.local.json`** - Local machine settings (gitignored, not committed)
 3. **`.iloom/settings.json`** - Project-wide settings (committed to repository)
-4. **Built-in defaults** - Hardcoded fallback values
+4. **`~/.config/iloom-ai/settings.json`** - Global user settings (applies to all projects)
+5. **Built-in defaults** - Hardcoded fallback values
 
-This allows teams to share project defaults via `settings.json` while individual developers maintain personal overrides in `settings.local.json`.
+This allows teams to share project defaults via `settings.json` while individual developers maintain personal overrides in `settings.local.json` or global preferences in `~/.config/iloom-ai/settings.json`.
 
 **Example Use Cases:**
-- Developer needs different `basePort` due to port conflicts
-- Local database connection strings that differ from team defaults
-- Personal preferences for `permissionMode` or component launch flags
+- **Global settings**: Default agent models or workflow permission modes that apply to all your projects
+- **Project settings**: Team defaults like `mainBranch`, database configuration, GitHub remote
+- **Local settings**: Machine-specific overrides like different `basePort` due to port conflicts, local database URLs, personal workflow preferences
+
+**Global Settings:**
+Global settings are stored in `~/.config/iloom-ai/settings.json` and apply to all iloom projects on your machine. Use these for personal preferences like default agent models or workflow permission modes. Project-specific settings (like database configuration) should remain in project config files.
 
 **Note:** The `.iloom/settings.local.json` file is automatically created and gitignored when you run `il init`.
 
@@ -443,6 +539,11 @@ This allows teams to share project defaults via `settings.json` while individual
 ```jsonc
 {
   "mainBranch": "main",
+  "sourceEnvOnStart": false,  // Source .env in terminal launches (default: false)
+  "mergeBehavior": {
+    "mode": "local",  // or "github-pr" for PR-based workflows
+    "remote": "upstream"  // optional, defaults to issueManagement.github.remote
+  },
   "capabilities": {
     "web": { "basePort": 3000 },
     "database": { "databaseUrlEnvVarName": "DATABASE_URL" }
@@ -477,6 +578,9 @@ This allows teams to share project defaults via `settings.json` while individual
 
 ** Common configuration options:**
 - `mainBranch` - Primary branch for merging (default: "main")
+- `sourceEnvOnStart` - Source .env file when launching terminal processes (default: false)
+- `mergeBehavior.mode` - How to finish work: "local" (merge locally) or "github-pr" (create PR) (default: "local")
+- `mergeBehavior.remote` - Remote to target for PRs (optional, defaults to `issueManagement.github.remote`)
 - `capabilities.web.basePort` - Base port for dev servers (default: 3000)
 - `capabilities.database.databaseUrlEnvVarName` - Name of environment variable for database connection URL (default: "DATABASE_URL")
 - `databaseProviders.neon.projectId` - Neon project ID (found in project URL, e.g., "fantastic-fox-3566354")
@@ -491,15 +595,149 @@ Example: Issue #25 with basePort 3000 = port 3025
 
 For complete configuration reference, see [.iloom/README.md](./.iloom/README.md)
 
+### IDE Configuration
+
+Configure which IDE launches when starting a loom:
+
+```jsonc
+{
+  "ide": {
+    "type": "cursor"  // or: vscode, webstorm, sublime, intellij, windsurf
+  }
+}
+```
+
+**Supported IDEs:**
+
+| Type | Command | Notes |
+|------|---------|-------|
+| `vscode` | `code` | Default. Visual Studio Code |
+| `cursor` | `cursor` | Cursor AI editor |
+| `webstorm` | `webstorm` | JetBrains WebStorm (launches with --nosplash) |
+| `sublime` | `subl` | Sublime Text |
+| `intellij` | `idea` | JetBrains IntelliJ IDEA (launches with --nosplash) |
+| `windsurf` | `windsurf` | Windsurf editor |
+
+**Configure via CLI:** Use the existing `--set` flag:
+
+```bash
+il start 25 --set ide.type=cursor
+```
+
+**Configure during setup:** Run `il init` to configure IDE preference interactively along with other settings.
+
+**Note:** Color synchronization (title bar colors) only works with VSCode-compatible editors (vscode, cursor, windsurf). Other IDEs will launch without color theming.
+
+## Issue Tracker Integration
+
+iloom supports multiple issue tracking systems through a provider abstraction. Choose GitHub or Linear based on your team's workflow.
+
+### GitHub (Default)
+
+GitHub is the default issue tracker and requires no additional configuration beyond authentication with the `gh` CLI.
+
+**Setup:**
+```bash
+# Authenticate with GitHub CLI
+gh auth login
+
+# Start using iloom with GitHub issues
+il start 123
+il start PR-456
+```
+
+**Configuration:**
+```jsonc
+{
+  "issueManagement": {
+    "provider": "github",  // Default, can be omitted
+    "github": {
+      "remote": "origin"  // Optional, defaults to "origin"
+    }
+  }
+}
+```
+
+### Linear
+
+iloom integrates with Linear through the official `@linear/sdk`, enabling full Linear issue tracking support.
+
+**Setup:**
+
+1. Get your Linear API token from [Linear Settings → API → Personal API Keys](https://linear.app/settings/api)
+
+2. Configure iloom to use Linear:
+   ```bash
+   il init
+   # Follow prompts to:
+   # - Select Linear as your issue tracker
+   # - Enter your Linear team ID (e.g., "ENG")
+   # - Enter your Linear API token (saved securely to settings.local.json)
+   ```
+
+   Or manually configure:
+
+   Edit `.iloom/settings.local.json` (for sensitive data):
+   ```jsonc
+   {
+     "issueManagement": {
+       "provider": "linear",
+       "linear": {
+         "teamId": "ENG",  // Required: Your Linear team key
+         "apiToken": "lin_api_..."  // Required: Your Linear API token
+       }
+     }
+   }
+   ```
+
+   **Important:** The `apiToken` should be stored in `settings.local.json` (not committed to git), not in `settings.json`. The init command will automatically save it to the correct location.
+
+   Alternatively, use an environment variable:
+   ```bash
+   export LINEAR_API_TOKEN="lin_api_..."
+   ```
+
+   Settings take precedence over environment variables.
+
+**Usage:**
+
+```bash
+# Start working on a Linear issue
+il start ENG-123
+
+# Create a new Linear issue
+il start "Add user authentication"
+
+# Finish and merge
+il finish
+```
+
+**Features:**
+
+- Full CRUD operations on issues and comments via the official Linear SDK
+- MCP integration for Claude AI assistance with Linear issues
+- Automatic workspace creation with Linear issue context
+
+**Limitations:**
+
+- Linear does not have pull requests. Use `il finish` with `mergeBehavior.mode: "local"` or `"github-pr"` to merge your code.
+
+**Port Calculation:**
+
+Linear issue identifiers (e.g., ENG-123) use hash-based port calculation instead of simple numeric addition. The port is deterministically generated from the branch name, ensuring consistency across sessions.
+
 ## Requirements
 
 **Essential:**
 - Claude CLI - AI assistance with issue context preloaded
 - Node.js 16+
 - Git 2.5+ (for worktree support)
-- GitHub CLI (`gh`) - authenticated with your repository
 
-**Recommended**
+**Issue Tracker (choose one):**
+- **GitHub CLI (`gh`)** - For GitHub issue tracking (default)
+- **Linear CLI (`linearis`)** - For Linear issue tracking (install with `npm install -g linearis`)
+
+**Recommended:**
 - A Claude Max subscription - iloom uses your own subscription
 
 **Optional (auto-detected):**
@@ -528,6 +766,8 @@ This is an early stage product - platform/tech stack support is limited for now.
 
 We (Claude and I) are actively working on expanding platform and integration support. Contributions welcome!
 
+See all [`known-limitation`](https://github.com/iloom-ai/iloom-cli/issues?q=is%3Aissue+is%3Aopen+label%3Aknown-limitation) issues for details and to [contribute](CONTRIBUTING.md) solutions.
+
 ## Installation
 
 ```bash
@@ -724,11 +964,31 @@ Other tools increase code output with minimal process change. iloom increases **
 
 ## Contributing
 
-This project follows Test-Driven Development. All code must:
-- Be written test-first with comprehensive unit tests
-- Achieve >70% code coverage
-- Include regression tests against bash script behavior
-- Use mock factories for all external dependencies
+We welcome contributions! Whether you're fixing a bug, adding a feature, or improving documentation, there are multiple ways to get involved.
+
+### Quick Start for Contributors
+
+The fastest way to get started contributing:
+
+```bash
+iloom contribute # requires the github CLI (gh)
+```
+
+This automated command handles forking, cloning, and setting up your development environment.
+
+### Finding Your First Issue
+
+New contributors should start with issues labeled [`starter-task`](https://github.com/iloom-ai/iloom-cli/issues?q=is%3Aissue+is%3Aopen+label%3Astarter-task) - these are designed to help you learn the iloom workflow and codebase while making meaningful contributions.
+
+### Full Contributing Guide
+
+For detailed information about our development process, testing requirements, and workflow, see our comprehensive [Contributing Guide](CONTRIBUTING.md).
+
+**Key highlights:**
+- Behavior-focused testing principles
+- AI-assisted development workflow using iloom itself
+- Clear PR process and code quality standards
+- Test-Driven Development with >70% coverage requirement
 
 ## License
 

package/dist/BranchNamingService-3OQPRSWT.js

@@ -0,0 +1,13 @@
+#!/usr/bin/env node
+import {
+  ClaudeBranchNameStrategy,
+  DefaultBranchNamingService,
+  SimpleBranchNameStrategy
+} from "./chunk-3KATJIKO.js";
+import "./chunk-GEHQXLEI.js";
+export {
+  ClaudeBranchNameStrategy,
+  DefaultBranchNamingService,
+  SimpleBranchNameStrategy
+};
+//# sourceMappingURL=BranchNamingService-3OQPRSWT.js.map

package/dist/ClaudeContextManager-MUQSDY2E.js

@@ -0,0 +1,13 @@
+#!/usr/bin/env node
+import {
+  ClaudeContextManager
+} from "./chunk-C5QCTEQK.js";
+import "./chunk-FIAT22G7.js";
+import "./chunk-XXV3UFZL.js";
+import "./chunk-WEN5C5DM.js";
+import "./chunk-ML3NRPNB.js";
+import "./chunk-GEHQXLEI.js";
+export {
+  ClaudeContextManager
+};
+//# sourceMappingURL=ClaudeContextManager-MUQSDY2E.js.map

package/dist/ClaudeService-HG4VQ7AW.js

@@ -0,0 +1,12 @@
+#!/usr/bin/env node
+import {
+  ClaudeService
+} from "./chunk-FIAT22G7.js";
+import "./chunk-XXV3UFZL.js";
+import "./chunk-WEN5C5DM.js";
+import "./chunk-ML3NRPNB.js";
+import "./chunk-GEHQXLEI.js";
+export {
+  ClaudeService
+};
+//# sourceMappingURL=ClaudeService-HG4VQ7AW.js.map

package/dist/GitHubService-EBOETDIW.js

@@ -0,0 +1,11 @@
+#!/usr/bin/env node
+import {
+  GitHubService
+} from "./chunk-G2IEYOLQ.js";
+import "./chunk-3RUPPQRG.js";
+import "./chunk-JKXJ7BGL.js";
+import "./chunk-GEHQXLEI.js";
+export {
+  GitHubService
+};
+//# sourceMappingURL=GitHubService-EBOETDIW.js.map

package/dist/{LoomLauncher-UMMLPIZO.js → LoomLauncher-FLEMBCSQ.js}

@@ -1,22 +1,22 @@
 #!/usr/bin/env node
 import {
   getDevServerLaunchCommand
-} from "./chunk-GZP4UGGM.js";
-import "./chunk-BLCTGFZN.js";
+} from "./chunk-ZM3CFL5L.js";
+import "./chunk-ZT3YZB4K.js";
 import {
   ClaudeContextManager
-} from "./chunk-DEPYQRRB.js";
+} from "./chunk-C5QCTEQK.js";
+import "./chunk-FIAT22G7.js";
+import "./chunk-XXV3UFZL.js";
+import "./chunk-WEN5C5DM.js";
+import "./chunk-ML3NRPNB.js";
 import {
   openMultipleTerminalWindows,
   openTerminalWindow
-} from "./chunk-RSRO7564.js";
+} from "./chunk-ZE74H5BR.js";
 import {
   generateColorFromBranchName
 } from "./chunk-ZZZWQGTS.js";
-import "./chunk-ELFT36PV.js";
-import "./chunk-PXZBAC2M.js";
-import "./chunk-PVAVNJKS.js";
-import "./chunk-VYQLLHZ7.js";
 import {
   logger
 } from "./chunk-GEHQXLEI.js";
@@ -25,42 +25,71 @@ import {
 import { existsSync } from "fs";
 import { join } from "path";
 
-// src/utils/vscode.ts
+// src/utils/ide.ts
 import { execa } from "execa";
-async function isVSCodeAvailable() {
+var IDE_PRESETS = {
+  vscode: { command: "code", name: "Visual Studio Code", args: [] },
+  cursor: { command: "cursor", name: "Cursor", args: [] },
+  webstorm: { command: "webstorm", name: "WebStorm", args: ["--nosplash"] },
+  sublime: { command: "subl", name: "Sublime Text", args: [] },
+  intellij: { command: "idea", name: "IntelliJ IDEA", args: ["--nosplash"] },
+  windsurf: { command: "surf", name: "Windsurf", args: [] }
+};
+function getIdeConfig(ideSettings) {
+  const type = (ideSettings == null ? void 0 : ideSettings.type) ?? "vscode";
+  const preset = IDE_PRESETS[type];
+  return {
+    command: preset.command,
+    args: [...preset.args],
+    name: preset.name
+  };
+}
+async function isIdeAvailable(command) {
   try {
-    await execa("command", ["-v", "code"], {
-      shell: true,
-      timeout: 5e3
-    });
+    await execa("command", ["-v", command], { shell: true, timeout: 5e3 });
     return true;
-  } catch (error) {
-    logger.debug("VSCode CLI not available", { error });
+  } catch {
     return false;
   }
 }
-async function openVSCodeWindow(workspacePath) {
-  const available = await isVSCodeAvailable();
+function getInstallHint(type) {
+  const hints = {
+    vscode: `Install command-line tools: Open VSCode > Command Palette > "Shell Command: Install 'code' command in PATH"`,
+    cursor: `Install command-line tools: Open Cursor > Command Palette > "Install 'cursor' command in PATH"`,
+    webstorm: "Install via JetBrains Toolbox > Settings > Shell Scripts > Enable",
+    sublime: 'Create symlink: ln -s "/Applications/Sublime Text.app/Contents/SharedSupport/bin/subl" /usr/local/bin/subl',
+    intellij: "Install via JetBrains Toolbox > Settings > Shell Scripts > Enable",
+    windsurf: "Install command-line tools during Windsurf installation or create symlink manually"
+  };
+  return hints[type] ?? `Ensure the IDE command is available in your PATH`;
+}
+async function openIdeWindow(workspacePath, ideSettings) {
+  const config = getIdeConfig(ideSettings);
+  const available = await isIdeAvailable(config.command);
   if (!available) {
+    const type = (ideSettings == null ? void 0 : ideSettings.type) ?? "vscode";
     throw new Error(
-      `VSCode is not available. Please install VSCode and ensure the "code" command is in your PATH.
-Install command-line tools: Open VSCode > Command Palette > "Shell Command: Install 'code' command in PATH"`
+      `${config.name} is not available. The "${config.command}" command was not found in PATH.
+` + getInstallHint(type)
     );
   }
   try {
-    await execa("code", [workspacePath]);
-    logger.debug(`Opened VSCode for workspace: ${workspacePath}`);
+    await execa(config.command, [...config.args, workspacePath]);
+    logger.debug(`Opened ${config.name} for workspace: ${workspacePath}`);
   } catch (error) {
     throw new Error(
-      `Failed to open VSCode: ${error instanceof Error ? error.message : "Unknown error"}`
+      `Failed to open ${config.name}: ${error instanceof Error ? error.message : "Unknown error"}`
     );
   }
 }
 
 // src/lib/LoomLauncher.ts
 var LoomLauncher = class {
-  constructor(claudeContext) {
+  constructor(claudeContext, settings) {
     this.claudeContext = claudeContext ?? new ClaudeContextManager();
+    if (settings !== void 0) {
+      this.settings = settings;
+    }
   }
   /**
    * Launch loom components based on individual flags
@@ -114,11 +143,13 @@ var LoomLauncher = class {
     logger.success("loom launched successfully");
   }
   /**
-   * Launch VSCode
+   * Launch IDE (VSCode or configured alternative)
    */
   async launchVSCode(options) {
-    await openVSCodeWindow(options.worktreePath);
-    logger.info("VSCode opened");
+    var _a;
+    const ideConfig = await ((_a = this.settings) == null ? void 0 : _a.loadSettings().then((s) => s.ide));
+    await openIdeWindow(options.worktreePath, ideConfig);
+    logger.info("IDE opened");
   }
   /**
    * Launch Claude terminal
@@ -151,7 +182,7 @@ var LoomLauncher = class {
       workspacePath: options.worktreePath,
       command: devServerCommand,
       backgroundColor: colorData.rgb,
-      includeEnvSetup: existsSync(join(options.worktreePath, ".env")),
+      includeEnvSetup: (options.sourceEnvOnStart ?? false) && existsSync(join(options.worktreePath, ".env")),
       includePortExport: options.capabilities.includes("web"),
       ...options.port !== void 0 && { port: options.port }
     });
@@ -165,7 +196,7 @@ var LoomLauncher = class {
     await openTerminalWindow({
       workspacePath: options.worktreePath,
       backgroundColor: colorData.rgb,
-      includeEnvSetup: existsSync(join(options.worktreePath, ".env")),
+      includeEnvSetup: (options.sourceEnvOnStart ?? false) && existsSync(join(options.worktreePath, ".env")),
       includePortExport: options.capabilities.includes("web"),
       ...options.port !== void 0 && { port: options.port }
     });
@@ -193,7 +224,7 @@ var LoomLauncher = class {
       command: claudeCommand,
       backgroundColor: colorData.rgb,
       title: claudeTitle,
-      includeEnvSetup: hasEnvFile,
+      includeEnvSetup: (options.sourceEnvOnStart ?? false) && hasEnvFile,
       ...options.port !== void 0 && { port: options.port, includePortExport: true }
     };
   }
@@ -214,7 +245,7 @@ var LoomLauncher = class {
       command: devServerCommand,
       backgroundColor: colorData.rgb,
       title: devServerTitle,
-      includeEnvSetup: hasEnvFile,
+      includeEnvSetup: (options.sourceEnvOnStart ?? false) && hasEnvFile,
       includePortExport: options.capabilities.includes("web"),
       ...options.port !== void 0 && { port: options.port }
     };
@@ -230,7 +261,7 @@ var LoomLauncher = class {
       workspacePath: options.worktreePath,
       backgroundColor: colorData.rgb,
       title: terminalTitle,
-      includeEnvSetup: hasEnvFile,
+      includeEnvSetup: (options.sourceEnvOnStart ?? false) && hasEnvFile,
       includePortExport: options.capabilities.includes("web"),
       ...options.port !== void 0 && { port: options.port }
     };
@@ -260,4 +291,4 @@ var LoomLauncher = class {
 export {
   LoomLauncher
 };
-//# sourceMappingURL=LoomLauncher-UMMLPIZO.js.map
+//# sourceMappingURL=LoomLauncher-FLEMBCSQ.js.map