Tools
Every tool in the log.
Filed by the tension it addresses.
Projects that illustrate an approach, filed under their first tension. Inclusion isn't an endorsement; each page links to the source so you can judge the claims.
104 tools
Plan: Scheduling the work
The plan tension and its approaches →- agent-orchestratorTakes tickets with declared dependencies, sorts them into parallel waves, runs an agent per task in its own worktree and opens one PR per task.
- agent-taskgraph-protocolA protocol for Claude Code and Codex agent teams: spec freeze, durable roles, isolated workers, independent review and evidence-backed delivery.
- AIWorkHubA local control plane in VS Code and MCP that coordinates several model workers through dependency-aware task graphs, durable project memory and evidence-based review.
- BeadsTrack tasks and dependencies as multiple agents work on a codebase.
- code-system-graphMaps APIs, events, schemas, packages, databases and ownership across repositories so agents can check the impact of a change before making it.
- First TreeOpen-source orchestration that puts several coding agents on one backlog, runs them in parallel and lands everything as a reviewed pull request.
- graph (gwaghmar)Plans agent work as a dependency graph of small nodes that are cached, validated and retried one by one.
- multi-agent-orchestrator-skillAn agent skill that splits a large task into a reviewed plan, then supervises worker agents in isolated worktrees with scoped prompts, validation and restarts.
- OmORoutes work to specialised agents as background tasks with dependency graphs and per-provider concurrency caps; an experimental team mode adds a mailbox and file-locked task claims.
- Open OrchestratorExploring orchestration of autonomous software work.
- opencode-madAn OpenCode plugin that splits a task into parallel subtasks, each in its own worktree, with planner, reviewer and file-ownership roles.
- OrdewellRun tasks separately, then bring successful results into an integration branch.
- OrkestraA deterministic DAG scheduler and integration kernel for agent-directed work.
- PactContract-first decomposition so agents can build behind typed interfaces.
- PlanuA spec-driven MCP server that locks the spec, plan and task list, then lets agents change only the files a manifest names.
- red-queenA deterministic state machine that moves Jira or GitHub tickets through spec, code, review, test and human gates, dispatching Claude Code workers between phases.
- RepoHelixA cross-repository contract graph that lets agents reason about how a change to an interface affects other repositories.
- SpecGraphAn approach to graph-shaped specifications and their relationships.
Isolate: Sharing the world
The isolate tension and its approaches →- agent-slotsDeterministic per-agent namespaces for worktrees, ports, queues, and data.
- agents (joaovictor3g)Gives every terminal coding agent its own branch, worktree, tmux window and session so several can work on one repo.
- agxA desktop and CLI control plane that keeps parallel coding agents in persistent sessions with worktrees and tmux, with optional Discord control.
- Blackbox CLIA coding CLI that plans changes before applying them, sends up to four agents in parallel and runs headless in CI.
- BranchBoxBranch runtime environments, networks, databases, and ports—not just code.
- CodeSandbox SDKStarts and controls CodeSandbox sandboxes programmatically, for running AI agents and their code.
- ConTreeA sandbox API with VM isolation whose execution state can be branched like Git, rolled back and explored in parallel.
- DoltGit-like branching, diffing, and merging for SQL database state.
- E2BCloud sandboxes that give every agent its own isolated machine to run code, browse and use tools, with pause and fork.
- forkdA Firecracker microVM runtime that forks many sandboxes from a warm parent snapshot copy-on-write, and can branch a live VM.
- isolaLocal runtime and database environments isolated per worktree.
- lakeFSBranching and merging over large-scale data, useful in independent sandboxes.
- OakVersion control and storage for agents: mounts large repos without a full clone, branches per task and snapshots quickly.
- PandaStack sandboxes: branch and exploreForks a sandbox copy-on-write to try N approaches in parallel real execution and keep the winner.
- Parallel CodeA workspace that gives each agent its own worktree so you can review the diffs, merge the good ones and drop the rest.
- RunloopSandboxes and evaluation infrastructure for running coding agents at enterprise scale.
- SafeAgentDBDatabase-per-agent and database-per-PR isolation for coding work.
- SuperlogicalA multiplexer for local development, coding agents, background jobs and remote sessions.
- WarrenRuns coding agents like infrastructure on compute you control: isolation, lifecycle, spend limits, recovery and Git delivery.
- wooiA macOS app that gives each agent task its own worktree, branch and session, and stacks tasks when one builds on another.
Coordinate: Coordinating intent
The coordinate tension and its approaches →- agent-messengerAn MCP server for agent-to-agent messages and threaded conversations, backed by Beads.
- agent-parleyRuns several coding agents on one repository, each in its own worktree, and records who owns what: claims, reservations, handoffs and refusals.
- AgentlocksExpiring file and working-tree locks for concurrent coding agents.
- BeadBoardA live dashboard, task reservations and typed agent-to-agent mail, built on Beads.
- claim-planeExecution control for concurrent coding agents: write authority before edits, semantic conflict detection, critical-path scheduling and integration, without agents negotiating with each other.
- Claude Code agent teamsA lead session spawns teammates that message each other and claim tasks from a shared, dependency-aware list; claiming uses file locking, file edits do not.
- DeltaA shared workspace where teammates and agents build and review code in threads that keep conversation and changes together.
- Gas CityAn SDK from the Gas Town team for building multi-agent coding workflows from formulas, sessions and a Beads data plane.
- Gas TownA Mayor agent coordinates swarms of workers in git worktrees, and a Refinery agent merges their changes to main one at a time.
- GoosetownCoordinates flocks of goose agents with research-first delegation, a broadcast wall and cross-model review.
- LimenTime-bounded, advisory write leases over shared mutable state, with a witnessed audit trail of writes, served over MCP.
- LoomAnticipates conflicts while agents work, with ownership zones and memory.
- MCP Agent MailAgents get identities and threaded inboxes, take TTL leases on file globs, and an optional pre-commit hook blocks commits that touch files another agent has reserved.
- Meowkit team configA MeowKit skill that sets up a parallel agent team: worktree structure, a file ownership map and a task queue.
- overstory-accountingSpawns worker agents in worktrees, coordinates them through a SQLite mail system and merges their work back with tiered conflict resolution.
- PolywaveA protocol for parallel agents that assigns disjoint file ownership and agrees interface contracts before implementation starts.
- RufloSpawns swarms of agents coordinated through MCP tools, with shared memory, work claims and hive-mind consensus.
- SWAPAgents claim individual functions and classes on a coordination server before editing, and get semantic diffs when peers change symbols they depend on.
- Swarm ToolsA coordinator splits a task into parallel subtasks; workers take exclusive file-path reservations and coordinate through an embedded event store with mail, durable locks and checkpoints.
- symlockSymbol-level locks and symbol-aware merging to reduce collisions.
- witAgents declare intents and lock symbols rather than files; agreed interface contracts are enforced by a pre-commit hook.
Integrate: The integration queue
The integrate tension and its approaches →- AgenticFlictA research dataset of merge conflicts in pull requests opened by AI coding agents on GitHub.
- Axonel SentinelRuns coding agents in isolated worktrees and integrates their work in a transactional step that rejects a stale target branch.
- clashDetects likely merge conflicts across Git worktrees early, while parallel agents are still working.
- Cursor OriginCursor's Git forge built for agents.
- DeployBotA GitHub merge queue driven by agents: they prepare and review PRs, the human says "deploy", and it merges independent work and pauses after failures.
- GitButlerA different way to manage parallel branches and code changes.
- GitHub Stacked PRsNative dependency-aware stacked pull requests and rebases.
- GitLab Merge TrainsTest predicted merged states such as A, A+B, and A+B+C.
- GraphiteStacked pull requests for sequencing and shipping dependent changes.
- Jujutsu (jj)A Git-compatible version control system with first-class conflicts, automatic rebasing and an operation log you can undo.
- mergetrainA local merge queue for parallel agents: branches are queued, merged in order, gated by tests on the combined result, and pushed only after approval.
- Mergify Parallel QueueDependency-aware parallel merges and speculative verification.
- Orchestrator.incA planner hands focused tasks to workers in their own branch and worktree, then tracks PRs, CI, reviews and merge conflicts and returns failures to the owning agent.
- OverstoryWorkers in isolated git worktrees exchange SQLite mail, and a FIFO merge queue resolves conflicts in tiers.
- quietclashRuns the code to catch behavioural conflicts between parallel agents' branches that merge cleanly and pass tests but break at runtime.
- restackRebases a chain of stacked PRs onto their current base branches after one of them merges.
- semantic_mergeReconcile code intent using symbols and ASTs, not just text.
- staxA stacked-branch workflow for Git with lanes for parallel agents and automatic resolution of rebase conflicts.
Verify: Proving it's safe
The verify tension and its approaches →- Adversarial ReviewIndependent coding models review changes and critique one another.
- AdversarialDebateIndependent agents debate reviews and preserve dissent or consensus.
- agent-fanoutRuns a coding agent N times in parallel git worktrees, drops attempts that fail the tests, ranks the rest and merges the winner behind a human gate.
- agent-specCompiles intent from PRDs and issues into verifiable task contracts, then checks the implementation against them BDD-style.
- Cursor /best-of-nRuns the same task across several models at once, each in its own worktree, and leaves picking or combining the results to you.
- FlaggerProgressive delivery and automated rollout analysis for Kubernetes.
- Kayenta AI Canary JudgeEvaluate control versus experiment versions before promotion.
- labruno-agentSpins up several sandboxes that each attempt the same task, runs them in parallel and uses an LLM judge to pick the best one.
- omp-best-ofRuns several candidate agents on the same task in copy-on-write workspaces and applies only the patch a verifier ranks best.
- QuetrexHooks for Claude Code that keep each gate shut until a real artifact proves it: an exit code, a review, a passing check.
- saplingsAdds tree search to an agent so it can look ahead, compare tool-use paths and backtrack.
Remember: Remembering why
The remember tension and its approaches →- agent-memory-engineA local MCP server that gives coding agents persistent project memory: architecture, constraints, past incidents and source context retrieved before complex tasks.
- agentdiffRecords which AI agent wrote which line, signs each attribution and stores it in the Git history.
- agenticowCopy-on-write branching for vector memory, so many agents can fork a shared memory base cheaply and query their own edits on top.
- CASCoding-agent system exploring continuity and traceability of work.
- cgxTurns a Git repository and its history into a queryable knowledge graph, served to agents over MCP.
- codecontextInline annotations for constraints and the reasons behind code, enforced by linting and freshness checks so later agents must read them.
- CodeGraphXA local code graph engine and MCP server that answers structural questions such as blast radius, dependency cycles and whether a symbol exists.
- Context Delta EngineBuilds inspectable, replayable context packets for coding agents, local-first.
- Engram MCPMemory infrastructure for context that needs to survive sessions.
- EntireKeep context around agent-generated work and coding sessions.
- GrapePackages repository context so agents stop rereading the same files, rules, decisions and failures across chats and tools.
- groundcrewRetrieval-augmented "chat with your code" over a repository, for maintenance, documentation and onboarding.
- MemforksBranch-aware shared memory for agents, with merge policies and recorded provenance for resolutions.
- qarinahCited project memory shared across coding agents: decisions, code relationships, tool outcomes and worktree history, handed to each new session.
- RookeryAn approach to preserving and organizing agent-work context.
- TreeWorkA tree-guided workflow skill that keeps a long-running agent's plan and decisions visible across sessions and handoffs.