FREE TOOL 001 / NOTHING UPLOADED

Parallel Coding Agent Worktree Planner

Give each coding agent a branch, worktree, port, cache namespace, test database, and handoff before the terminal grid turns into a small accidental government.

Built by · Free · Runs locally in your browser

01add authenticationfeat/add-authentication:3101
02write authentication testsfeat/write-authentication-tests:3102
03review accessibilityfeat/review-accessibility:3103

1 / Worktree commands

Set-Location 'C:\dev\my-app'
git fetch origin --prune
git rev-parse origin/main

# Agent 1: add authentication
git worktree add '.worktrees/add-authentication' -b feat/add-authentication origin/main
# Agent 2: write authentication tests
git worktree add '.worktrees/write-authentication-tests' -b feat/write-authentication-tests origin/main
# Agent 3: review accessibility
git worktree add '.worktrees/review-accessibility' -b feat/review-accessibility origin/main

git worktree list

2 / Runtime assignments

# Agent 1: add authentication
AGENT_SLOT=01
APP_PORT=3101
CACHE_NAMESPACE=agent-01-add-authentication
TEST_DATABASE=agent_01_add_authentication
PROCESS_OWNER=feat/add-authentication

# Agent 2: write authentication tests
AGENT_SLOT=02
APP_PORT=3102
CACHE_NAMESPACE=agent-02-write-authentication-tests
TEST_DATABASE=agent_02_write_authentication_tests
PROCESS_OWNER=feat/write-authentication-tests

# Agent 3: review accessibility
AGENT_SLOT=03
APP_PORT=3103
CACHE_NAMESPACE=agent-03-review-accessibility
TEST_DATABASE=agent_03_review_accessibility
PROCESS_OWNER=feat/review-accessibility

3 / Handoff template

TASK HANDOFF
Outcome:
Worktree:
Branch:
Commit:
Dirty files:
Checks run:
Owned processes stopped:
Known risks:
Next action:

What the planner generates

The tool creates one outcome-named Git branch and worktree command for every editing agent. It also assigns sequential ports, distinct cache and database namespaces, and a handoff template that forces the final agent state into something another person can actually inspect.

Inputs never leave the page. There is no account, backend, telemetry call, or generated configuration file to download and forget about. Copy the plan, review the commands, and run them from the repository you named.

What the planner cannot isolate for you

A generated port does not stop an old process from already owning it. A database name does not create that database. A worktree does not prevent two logically coupled tasks from editing the same invariant. Check the machine and the task boundaries before you launch anything expensive.

The Git worktree guide covers safe setup and cleanup. The orchestration architecture covers task state, observability, and integration. The field guide includes the full failure taxonomy.

A good agent task can fail independently

“Improve the backend” is not a useful planner input. “Reject expired refresh tokens” is. Use one line per outcome that has a clear owner and focused evidence. If two outcomes must change the same hot file or schema, sequence them or give the shared boundary to one agent.

Start with two or three editing agents. Add concurrency only after the current set stays observable and integrates cleanly. Eight agents are supported because some tasks really are independent, not because eight is a personality test you need to pass.