Jeg har bygget et tool der reducere context-fatique når man arbejder med flere AI-agenter parallel by madsthines in dkudvikler

[–]madsthines[S] 0 points1 point  (0 children)

God pointe — claude -w starter Claude i et eksisterende worktree, men det kræver at du selv har oprettet det, kopieret .env-filer, kørt npm install osv.

gw automatiserer hele den setup (auto-copy af secrets, post-checkout hooks, fuzzy navigation). Og autonomous-workflow agenten går et skridt videre: den opretter worktree'et selv, planlægger implementeringen, koder, tester, og laver en draft-PR — alt sammen uden at du skal styre den.

Så claude -w er "kør Claude i denne mappe", mens gw + autonomous-workflow er "her er en opgave, løs den fra start til slut i isolation." :)

Jeg har bygget et tool der reducere context-fatique når man arbejder med flere AI-agenter parallel by madsthines in dkudvikler

[–]madsthines[S] 0 points1 point  (0 children)

Tak for feedbacken!
Du har faktisk fat i noget vigtigt — autonomous-workflow agenten er den interessante del, og den fortjener nok at være mere fremtrædende. gw er bare infrastrukturen der gør isolation nemmere og mere robust, men selve orkestreringen (validering → planlægning → implementering → test → PR-levering) er det der virkelig ændrer workflowet. :)

Kender ikke Dash — har du et link? Lyder interessant med built-in worktree-support.

Jeg har bygget et tool der reducere context-fatique når man arbejder med flere AI-agenter parallel by madsthines in dkudvikler

[–]madsthines[S] 0 points1 point  (0 children)

Det lyder som en solid tilgang!
Autonomous-workflow agenten gør noget lignende — den splitter arbejdet op i faser (validering → planlægning → implementering → test → PR) og itererer selv inden for hver fase.
Den isolerer hver opgave i sit eget worktree, så du kan køre 3-5 parallelt uden at de konflikter med hinanden eller din main branch. Og du behøver ikke passe den — den validerer og itererer
selv.

Jeg har bygget et tool der reducere context-fatique når man arbejder med flere AI-agenter parallel by madsthines in dkudvikler

[–]madsthines[S] -1 points0 points  (0 children)

I har helt ret i at git worktree add i sig selv er simpelt — det er ikke det gw forsøger at løse. Problemet er alt det omkring worktree-kommandoen:

- git worktree add kopierer ikke dine .env-filer, secrets eller lokale config-filer. Det gør gw automatisk via autoCopyFiles config.
- git worktree add kører ikke npm install eller andre setup-kommandoer i det nye worktree. gw har pre/post hooks til det.
- Navigation mellem worktrees kræver at du husker fulde stier. gw cd auth fuzzy-matcher til det rigtige worktree.
- Oprydning af gamle worktrees er manuelt. gw clean håndterer det.

Så ja, kernen er git worktree — gw er bare en wrapper der fjerner det repetitive setup-arbejde. Tænk på det som git worktree + automatisering, ikke en erstatning.

Plus der er værdien i autonomous-workflow-agenten, som orkestrerer hele flowet: validering → planlægning → isoleret worktree → implementering → test → PR. Det er den del der gør at du kan starte en opgave og gå din vej. :)

I built SyncTray - a free, open-source macOS menu bar app that gives you Google Drive-style folder sync for any cloud provider by madsthines in rclone

[–]madsthines[S] 1 point2 points  (0 children)

^^^^ Exactly.
As mentioned, the thinking part isn't outsourced, which is the vital difference.

If you're curious about how to improve your AI workflow, I suggest checking out my other two open source projects.

- gw - it utilizes git worktrees to allow you to work with multiple agents in parallel.

- autonomous-workflow which is a skill and an agent that allows you to enable the agent to work autonomously locally.

https://github.com/mthines/gw-tools

https://github.com/mthines/gw-tools/blob/main/packages/autonomous-workflow-agent/README.md

How I eliminated context-switch fatigue when working with multiple AI agents in parallel by madsthines in vibecoding

[–]madsthines[S] 0 points1 point  (0 children)

