# git worktree

Published articles for git worktree.

This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles.

## I Ran 13 Claude Code Sessions at Once. Here's What the Data Revealed

DevFeed: [I Ran 13 Claude Code Sessions at Once. Here's What the Data Revealed](<https://devfeed.tech/articles/i-ran-13-claude-code-sessions-at-once-here-s-what-the-data-revealed-128452.md>)

Original publisher: [Read original article](<https://hackernoon.com/i-ran-13-claude-code-sessions-at-once-heres-what-the-data-revealed?source=rss>)

Author: Myeongseok Kang

Published: 2026-11-11T07:22:36Z

Content type: news

Language: en

Sources: [HackerNoon](<https://devfeed.tech/sources/hackernoon.md>)

Topics: [Claude Code](<https://devfeed.tech/topics/claude-code.md>), [AI-assisted coding](<https://devfeed.tech/topics/ai-assisted-coding.md>), [hooks](<https://devfeed.tech/topics/hooks.md>), [code security](<https://devfeed.tech/topics/code-security.md>), [versioning](<https://devfeed.tech/topics/versioning.md>), [Test-driven development](<https://devfeed.tech/topics/tdd.md>)

Tags: [ai](<https://devfeed.tech/tags/ai.md>), [ai-agent](<https://devfeed.tech/tags/ai-agent.md>), [ai-agent-isolation](<https://devfeed.tech/tags/ai-agent-isolation.md>), [ai-agents](<https://devfeed.tech/tags/ai-agents.md>), [ai-coding-agents](<https://devfeed.tech/tags/ai-coding-agents.md>), [app](<https://devfeed.tech/tags/app.md>), [block](<https://devfeed.tech/tags/block.md>), [checkout](<https://devfeed.tech/tags/checkout.md>), [claude-code](<https://devfeed.tech/tags/claude-code.md>), [claude-projects](<https://devfeed.tech/tags/claude-projects.md>), [command](<https://devfeed.tech/tags/command.md>), [commands](<https://devfeed.tech/tags/commands.md>), [commit](<https://devfeed.tech/tags/commit.md>), [developer-tools](<https://devfeed.tech/tags/developer-tools.md>), [git](<https://devfeed.tech/tags/git.md>), [git-worktree](<https://devfeed.tech/tags/git-worktree.md>), [git-worktree-add](<https://devfeed.tech/tags/git-worktree-add.md>), [git-worktree-conflicts](<https://devfeed.tech/tags/git-worktree-conflicts.md>), [github](<https://devfeed.tech/tags/github.md>), [guard](<https://devfeed.tech/tags/guard.md>), [open-source](<https://devfeed.tech/tags/open-source.md>), [rules](<https://devfeed.tech/tags/rules.md>), [sessions](<https://devfeed.tech/tags/sessions.md>), [shell](<https://devfeed.tech/tags/shell.md>), [transcripts](<https://devfeed.tech/tags/transcripts.md>)

### AI overview

Replaying two weeks of Claude Code history (204 sessions, 101,167 shell commands) against shared-machine guard rules flagged 507 commands that could interfere with another session. Twenty-five were `git add -A` commands in a tree where another session was active within ten minutes. The rules target broad staging, killing processes by name, port conflicts, disk scans, and removing an in-use worktree. As Claude Code hooks, they inspect matching commands before execution, block risky cases, and give the model a safer next step; the guards fail open if they cannot parse or inspect context. The scan is read-only and can be run on transcripts with claude-bulkhead. Its count is incomplete: historical transcripts lack port and memory state, so those checks were excluded, and a rule match does not establish that damage occurred. The command parser also cannot catch every script, alias, or encoded command, so the guards are not a sandbox.

### Source excerpt

Replaying two weeks of Claude Code transcripts through guard rules: 507 of 101,167 shell commands would have hurt another live session.

## Git worktrees: How to work on multiple branches at once

DevFeed: [Git worktrees: How to work on multiple branches at once](<https://devfeed.tech/articles/git-worktrees-how-to-work-on-multiple-branches-at-once-98648.md>)

Original publisher: [Read original article](<https://circleci.com/blog/git-worktree/>)

Author: Jacob Schmitt

Published: 2026-10-23T16:00:00Z

Content type: tutorial

Language: en

Sources: [CircleCI](<https://devfeed.tech/sources/the-circleci-blog-feed-circleci.md>)

Topics: [Git](<https://devfeed.tech/topics/git.md>), [Parallelism](<https://devfeed.tech/topics/parallelism.md>), [CI/CD](<https://devfeed.tech/topics/cicd.md>), [Pull Request](<https://devfeed.tech/topics/pull-request.md>), [developer-productivity](<https://devfeed.tech/topics/developer-productivity.md>)

Tags: [2026](<https://devfeed.tech/tags/2026.md>), [agent](<https://devfeed.tech/tags/agent.md>), [agents](<https://devfeed.tech/tags/agents.md>), [ai](<https://devfeed.tech/tags/ai.md>), [ai-development](<https://devfeed.tech/tags/ai-development.md>), [branch](<https://devfeed.tech/tags/branch.md>), [circleci](<https://devfeed.tech/tags/circleci.md>), [codex](<https://devfeed.tech/tags/codex.md>), [coding](<https://devfeed.tech/tags/coding.md>), [coding-agent](<https://devfeed.tech/tags/coding-agent.md>), [coding-agents](<https://devfeed.tech/tags/coding-agents.md>), [engineering-productivity](<https://devfeed.tech/tags/engineering-productivity.md>), [git](<https://devfeed.tech/tags/git.md>), [git-remove-worktree](<https://devfeed.tech/tags/git-remove-worktree.md>), [git-worktree](<https://devfeed.tech/tags/git-worktree.md>), [git-worktree-add](<https://devfeed.tech/tags/git-worktree-add.md>), [git-worktree-tutorial](<https://devfeed.tech/tags/git-worktree-tutorial.md>), [git-worktree-vs-branch](<https://devfeed.tech/tags/git-worktree-vs-branch.md>), [git-worktrees](<https://devfeed.tech/tags/git-worktrees.md>), [how-to](<https://devfeed.tech/tags/how-to.md>), [how-to-use-git-worktree](<https://devfeed.tech/tags/how-to-use-git-worktree.md>), [parallel](<https://devfeed.tech/tags/parallel.md>), [what-is-a-git-worktree](<https://devfeed.tech/tags/what-is-a-git-worktree.md>)

### AI overview

Git worktrees provide separate working directories and staging areas for multiple branches while sharing one repository's history, avoiding repeated branch switching or duplicate clones. Create, inspect, and remove them with `git worktree add`, `list`, and `remove`; branches can only be checked out in one worktree at a time. For coding agents, assign independent tasks to separate worktrees, review committed and uncommitted changes, confirm checks, then merge and clean up. Tool workflows differ: Claude Code and Codex support `.worktreeinclude` for ignored files, Cursor can run setup commands from `.cursor/worktrees.json`; Codex offers "Create branch here," and Cursor has `/apply-worktree`. Worktrees do not isolate shared ports, databases, services, credentials, or overlapping code, so separate environments may be needed and merge conflicts remain possible. Keep tasks small, limit work in progress, and merge regularly. CircleCI's CLI and MCP tools provide CI logs and failures to agents; its CLI `--failure-report` gathers failures across jobs.

### Source excerpt

Learn how git worktrees let you work on several branches at once, how to set each one up, and how to keep parallel work from piling up unmerged.

## The Importance of Planning Before Coding: A Workflow Solution

DevFeed: [The Importance of Planning Before Coding: A Workflow Solution](<https://devfeed.tech/articles/the-importance-of-planning-before-coding-a-workflow-solution-55871.md>)

Original publisher: [Read original article](<https://swamp-club.com/feed/p/595db501-7d6a-46de-b69f-80cbd7c7306b/go>)

Author: adron

Published: 2026-08-24T18:38:20Z

Content type: opinion

Language: en

Sources: [Swamp Club Feed](<https://devfeed.tech/sources/swamp-club-feed.md>)

Topics: [agentic-coding](<https://devfeed.tech/topics/agentic-coding.md>), [human-in-the-loop UX](<https://devfeed.tech/topics/human-in-the-loop-ux.md>), [qualitygates](<https://devfeed.tech/topics/qualitygates.md>), [Application Development](<https://devfeed.tech/topics/application-development.md>), [Claude Code](<https://devfeed.tech/topics/claude-code.md>)

Tags: [agentic](<https://devfeed.tech/tags/agentic.md>), [agents](<https://devfeed.tech/tags/agents.md>), [ai](<https://devfeed.tech/tags/ai.md>), [blast-radius](<https://devfeed.tech/tags/blast-radius.md>), [branch](<https://devfeed.tech/tags/branch.md>), [changes](<https://devfeed.tech/tags/changes.md>), [code](<https://devfeed.tech/tags/code.md>), [coding](<https://devfeed.tech/tags/coding.md>), [coding-agent](<https://devfeed.tech/tags/coding-agent.md>), [docs](<https://devfeed.tech/tags/docs.md>), [e2e](<https://devfeed.tech/tags/e2e.md>), [gate](<https://devfeed.tech/tags/gate.md>), [gen-ai](<https://devfeed.tech/tags/gen-ai.md>), [git](<https://devfeed.tech/tags/git.md>), [git-worktree](<https://devfeed.tech/tags/git-worktree.md>), [idor](<https://devfeed.tech/tags/idor.md>), [implementation](<https://devfeed.tech/tags/implementation.md>), [llms](<https://devfeed.tech/tags/llms.md>), [multiple-agents](<https://devfeed.tech/tags/multiple-agents.md>), [planning](<https://devfeed.tech/tags/planning.md>), [programming](<https://devfeed.tech/tags/programming.md>), [unknown-code-ramblings](<https://devfeed.tech/tags/unknown-code-ramblings.md>), [workflow](<https://devfeed.tech/tags/workflow.md>)

### AI overview

The article recommends gating coding agents behind an ask-plan-confirm workflow so they clarify ambiguity and get approval before editing. Agents first surface open questions, then propose a concise plan naming files and routes in scope, the approach, risks, tests, and any additive migration; implementation starts only after an explicit yes. Approval covers only that plan, so scope changes require re-planning and renewed approval. Questions may be skipped for genuinely unambiguous, low-risk requests. Agent-specific prompts adapt the gate to migrations, tests, e2e, docs, and blog work; read-only security and UX reviews clarify scope, then use the full gate if asked to make fixes. The author pairs this with isolated git worktrees. The excerpt argues the small upfront pause helps prevent unwanted diffs and scope creep.

### Source excerpt

Learn how to prevent coding mishaps by implementing a structured planning process before AI agents make changes to your codebase.

## GitHub Desktop 3.6: Worktrees and deeper Copilot integration

DevFeed: [GitHub Desktop 3.6: Worktrees and deeper Copilot integration](<https://devfeed.tech/articles/github-desktop-3-6-worktrees-and-deeper-copilot-integration-71661.md>)

Original publisher: [Read original article](<https://github.blog/changelog/2026-06-26-github-desktop-3-6-worktrees-and-deeper-copilot-integration>)

Author: Allison

Published: 2026-06-26T10:32:58Z

Content type: release

Language: en

Sources: [GitHub Changelog](<https://devfeed.tech/sources/github-changelog.md>)

Topics: [GitHub Desktop](<https://devfeed.tech/topics/github-desktop.md>), [GitHub Copilot](<https://devfeed.tech/topics/github-copilot.md>), [GitHub](<https://devfeed.tech/topics/github.md>)

Tags: [agents-md](<https://devfeed.tech/tags/agents-md.md>), [ai](<https://devfeed.tech/tags/ai.md>), [ai-assisted](<https://devfeed.tech/tags/ai-assisted.md>), [authoring](<https://devfeed.tech/tags/authoring.md>), [coding-agents](<https://devfeed.tech/tags/coding-agents.md>), [commit](<https://devfeed.tech/tags/commit.md>), [conflict-resolution](<https://devfeed.tech/tags/conflict-resolution.md>), [copilot](<https://devfeed.tech/tags/copilot.md>), [desktop](<https://devfeed.tech/tags/desktop.md>), [git](<https://devfeed.tech/tags/git.md>), [git-worktree](<https://devfeed.tech/tags/git-worktree.md>), [github](<https://devfeed.tech/tags/github.md>), [github-copilot](<https://devfeed.tech/tags/github-copilot.md>), [github-desktop](<https://devfeed.tech/tags/github-desktop.md>), [merge](<https://devfeed.tech/tags/merge.md>), [worktrees](<https://devfeed.tech/tags/worktrees.md>)

### AI overview

GitHub Desktop 3.6 adds worktrees for working across branches without repeatedly stashing, switching branches, or cloning, alongside Copilot-assisted commit authoring and merge conflict resolution. Generated commit messages can use repository guidance from `.github/copilot-instructions.md` and `AGENTS.md` and follow commit metadata rules. For conflicts, Desktop explains changes and suggests a resolution that users can review, accept, or edit. Copilot features include a model picker for models available through GitHub and support for connecting a third-party provider or local model with a bring your own key. Version 3.6.0 is available for macOS and Windows; Copilot features require GitHub Copilot access.

### Source excerpt

GitHub Desktop 3.6 brings more of your day-to-day Git flow into one place with GitHub Copilot now powering commit authoring and merge conflict resolution, plus new Git worktree support. The...

## Five Stacks Before Lunch: The Parallel Coding Playbook for Pulumi

DevFeed: [Five Stacks Before Lunch: The Parallel Coding Playbook for Pulumi](<https://devfeed.tech/articles/five-stacks-before-lunch-the-parallel-coding-playbook-for-pulumi-19018.md>)

Original publisher: [Read original article](<https://www.pulumi.com/blog/parallel-coding-playbook-for-pulumi/>)

Author: Engin Diri

Published: 2026-06-02T00:00:00Z

Content type: article

Language: en

Sources: [Pulumi](<https://devfeed.tech/sources/pulumi.md>)

Topics: [AI-assisted coding](<https://devfeed.tech/topics/ai-assisted-coding.md>), [pulumi](<https://devfeed.tech/topics/pulumi.md>), [Pull Request](<https://devfeed.tech/topics/pull-request.md>), [Code review](<https://devfeed.tech/topics/code-review.md>), [GitHub Copilot](<https://devfeed.tech/topics/github-copilot.md>), [Linear](<https://devfeed.tech/topics/linear.md>)

Tags: [acceptance](<https://devfeed.tech/tags/acceptance.md>), [ai](<https://devfeed.tech/tags/ai.md>), [ai-agents](<https://devfeed.tech/tags/ai-agents.md>), [ai-coding-agents](<https://devfeed.tech/tags/ai-coding-agents.md>), [automation](<https://devfeed.tech/tags/automation.md>), [best-practices](<https://devfeed.tech/tags/best-practices.md>), [build](<https://devfeed.tech/tags/build.md>), [coding](<https://devfeed.tech/tags/coding.md>), [concurrent](<https://devfeed.tech/tags/concurrent.md>), [git-worktree](<https://devfeed.tech/tags/git-worktree.md>), [git-worktrees](<https://devfeed.tech/tags/git-worktrees.md>), [implementation](<https://devfeed.tech/tags/implementation.md>), [infrastructure](<https://devfeed.tech/tags/infrastructure.md>), [infrastructure-as-code](<https://devfeed.tech/tags/infrastructure-as-code.md>), [issue](<https://devfeed.tech/tags/issue.md>), [parallel](<https://devfeed.tech/tags/parallel.md>), [plan](<https://devfeed.tech/tags/plan.md>), [platform-engineering](<https://devfeed.tech/tags/platform-engineering.md>), [pull-request](<https://devfeed.tech/tags/pull-request.md>), [pulumi](<https://devfeed.tech/tags/pulumi.md>), [pulumi-neo](<https://devfeed.tech/tags/pulumi-neo.md>), [review](<https://devfeed.tech/tags/review.md>), [self-healing](<https://devfeed.tech/tags/self-healing.md>), [spec](<https://devfeed.tech/tags/spec.md>)

### AI overview

The playbook argues that parallel AI coding depends more on isolation and workflow plumbing than on prompting. It proposes five patterns: make a GitHub issue with acceptance criteria the implementation spec; use a plan/build/validate loop that produces a readable plan, a diff, and a check against the spec; give each agent its own git worktree and branch; have a fresh-session agent review the result without seeing the writer's conversation; and fix recurring issues by updating the system that allowed them. This excerpt frames the patterns as aimed at application code and raises, but does not answer, how they change for infrastructure work.

### Source excerpt

AI coding has two shapes right now. One agent in a loop, sequential work, you babysitting the chat window. Call that 2x. Most teams live here. Five agents in worktrees, parallel work, fresh-context review on every change. Call that 10x. The trick: 2x is mostly prompting, 10x is mostly plumbing. The parallel coding playbook is a five-pattern setup for running multiple AI coding agents at the same time without them stepping on each other: an issue used as the spec, a plan/build/validate loop, parallel git worktrees, fresh-session review, and a self-healing layer. The whole thing targets application code. The interesting question, and the one I keep ending up at, is what changes when the five agents are touching infrastructure. 2x is prompting, 10x is plumbing 2x is one human, one agent, one repo, one branch. The agent writes, you review, you tell it to try again, it tries again. The bottleneck is your attention. Whatever the agent's raw throughput, your reading speed sets the ceiling. 10x moves you out of the per-change loop and into the issue loop. You write five issues with sharp acceptance criteria, send each one to its own agent in its own worktree, and let them plan, build, and validate end-to-end. You read five PRs at lunch instead of pair-programming on one all morning. Concurrent isolation does the work. And isolation is mostly an infrastructure problem. The five pillars The five pillars, in one sentence each. Issue is the spec. The GitHub issue carries the acceptance criteria. The pull request is the artifact that gets validated. Input and output of every implementation are versioned, scoped, and reviewable on their own. Plan, build, validate. Three stages, three artifacts. A markdown plan you can read in thirty seconds. A build that produces a diff. A validate step that checks the diff against the spec. Parallel worktrees. Each agent runs in its own git worktree so concurrent changes never trample each other. One repo, five working trees, five branches. Fres