# Worktree structures, workflow events, and enum metadata Page: https://stenobird.com/podcast/north-meets-south-web-podcast-706861/worktree-structures-workflow-events-and-enum-metadata Text version: https://stenobird.com/podcast/north-meets-south-web-podcast-706861/worktree-structures-workflow-events-and-enum-metadata.md Podcast: [North Meets South Web Podcast](https://stenobird.com/podcast/north-meets-south-web-podcast-706861) Published: 2026-03-05T15:00:00+00:00 Episode link: https://share.transistor.fm/s/a59f25e7 Audio file: https://media.transistor.fm/a59f25e7/b8a7b2ce.mp3 Processing state: not_requested JSON: https://stenobird.com/v1/public/podcasts/north-meets-south-web-podcast-706861/episodes/worktree-structures-workflow-events-and-enum-metadata Duration seconds: 2694 ## Resource In this episode, we discuss using `claude --worktree` to spin up parallel feature work, and the unexpected friction that can arise when your editor doesn’t play nicely with nested worktrees. Jake shares his experience running multiple Claude agents in parallel and problems that surfaced in PhpStorm. Michael explains how he structures worktrees differently, avoiding those issues, and the two compare workflows between PhpStorm and Neovim. Show Links claude --worktree Git worktrees PhpStorm Neovim Tmux LazyGit Using GitHub CLI in workflows archtechx/enums Arbor Laracon US Git Worktree Hub plugin for PhpStorm ## Actions - request_transcript: `POST https://stenobird.com/v1/public/podcasts/north-meets-south-web-podcast-706861/episodes/worktree-structures-workflow-events-and-enum-metadata/transcription-requests` — Idempotently request low-priority transcript generation for this episode. - read_markdown: `GET https://stenobird.com/podcast/north-meets-south-web-podcast-706861/worktree-structures-workflow-events-and-enum-metadata.md` — Read the agent-friendly Markdown representation of this episode resource. A page view does not enqueue transcription. Agents should invoke `request_transcript` explicitly when they need this episode processed. ## Transcript Full transcripts are not published on public pages unless there is a clear rights basis.