I think direnv would actually play nicely with what we're working on https://coasts.dev. It's for isolating docker-compose runtimes so you can run multiple localhost runtimes and assign them to your various worktrees.

We specifically don't solve the env vars per directory problem, so this is really cool to see.

It's crazy the see the amount of hackery we're all having to figure out with worktrees, way cool to see all these solutions popping up.

Thanks - I use worktrees and direnv but never thought about this ennrc trick to auto-share .env across worktrees.

Roocode has a nice feature called .worktreeinclude -- if you have a file in both .git ignore and that file, it will copy it into new worktrees.

I just use the WorktreeCreate hook in Claude to copy over the .env file.

This is how I currently use Git worktrees. Curious about how you are using it.

Oh, that's a really nice approach. Thank you for sharing.