DEDUPED Hot AI repos, turned into use cases Get 5 a day

How to give each coding task its own Git worktree and branch with Diri

Run parallel agent tasks in separate worktrees so their changes never collide.

Who it is forA developer splitting one codebase into several features or fixes that agents should work on at the same time.

The problemParallel agents editing the same checkout overwrite each other's files and make branches hard to untangle.

The outcomeEach task runs in its own worktree and branch, so you can review and merge each one independently.

What you need first

  • macOS 15 or newer on Apple silicon or Intel, or x86_64 Ubuntu 22.04 or 24.04 for the Linux beta
  • Terminal coding agent CLIs and accounts already installed on your machine, such as Claude Code, Codex, Cursor, or Gemini
  • A Git repository to work in, since each agent can get its own Git worktree and branch
  • For remote runs: an SSH host you control

Steps

  1. Install the app with brew install --cask cristicretu/diri/diri.
  2. Open Diri and create one agent session per task.
  3. Enable a separate Git worktree and branch for each session.
  4. Let the agents work, then check each session's branch for its own changes.
  5. Review and merge the branches one at a time.

Prompt for your agent

In the diri repo at github.com/cristicretu/diri, confirm that each agent session for <task-list> has its own Git worktree and branch. Output a table of session, worktree path, and branch name, and verify that no two sessions share a branch.

Caveat. The README says each agent can get a worktree but does not say how to enable it, so check the Diri docs for the setting before relying on it.

Share: X LinkedIn Hacker News Email Copy link

Disclaimer

Deduped lists open-source repositories that belong to other people. We do not own, maintain, audit, or vouch for any of them, and a repo appearing here is not an endorsement or a safety check. The use cases, steps, and prompts are written by AI and may be incomplete, outdated, or just wrong. Where a use case is marked "Seen in the wild", we link to public posts where someone described something similar, but we have not verified those posts and the use case itself is still our AI's own write-up. Use all of this at your own risk. Only run code, commands, or agents on systems and accounts you are authorized to use, and read the code and every command before you run it, especially anything that touches credentials, files, or the network. Nothing here is professional, security, legal, or financial advice. All trademarks and project names belong to their respective owners, and their use here does not imply affiliation. Content is provided as is, without warranties of any kind. Found a mistake, a safety problem, or something you want removed? Email [email protected] and we will look at it promptly. Full disclaimer page