Smart ergonomics — the pain of keeping .env files in sync across worktrees is real. Every worktree ends up with slightly different secret values and nobody knows which is current.
The deeper fix I'd love to see is integration with a secrets manager that owns the canonical values, so worktrees pull from a shared encrypted store rather than each maintaining their own .env copy. We built KeyEnv (https://keyenv.dev) for exactly that: `keyenv run -- npm start` and the process gets injected secrets from the team store. No file duplication, no drift.
Does Workz support custom commands on worktree creation? Could imagine a hook that runs `keyenv pull` or similar to bootstrap without a .env at all.
Smart ergonomics — the pain of keeping .env files in sync across worktrees is real. Every worktree ends up with slightly different secret values and nobody knows which is current.
The deeper fix I'd love to see is integration with a secrets manager that owns the canonical values, so worktrees pull from a shared encrypted store rather than each maintaining their own .env copy. We built KeyEnv (https://keyenv.dev) for exactly that: `keyenv run -- npm start` and the process gets injected secrets from the team store. No file duplication, no drift.
Does Workz support custom commands on worktree creation? Could imagine a hook that runs `keyenv pull` or similar to bootstrap without a .env at all.