openfox 2.0.65 → 2.0.67

package/dist/{chunk-BGTEIA2S.js → chunk-TFCHWMOJ.js}

@@ -9,30 +9,27 @@ import {
   startProcess,
   updateStatus
 } from "./chunk-PK2RMVMB.js";
+import {
+  getPlatformShell
+} from "./chunk-X5DOUA3Z.js";
 
-// src/server/tools/background-process/manager.ts
+// src/server/utils/shell.ts
 import { spawn } from "child_process";
-
-// src/server/utils/platform.ts
-import os from "os";
-function getPlatformShell() {
-  if (process.platform === "win32") {
-    return { command: "cmd.exe", args: ["/c"] };
-  }
-  const userShell = os.userInfo().shell;
-  if (userShell) {
-    return { command: userShell, args: ["-c"] };
-  }
-  return { command: "sh", args: ["-c"] };
+function checkAborted(signal) {
+  return !!signal?.aborted;
 }
-function getPathSeparator() {
-  return process.platform === "win32" ? ";" : ":";
-}
-function isWindowsPath(path) {
-  return /^[A-Za-z]:[/\\]/.test(path);
+function spawnShell(command, options) {
+  const shell = getPlatformShell();
+  return spawn(shell.command, [...shell.args, command], {
+    cwd: options.cwd,
+    env: { ...process.env },
+    stdio: options.stdio ?? ["ignore", "pipe", "pipe"],
+    windowsHide: true,
+    ...options.detached ? { detached: true } : {}
+  });
 }
-function isAbsolutePath(path) {
-  return path.startsWith("/") || isWindowsPath(path);
+function spawnShellProcess(command, cwd, _signal, detached = false) {
+  return spawnShell(command, { cwd, detached });
 }
 
 // src/server/tools/background-process/manager.ts
@@ -64,13 +61,9 @@ function createProcess2(sessionId, name, command, cwd, timeout) {
 function startProcessCommand(processId, sessionId, command, cwd) {
   const proc = startProcess(processId, sessionId, 0);
   if (!proc) return null;
-  const shell = getPlatformShell();
-  const child = spawn(shell.command, [...shell.args, command], {
+  const child = spawnShell(command, {
     cwd,
-    env: { ...process.env, FORCE_COLOR: "1" },
-    stdio: ["ignore", "pipe", "pipe"],
-    detached: true,
-    windowsHide: true
+    detached: true
   });
   proc.pid = child.pid ?? null;
   updateStatus(processId, sessionId, "running");
@@ -143,9 +136,9 @@ function getProcessLogs(processId, since = 0, maxLines) {
 }
 
 export {
-  getPlatformShell,
-  getPathSeparator,
-  isAbsolutePath,
+  checkAborted,
+  spawnShell,
+  spawnShellProcess,
   onProcessEvent,
   createProcess2 as createProcess,
   startProcessCommand,
@@ -154,4 +147,4 @@ export {
   getSessionProcesses2 as getSessionProcesses,
   getProcessLogs
 };
-//# sourceMappingURL=chunk-BGTEIA2S.js.map
+//# sourceMappingURL=chunk-TFCHWMOJ.js.map

package/dist/{chunk-AIJE3RYH.js → chunk-TFDK6VSG.js}

@@ -5,10 +5,10 @@ import {
   foldContextState,
   foldSessionState,
   spreadOptionalMessageFields
-} from "./chunk-TMUBLQFC.js";
+} from "./chunk-C3VLGVSQ.js";
 import {
   getDatabase
-} from "./chunk-ZPIZLTWU.js";
+} from "./chunk-GMXKJGJ2.js";
 import {
   logger
 } from "./chunk-K44MW7JJ.js";
@@ -680,21 +680,33 @@ function getProjectDangerLevel(projectId) {
     return "normal";
   }
 }
-function createSession(projectId, workdir, title, providerId, providerModel) {
+function createSession(projectId, workdir, title, providerId, providerModel, worktree) {
   const db = getDatabase();
   const now = (/* @__PURE__ */ new Date()).toISOString();
   const id = crypto.randomUUID();
   const dangerLevel = getProjectDangerLevel(projectId);
   db.prepare(
     `
-    INSERT INTO sessions (id, project_id, workdir, phase, mode, workflow_phase, is_running, created_at, updated_at, title, provider_id, provider_model, danger_level)
-    VALUES (?, ?, ?, 'idle', 'planner', 'plan', 0, ?, ?, ?, ?, ?, ?)
+    INSERT INTO sessions (id, project_id, workdir, worktree, phase, mode, workflow_phase, is_running, created_at, updated_at, title, provider_id, provider_model, danger_level)
+    VALUES (?, ?, ?, ?, 'idle', 'planner', 'plan', 0, ?, ?, ?, ?, ?, ?)
   `
-  ).run(id, projectId, workdir, now, now, title ?? null, providerId ?? null, providerModel ?? null, dangerLevel);
+  ).run(
+    id,
+    projectId,
+    workdir,
+    worktree ?? null,
+    now,
+    now,
+    title ?? null,
+    providerId ?? null,
+    providerModel ?? null,
+    dangerLevel
+  );
   return {
     id,
     projectId,
     workdir,
+    ...worktree ? { worktree } : {},
     mode: "planner",
     phase: "plan",
     isRunning: false,
@@ -843,6 +855,7 @@ function listSessions() {
       s.id,
       s.project_id,
       s.workdir,
+      s.worktree,
       s.mode,
       s.workflow_phase,
       s.is_running,
@@ -866,6 +879,7 @@ function listSessionsByProject(projectId, limit = 20, offset = 0) {
       s.id,
       s.project_id,
       s.workdir,
+      s.worktree,
       s.mode,
       s.workflow_phase,
       s.is_running,
@@ -885,6 +899,16 @@ function listSessionsByProject(projectId, limit = 20, offset = 0) {
   const sessions = rows.slice(0, limit).map(mapSessionSummaryRow);
   return { sessions, hasMore };
 }
+function updateSessionWorkdir(id, workdir, worktree) {
+  const db = getDatabase();
+  const now = (/* @__PURE__ */ new Date()).toISOString();
+  db.prepare("UPDATE sessions SET workdir = ?, worktree = ?, updated_at = ? WHERE id = ?").run(
+    workdir,
+    worktree,
+    now,
+    id
+  );
+}
 function deleteSession(id) {
   const db = getDatabase();
   db.prepare("DELETE FROM sessions WHERE id = ?").run(id);
@@ -894,6 +918,7 @@ function mapSessionBase(row) {
     id: row.id,
     projectId: row.project_id,
     workdir: row.workdir,
+    ...row.worktree ? { worktree: row.worktree } : {},
     mode: row.mode ?? "planner",
     phase: row.workflow_phase ?? "plan",
     isRunning: Boolean(row.is_running),
@@ -1396,6 +1421,7 @@ export {
   getSessionCachedPrompt,
   listSessions,
   listSessionsByProject,
+  updateSessionWorkdir,
   deleteSession,
   loadConfig,
   setRuntimeConfig,
@@ -1434,4 +1460,4 @@ export {
   truncateSessionMessages,
   getRecentUserPromptsForSession
 };
-//# sourceMappingURL=chunk-AIJE3RYH.js.map
+//# sourceMappingURL=chunk-TFDK6VSG.js.map

package/dist/{chunk-X5YCWKNS.js → chunk-TJO4QFDQ.js}

@@ -1,3 +1,6 @@
+import {
+  getPlatformShell
+} from "./chunk-X5DOUA3Z.js";
 import {
   streamWithSegments
 } from "./chunk-J2GP3J3X.js";
@@ -9,7 +12,7 @@ import {
 } from "./chunk-YHEQTVFV.js";
 import {
   buildModelParams
-} from "./chunk-Z6W4YHJB.js";
+} from "./chunk-BL5LOLVA.js";
 import {
   logger
 } from "./chunk-K44MW7JJ.js";
@@ -33,6 +36,7 @@ function computeEffectiveTools(allowedTools, type) {
 }
 
 // src/server/chat/prompts.ts
+import { basename } from "path";
 function buildBasePrompt(workdir, customInstructions, skills, modelName) {
   const instructionsSection = customInstructions ? `
 
@@ -47,120 +51,91 @@ Today's date is ${(/* @__PURE__ */ new Date()).toISOString().split("T")[0].repla
 
 ## ENVIRONMENT
 Working directory: ${workdir}
-Platform: ${process.platform} (${process.arch})${modelLine}
+Platform: ${process.platform} (${process.arch})
+Shell (run_command): ${basename(getPlatformShell().command)}${modelLine}
 
 ## CORE BEHAVIOR
-- Help the user complete any tasks safely and efficiently.
-- Do everything in your capacity to satisfy user requirements.
-- Read code before changing it.
-- Prefer precise, minimal changes.
-- Use available tools when needed.
-- Explain tradeoffs clearly when requirements are ambiguous.
-- Follow repository and project instructions exactly.
+Help user complete tasks safely and efficiently.
+Do everything to satisfy user requirements.
+Read file before editing.
+Prefer precise, minimal changes.
+Use available tools when needed.
+Explain tradeoffs clearly when requirements are ambiguous.
+Follow repository and project instructions exactly.
 
 ## MODE CONTROL
-- OpenFox may append system-generated runtime control messages as USER-role messages wrapped in <system-reminder>...</system-reminder>.
-- These reminders are authoritative framework instructions from OpenFox.
-- Treat them as higher-priority operational constraints than normal user task wording for the current turn.
-- Do not describe them as "the user reminded me"; they are runtime mode/control metadata injected by OpenFox.
+OpenFox appends runtime control as USER-role messages wrapped in <system-reminder>...</system-reminder>.
+These reminders are authoritative, treat them as higher-priority operational constraints.
+Never say "user reminded me"; they are runtime mode injected by OpenFox.
 
 ## WORKFLOW
-- If the current runtime reminder says planning mode, focus on understanding, exploration, clarification, and criteria quality.
-- If the current runtime reminder says build mode, focus on implementation, verification, and completing approved criteria.
-- Respect tool and permission constraints enforced by the server even if the conversation suggests otherwise.
-
-## FILE REFERENCES
-- The user may reference files or directories with an @ prefix, e.g. @src/index.ts or @web/components/.
-- These are paths relative to the working directory above. Strip the leading @ and resolve against the working directory \u2014 never treat an @-reference as an absolute path.
-
-## IMPORTANT GUARDRAILS
-- NEVER delete/git checkout an already modified file: that would result in a data loss.
-
-
-# Tone and style
-You should be concise, direct, and to the point. When you run a non-trivial bash command, you should explain what the command does and why you are running it, to make sure the user understands what you are doing (this is especially important when you are running a command that will make changes to the user's system).
-Remember that your output will be displayed on a command line interface. Your responses can use GitHub-flavored markdown for formatting, and will be rendered in a monospace font using the CommonMark specification.
-Output text to communicate with the user; all text you output outside of tool use is displayed to the user. Only use tools to complete tasks. Never use tools like Bash or code comments as means to communicate with the user during the session.
-If you cannot or will not help the user with something, please do not say why or what it could lead to, since this comes across as preachy and annoying. Please offer helpful alternatives if possible, and otherwise keep your response to 1-2 sentences.
-Only use emojis if the user explicitly requests it. Avoid using emojis in all communication unless asked.
-IMPORTANT: You should minimize output tokens as much as possible while maintaining helpfulness, quality, and accuracy. Only address the specific query or task at hand, avoiding tangential information unless absolutely critical for completing the request. If you can answer in 1-3 sentences or a short paragraph, please do.
-IMPORTANT: You should NOT answer with unnecessary preamble or postamble (such as explaining your code or summarizing your action), unless the user asks you to.
-IMPORTANT: Keep your responses short, since they will be displayed on a command line interface. You MUST answer concisely with fewer than 4 lines (not including tool use or code generation), unless user asks for detail. Answer the user's question directly, without elaboration, explanation, or details. One word answers are best. Avoid introductions, conclusions, and explanations. You MUST avoid text before/after your response, such as "The answer is <answer>.", "Here is the content of the file..." or "Based on the information provided, the answer is..." or "Here is what I will do next...". Here are some examples to demonstrate appropriate verbosity:
-<example>
+Reminder = planning mode: focus on understanding, exploration, clarification, criteria quality.
+Reminder = build mode: focus on implementation, verification, completing approved criteria.
+
+## TONE AND STYLE
+Be concise, direct, and to the point.
+Explain non-trivial bash commands (what & why).
+Output renders as CLI markdown (CommonMark).
+Only use tools for tasks, not communication.
+No emojis unless asked.
+Minimize tokens, stay on-topic.
+No preamble/postamble.
+Keep responses under ~4 lines unless detail requested.
+
+### Examples
 user: 2 + 2
 assistant: 4
-</example>
-
-<example>
-user: what is 2+2?
-assistant: 4
-</example>
-
-<example>
-user: is 11 a prime number?
-assistant: Yes
-</example>
 
-<example>
 user: what command should I run to list files in the current directory?
 assistant: ls
-</example>
 
-<example>
 user: what command should I run to watch files in the current directory?
 assistant: [use the ls tool to list the files in the current directory, then read docs/commands in the relevant file to find out how to watch files]
-npm run dev
-</example>
+  npm run dev
 
-<example>
-user: How many golf balls fit inside a jetta?
-assistant: 150000
-</example>
-
-<example>
 user: what files are in the directory src/?
 assistant: [runs ls and sees foo.c, bar.c, baz.c]
 user: which file contains the implementation of foo?
 assistant: src/foo.c
-</example>
 
-<example>
 user: write tests for new feature
-assistant: [uses grep and glob search tools to find where similar tests are defined, uses concurrent read file tool use blocks in one tool call to read relevant files at the same time, uses edit file tool to write new tests]
-</example>
+assistant: [uses run_command tool to find where similar tests are defined, uses concurrent read file tool use blocks in one tool call to read relevant files at the same time, uses edit file tool to write new tests]
+
+## FILE REFERENCES
+@ prefix, e.g. @src/index.ts or @web/components/.
+Relative to the working directory above. Strip leading @ and resolve against working directory, never treat as absolute path.
+
+## IMPORTANT GUARDRAILS
+NEVER delete/git checkout already modified file: would result in data loss.
 
 # Proactiveness
-You are allowed to be proactive, but only when the user asks you to do something. You should strive to strike a balance between:
+Allowed to be proactive, but only when user asks you to do something. Balance:
 1. Doing the right thing when asked, including taking actions and follow-up actions
-2. Not surprising the user with actions you take without asking
-For example, if the user asks you how to approach something, you should do your best to answer their question first, and not immediately jump into taking actions.
-3. Do not add additional code explanation summary unless requested by the user. After working on a file, just stop, rather than providing an explanation of what you did.
+2. Not surprising user with actions you take without asking
+For example, if user asks you how to approach something, you should do your best to answer their question first, and not immediately jump into taking actions.
+3. Do not add additional code explanation summary unless requested by user. After working on a file, just stop, rather than providing an explanation of what you did.
 
 # Following conventions
-When making changes to files, first understand the file's code conventions. Mimic code style, use existing libraries and utilities, and follow existing patterns.
-- NEVER assume that a given library is available, even if it is well known. Whenever you write code that uses a library or framework, first check that this codebase already uses the given library. For example, you might look at neighboring files, or check the package.json (or cargo.toml, and so on depending on the language).
-- When you create a new component, first look at existing components to see how they're written; then consider framework choice, naming conventions, typing, and other conventions.
-- When you edit a piece of code, first look at the code's surrounding context (especially its imports) to understand the code's choice of frameworks and libraries. Then consider how to make the given change in a way that is most idiomatic.
-- Always follow security best practices. Never introduce code that exposes or logs secrets and keys. Never commit secrets or keys to the repository.
+Understand file's code conventions. Mimic code style, use existing libraries and utilities, follow existing patterns.
+NEVER assume that a given library is available. To use library or framework, first check that codebase already uses given library.
+When you create new component, first look at existing components to see how written; then consider framework choice, naming conventions, typing, other conventions.
+When you edit code, look at code's surrounding context (imports) to understand code's choice of frameworks and libraries. Then consider how to make given change in way that is most idiomatic.
+Always follow security best practices. Never introduce code that exposes or logs secrets and keys. Never commit secrets or keys to the repository.
 
 # Code style
-- IMPORTANT: DO NOT ADD ***ANY*** COMMENTS unless asked
+IMPORTANT: DO NOT ADD ***ANY*** COMMENTS unless asked
 
 # Doing tasks
-The user will primarily request you perform software engineering tasks. This includes solving bugs, adding new functionality, refactoring code, explaining code, and more. For these tasks the following steps are recommended:
-- Use the available search tools to understand the codebase and the user's query. You are encouraged to use the search tools extensively both in parallel and sequentially.
-- Implement the solution using all tools available to you
-- Verify the solution if possible with tests. NEVER assume specific test framework or test script. Check the README or search codebase to determine the testing approach.
-- VERY IMPORTANT: When you have completed a task, you MUST run the lint and typecheck commands (e.g. npm run lint, npm run typecheck, ruff, etc.) with Bash if they were provided to you to ensure your code is correct. If you are unable to find the correct command, ask the user for the command to run and if they supply it, proactively suggest writing it to AGENTS.md so that you will know to run it next time.
-NEVER commit changes unless the user explicitly asks you to. It is VERY IMPORTANT to only commit when explicitly asked, otherwise the user will feel that you are being too proactive.
-
-- Tool results and user messages may include <system-reminder> tags. <system-reminder> tags contain useful information and reminders. They are NOT part of the user's provided input or the tool result.
+User will primarily request you perform software engineering tasks. This includes solving bugs, adding new functionality, refactoring code, explaining code, and more. For these tasks the following steps are recommended:
+Use run_command or Explorer sub-agent to understand the codebase and user's query.
+Implement solution using all tools available to you.
+Verify the solution if possible with tests. NEVER assume specific test framework or test script. Check README or search codebase to determine testing approach.
+VERY IMPORTANT: When you have completed a task, you MUST run lint and typecheck commands (e.g. npm run lint, npm run typecheck, ruff, etc.) with run_command to ensure your code is correct.
+NEVER commit changes unless user explicitly asks you to. VERY IMPORTANT only commit when explicitly asked, otherwise user will feel that you are being too proactive.
 
 # Tool usage policy
-- When doing file search, prefer to use the Task tool in order to reduce context usage.
-- You have the capability to call multiple tools in a single response. When multiple independent pieces of information are requested, batch your tool calls together for optimal performance. When making multiple bash tool calls, you MUST send a single message with multiple tools calls to run the calls in parallel. For example, if you need to run "git status" and "git diff", send a single message with two tool calls to run the calls in parallel.
-
-You MUST answer concisely with fewer than 4 lines of text (not including tool use or code generation), unless user asks for detail.
+When doing file search, prefer to use the call_sub_agent tool with the "explorer" in order to reduce context usage, except if this would take less than 3 calls to get the information.
+You have the capability to call multiple tools in a single response. When multiple independent pieces of information are requested, batch your tool calls together for optimal performance.
 
 ${instructionsSection}
 ${buildSkillsSection(skills)}
@@ -256,7 +231,6 @@ function buildAgentSmallReminder(name) {
 Reminder: you are in '${name}' mode.
 </system-reminder>`;
 }
-var WORKFLOW_KICKOFF_PROMPT = (criteriaCount) => `Implement the task and make sure you fulfil the ${criteriaCount} criteria.`;
 var COMPACTION_PROMPT = `You are a helpful AI assistant tasked with summarizing conversations for continuation.
 
 Summarize the conversation history concisely, preserving:
@@ -694,7 +668,6 @@ export {
   buildTopLevelSystemPrompt,
   buildAgentReminder,
   buildAgentSmallReminder,
-  WORKFLOW_KICKOFF_PROMPT,
   COMPACTION_PROMPT,
   streamLLMPure,
   TurnMetrics,
@@ -705,4 +678,4 @@ export {
   createChatDoneEvent,
   consumeStreamGenerator
 };
-//# sourceMappingURL=chunk-X5YCWKNS.js.map
+//# sourceMappingURL=chunk-TJO4QFDQ.js.map

package/dist/{chunk-QJ5FH5DP.js → chunk-TMHWQYWE.js}

@@ -2,11 +2,11 @@ import {
   getEventStore,
   getRuntimeConfig,
   updateSessionMetadata
-} from "./chunk-AIJE3RYH.js";
+} from "./chunk-TFDK6VSG.js";
 import {
   buildMessagesFromStoredEvents,
   foldPendingConfirmations
-} from "./chunk-TMUBLQFC.js";
+} from "./chunk-C3VLGVSQ.js";
 import {
   createContextStateMessage,
   createSessionStateMessage
@@ -135,7 +135,7 @@ async function generateSessionNameForSession(sessionId, userMessage, deps, signa
       client = deps.getLLMClient();
       client.setModel(providerConfig.model);
     } else if (providerConfig) {
-      const { createLLMClient } = await import("./client-LAKW7TA5.js");
+      const { createLLMClient } = await import("./client-BUX62J2K.js");
       client = createLLMClient({
         llm: {
           baseUrl: providerConfig.baseUrl,
@@ -184,4 +184,4 @@ export {
   buildRunChatTurnParams,
   generateSessionNameForSession
 };
-//# sourceMappingURL=chunk-QJ5FH5DP.js.map
+//# sourceMappingURL=chunk-TMHWQYWE.js.map

package/dist/chunk-VLV3XWZS.js

@@ -0,0 +1,191 @@
+import {
+  gitSpawnEnv
+} from "./chunk-WGMJCFCE.js";
+import {
+  logger
+} from "./chunk-K44MW7JJ.js";
+
+// src/server/git/worktree.ts
+import { spawn } from "child_process";
+import { mkdir, readFile, appendFile, stat, symlink } from "fs/promises";
+import { resolve } from "path";
+import copy from "@danieldietrich/copy";
+function captureStdout(cwd, args) {
+  return new Promise((resolvePromise) => {
+    const proc = spawn("git", args, { cwd, env: gitSpawnEnv(), stdio: ["ignore", "pipe", "ignore"] });
+    let out = "";
+    proc.stdout.on("data", (d) => {
+      out += d.toString();
+    });
+    proc.on("close", (code) => resolvePromise(code === 0 ? out : null));
+    proc.on("error", () => resolvePromise(null));
+  });
+}
+function runGit(cwd, args) {
+  return new Promise((resolvePromise, reject) => {
+    const proc = spawn("git", args, { cwd, env: gitSpawnEnv(), stdio: ["ignore", "pipe", "pipe"] });
+    let stderr = "";
+    proc.stderr.on("data", (d) => {
+      stderr += d.toString();
+    });
+    proc.on("close", (code) => {
+      if (code === 0) resolvePromise();
+      else reject(new Error(stderr.trim() || `git ${args[0]} failed (code ${code})`));
+    });
+    proc.on("error", (err) => reject(err));
+  });
+}
+function getGitBranch(cwd) {
+  return captureStdout(cwd, ["rev-parse", "--abbrev-ref", "HEAD"]).then((r) => r?.trim() ?? null);
+}
+function listWorktrees(cwd) {
+  return captureStdout(cwd, ["worktree", "list", "--porcelain"]).then((out) => {
+    if (!out) return [];
+    const entries = [];
+    let current = {};
+    for (const line of out.split("\n")) {
+      if (line.startsWith("worktree ")) current.path = line.slice(9);
+      else if (line.startsWith("branch ")) current.branch = line.slice(7).replace("refs/heads/", "");
+      else if (line === "" && current.path && current.branch) {
+        entries.push({ path: current.path, branch: current.branch });
+        current = {};
+      }
+    }
+    if (current.path && current.branch) entries.push({ path: current.path, branch: current.branch });
+    return entries;
+  });
+}
+function validateRef(cwd, name) {
+  return runGit(cwd, ["check-ref-format", `refs/heads/${name}`]);
+}
+function addWorktree(cwd, args) {
+  return runGit(cwd, ["worktree", "add", ...args]);
+}
+async function ensureWorktreesIgnored(projectDir) {
+  const gitignorePath = resolve(projectDir, ".gitignore");
+  let content = "";
+  try {
+    content = await readFile(gitignorePath, "utf-8");
+  } catch {
+  }
+  const lines = content.split("\n");
+  const hasWorktreesIgnore = lines.some(
+    (line) => line.trim() === "worktrees/" || line.trim() === "/worktrees/" || line.trim() === "worktrees"
+  );
+  if (hasWorktreesIgnore) return;
+  const entry = content.length > 0 && !content.endsWith("\n") ? "\nworktrees/\n" : "worktrees/\n";
+  await appendFile(gitignorePath, entry);
+}
+function listBranches(cwd) {
+  return captureStdout(cwd, ["branch", "--format", "%(refname:short)%09%(HEAD)"]).then((out) => {
+    if (!out) return [];
+    const branches = [];
+    for (const line of out.trim().split("\n")) {
+      if (!line) continue;
+      const [name, head] = line.split("	");
+      if (name) branches.push({ name, current: head === "*" });
+    }
+    return branches;
+  });
+}
+function checkoutBranch(cwd, name) {
+  return runGit(cwd, ["checkout", name]);
+}
+function createBranch(cwd, name) {
+  return runGit(cwd, ["checkout", "-b", name]);
+}
+function branchExists(cwd, name) {
+  return captureStdout(cwd, ["rev-parse", "--verify", `refs/heads/${name}`]).then((r) => r !== null);
+}
+async function ensureWorktree(projectDir, name, startBranch) {
+  await validateRef(projectDir, name);
+  const worktreesDir = resolve(projectDir, "worktrees");
+  const wtPath = resolve(worktreesDir, name.replace(/\//g, "-"));
+  await mkdir(worktreesDir, { recursive: true });
+  await ensureWorktreesIgnored(projectDir).catch((err) => {
+    logger.warn("Failed to update .gitignore", { projectDir, error: String(err) });
+  });
+  const startBranchResolved = startBranch ?? await getGitBranch(projectDir) ?? "main";
+  try {
+    const st = await stat(wtPath);
+    if (st.isDirectory()) return { path: wtPath, name };
+  } catch {
+  }
+  try {
+    await addWorktree(projectDir, ["-b", name, wtPath, startBranchResolved]);
+  } catch (err) {
+    const exists = await branchExists(projectDir, name);
+    if (exists) {
+      await addWorktree(projectDir, [wtPath, name]);
+    } else {
+      throw err;
+    }
+  }
+  return { path: wtPath, name };
+}
+async function getIgnoredDirectories(projectDir) {
+  const out = await captureStdout(projectDir, [
+    "ls-files",
+    "--others",
+    "--ignored",
+    "--exclude-standard",
+    "--directory"
+  ]);
+  if (!out) return [];
+  return out.trim().split("\n").filter(Boolean);
+}
+function resolveStrategy(relPath, config) {
+  const normalized = relPath.replace(/\/$/, "");
+  const basename = normalized.split("/").pop() ?? normalized;
+  return config.overrides?.[normalized] ?? config.overrides?.[basename] ?? config.ignoredAssets;
+}
+async function syncIgnoredAssets(projectDir, worktreePath, config) {
+  const ignoredPaths = await getIgnoredDirectories(projectDir);
+  if (ignoredPaths.length === 0) return;
+  const results = [];
+  for (const relPath of ignoredPaths) {
+    const sourcePath = resolve(projectDir, relPath);
+    const targetPath = resolve(worktreePath, relPath);
+    try {
+      await stat(sourcePath);
+    } catch {
+      continue;
+    }
+    const strategy = resolveStrategy(relPath, config);
+    if (strategy === "skip") continue;
+    try {
+      if (strategy === "symlink") {
+        try {
+          await stat(targetPath);
+          continue;
+        } catch {
+        }
+        await symlink(sourcePath, targetPath);
+        results.push(`symlink ${relPath}`);
+      } else if (strategy === "copy") {
+        await copy(sourcePath, targetPath);
+        results.push(`copy ${relPath}`);
+      }
+    } catch (err) {
+      logger.warn("Failed to sync ignored asset to worktree", { relPath, strategy, error: String(err) });
+    }
+  }
+  if (results.length > 0) {
+    logger.info("Synced ignored assets to worktree", { count: results.length, actions: results });
+  }
+}
+
+export {
+  getGitBranch,
+  listWorktrees,
+  validateRef,
+  addWorktree,
+  ensureWorktreesIgnored,
+  listBranches,
+  checkoutBranch,
+  createBranch,
+  ensureWorktree,
+  getIgnoredDirectories,
+  syncIgnoredAssets
+};
+//# sourceMappingURL=chunk-VLV3XWZS.js.map

package/dist/chunk-WGMJCFCE.js

@@ -0,0 +1,14 @@
+// src/server/git/env.ts
+function gitSpawnEnv() {
+  const env = { ...process.env };
+  delete env["GIT_DIR"];
+  delete env["GIT_INDEX_FILE"];
+  delete env["GIT_WORK_TREE"];
+  delete env["GIT_PREFIX"];
+  return env;
+}
+
+export {
+  gitSpawnEnv
+};
+//# sourceMappingURL=chunk-WGMJCFCE.js.map