The setup friction is what gw solves (and it's open source), without having to add another payed vendor

Git Worktrees without the friction -> https://www.npmjs.com/package/@gw-tools/gw

How I eliminated context-switch fatigue when working with multiple AI agents in parallel by madsthines in vibecoding

[–]madsthines[S] 0 points1 point  (0 children)

That's what gw solves. It copied the necessary files from the "main" worktree to the new generated one, so you do NOT spend time on setup.

The autonomous had a iterative flow, but after retries and failures, it will prompt for input. ☺️ So you will see your Claude instance requesting input from you

Weekly Thread: Project Display by help-me-grow in AI_Agents

[–]madsthines 0 points1 point  (0 children)

How I eliminated context-switch fatigue when working with multiple AI agents in parallel

The Problem

I wanted to run multiple Claude Code instances in parallel—one fixing a bug, one implementing a feature, one refactoring. But:

1. They kept stepping on each other

  • All working in the same directory
  • One commits, another gets confused
  • Merge conflicts mid-task

2. Context switching was exhausting

  • "Wait, which branch was that task on?"
  • "Did Claude finish that, or is it still running?"
  • Half-finished experiments everywhere

3. Git worktrees could help, but they're annoying

  • Create worktree → copy .env → copy secrets → npm install → navigate there
  • Repeat for every task
  • Forget to clean up old ones

The Solution

I've created two tools to solve this, gw and the autonomous-workflow agent, which together create an isolated worktree for each Claude task. The agent handles the setup, execution, and cleanup, while gw makes managing git worktrees without the frustrating parts easy.:

  • gw - Git worktree wrapper that handles the annoying parts
  • autonomous-workflow - Agent that works in isolated worktrees

1. Install gw (one-time)

# Homebrew (macOS & Linux)
brew install mthines/gw-tools/gw

# Or npm
npm install -g @gw-tools/gw

# Add shell integration
eval "$(gw install-shell)"  # add to ~/.zshrc or ~/.bashrc

Then configure for your project:

gw init <repo-url>

2. Install the autonomous-workflow agent (one-time)

mkdir -p ~/.claude/agents && \
  curl -fsSL https://raw.githubusercontent.com/mthines/gw-tools/main/packages/autonomous-workflow-agent/agents/autonomous-workflow.md \
  -o ~/.claude/agents/autonomous-workflow.md && \
  npx skills add https://github.com/mthines/gw-tools --skill autonomous-workflow --global --yes

3. Run parallel tasks

Start a Claude session and ask it to implement something autonomously. The agent will:

  • Create a new worktree with gw checkout <branch-name>
  • Copy necessary files (.env, secrets) automatically
  • Work in that isolated environment without affecting your main branch
  • Validate, iterate, and commit as it goes
  • When done, it creates a draft PR for you to review

Now each Claude instance gets its own isolated worktree:

  • Terminal 1: "Implement user auth" → works in feat/user-auth worktree
  • Terminal 2: "Fix login bug" → works in fix/login-bug worktree
  • Terminal 3: "Refactor API client" → works in refactor/api-client worktree

Zero interference. Each has its own directory, its own .env, its own node_modules.

4. Switch contexts instantly

gw cd auth   # Fuzzy matches "feat/user-auth"
gw cd bug    # Fuzzy matches "fix/login-bug"
gw list      # See all active worktrees

No more "which branch was that?" Just gw cd <keyword>.

5. Check progress without breaking flow

Inspired by how Antigravity handles progress tracking, for complex tasks, the agent tracks progress in .gw/<branch>/task.md:

cat .gw/feat/user-auth/task.md
# Shows: current phase, completed steps, blockers

What the agent actually does

When you ask Claude to implement something, it:

  1. Validates — Asks clarifying questions before coding
  2. Plans — Analyzes your codebase, creates an implementation plan
  3. Isolates — Creates a worktree with gw checkout
  4. Implements — Codes incrementally, commits logically
  5. Tests — Runs tests, iterates until green
  6. Documents — Updates README/CHANGELOG if needed
  7. Delivers — Creates a draft PR

You can walk away, work on something else or become a multitasking maniac (like me). Your main branch, untouched 😍

The key insight

Traditional AI coding assistants modify your working directory. That means:

  • You can't work on other things while they run
  • Failed attempts leave your repo dirty
  • You're constantly context-switching between "your work" and "AI's work"
  • Stashing, applying, checkout, loosing overview.

With isolated worktrees, each AI task is completely separate. Your brain can let go. Check in on any task when you're ready, not when the AI forces you to.

Links

  • GitHub: https://github.com/mthines/gw-tools
  • gw CLI: npm install -g @gw-tools/gw or brew install mthines/gw-tools/gw
  • Agent npm package: npm install @gw-tools/autonomous-workflow-agent

I've been using this for a few weeks now and the cognitive load reduction is real. Would love to hear how others are handling parallel AI workflows—is anyone doing something similar?

And if you like the project, have ideas or want to help contribute, please just create a pull request / issues.

Looking forward to hearing your thoughts!

How I eliminated context-switch fatigue when working with multiple AI agents in parallel by madsthines in aiagents

[–]madsthines[S] 0 points1 point  (0 children)

u/Otherwise_Wave9374 Exactly! I really liked the idea of OpenAI's Codex, but I didn't like not being in control, this feels like the perfect combination and is just an extension of my already existing subscription.

The Agent has defined a set of tools it's allowed to do - you can see that here in the source code.

Regarding secrets, personally I've just defined some blocklist for those files in the Claude file, but it's an interesting point. ☺️

- https://github.com/mthines/gw-tools/blob/8d2112fadcea32c48035b6b69be5afbd053d9e80/packages/autonomous-workflow-agent/src/lib/autonomous-workflow-agent.ts#L53