I replaced Claude Code’s default --worktree command with a custom one built around Ghostty, Lazygit, and Yazi. By default, Claude Code creates worktrees inside the .claude/worktrees folder within the same project. That means if you spin up 3 worktrees, you end up with 3 complete copies of your project... nested inside your main project. It makes the project structure messy and difficult to manage. So I built a hook that: - Overrides the default --worktree command - Creates each branch in a sibling directory: ../worktrees/branch-name - Automatically opens Ghostty panes - Launches Lazygit and Yazi already positioned in the correct branch directory Install it with: npx claude-code-templates@latest --hook=development-tools/worktree-ghostty --yes Now each branch lives where it should, outside the main project, and your terminal environment is ready instantly.show more

nice! can you also optionally support workspaces+panes in with cmux cli?

how do you do the ghostty panes? did not know you could script those

You can do similar without the third party dep with a bash function like this

This is such a clean upgrade to Claude Code worktrees, love how you turned chaos into a focused branch playground 🚀

Or... Just use @conductor_build

Good luck with your permissions with a sibling! When inside the same repo you inherit the repo permissions

Love it!

I love your customization tools for ghostty and Claude Code, thanks for sharing! Do you use an IDE on top, or only the terminal?

tmux bro

Great workflow tweak. Keeping worktrees outside the repo is cleaner for fs watchers and usually cuts IDE index churn when multiple branches are open.

Nested worktrees inside the project dir = accidental complexity tax. Solving it at the hook layer with adjacent dirs is a small spatial shift, big cognitive payoff. Bookmarked.

moving worktrees to sibling directories is one of those fixes that seems small until you realize how much cognitive overhead messy project nesting adds. having lazygit and yazi ready in the right context on launch is a nice touch too. most people underestimate how much time they lose just navigating to the right place before they can start working

It's indeed a better DX than the default one! I didn't know that you can hook and overwrite the commands. How did you do that magic?

the sibling directory move is underrated. I've seen agents step on each other's files mid-task and it's chaos. isolation isn't just cleaner — it's the difference between reliable output and silent corruption nobody catches until production.

Nicely done! I also found hooks to be the ideal solution to parallel subagents. Furthermore, you can use context injection to avoid information repetition. Check it out here:

bro turned worktrees into a spa day for branches

This is awesome. If you want the editor part too, I made lazyide — lazygit-style TUI IDE made to run right next to Claude Code.

What's your ghostty setup? Looks amazing!

Super interesting Daniel, I need to try this.

@dani_avila7, Dani, custom worktrees offer better project organization.

This is cool. I built my own tool for worktrees management too. Love the integration for automation for lazygit and yazi. Stealing this for my claude hooks!

this is the kind of customization that makes claude code feel like a proper development environment and not just an AI chatbot in a terminal. the hooks system is so underrated. having ghostty panes auto launch with lazygit and yazi ready to go means you can actually context switch between worktrees without losing your flow. saving this for later

One assumes they do it within the workspace because that keeps them trivially all in the same sandbox workspace and so permissions apply across them.

that's slick, lazygit + yazi must speed things up??

Wanna try to add a setup_worktree hook like Cursor has?

This is so cool. Almost exactly what I have been looking for. Thank you for sharing.

Love how you smooth the workflow 💙 ⚡ Small tweaks like this make coding feel effortless and joyful.