Repository navigation
Copy gitignored config files (.env) into new worktrees (.worktreeinclude) #185
Description
What competitors do
Conductor supports a checked-in .worktreeinclude file listing gitignored paths copied verbatim into each new worktree (docs); Emdash preserves configuration files (.env, etc.) to the worktree on task creation.
Solenta today
setupWorktree (electron/worktrees.js:501-536) is exactly git worktree add and nothing else. #153 covers setup SCRIPTS; this is the simpler declarative sibling.
Why it matters
Every thread starts in a worktree missing .env, local certs or fixture DBs, so the agent's first minutes are spent rediscovering "database won't connect." Both Conductor and Emdash treat this as core, not optional.
Fix direction
On worktree creation, read .worktreeinclude (or a sensible default list like .env*) from the repo root and copy the listed gitignored paths into the new worktree.
Activity
currentbits commentedon Aug 19, 2026
Claude Code Desktop uses
.worktreeincludewith the same name and semantics — "to include gitignored files like.envin new worktrees, create a.worktreeincludefile in your project root" (docs). Convergent naming; nothing to change.Two adjacent settings they expose that Solenta hardcodes:
<project-root>/.claude/worktrees/, user-overridable to a custom directory. Users on encrypted or synced home directories, or with tooling that scans the repo root, need worktrees somewhere else.coder/<slug>-<hash>; teams with branch naming policy or CI branch filters cannot adopt that.Both are one store field and one call site each.
Copy gitignored config (.env) into new worktrees via .worktreeinclude (…
Copy gitignored config (.env) into new worktrees via .worktreeinclude (…
currentbits commentedon Oct 10, 2026
Shipped in #1563 (08c1d5a): new worktrees get untracked+gitignored files matching
.worktreeinclude, or root.env*by default. Copied before the #153 setup script; never overwrites; best-effort.Copy gitignored config (.env) into new worktrees via .worktreeinclude (…