FREE · OPEN SOURCE · MACOS

Run agents in parallel.Fold the work back cleanly.

Treefold is a macOS app for managing parallel agent development. Give each task its own Git worktree, run agents and shells together, track work, review changes, and deliver the results.

Get Treefold View source

The first public alpha is available. Install with Homebrew or download the DMG.

Separate development directoriesTasks and Sessions in one placeFrom starting work to delivering it

01Split the work02Run in parallel03Review & deliver

TreefoldWorkflow illustration · Sample data

Workspace / auth-flow

Complete the sign-in feature

Todo02

Validate auth edge casesCreate a Fork from a Todo ↗

Forkvalidationfork/validation

Own branch · Own worktree

Add API integration tests→ api-tests

Fork02 · Running

CodexRunning

Fork / validation

Validate auth edge cases

src/auth/session.ts +24 −6

Claude CodeRunning

Fork / api-tests

Add API integration tests

tests/auth/api.test.ts +48

Sessions in the same Fork share a checkout

Review changesvalidation

src/auth/session.ts

− return session.user+ validateSession(session)+ return session.user

✓ Tests passed · Awaiting review

ForkvalidationWorkspaceauth-flow

Merge into parent Workspace ↗

Archive when finished; keep the worktree and work records

Turn a Todo into a Fork with its own branch and worktree.

Run an agent in each Fork, with code changes isolated from one another.

Review changes and test results, then merge the Fork into its parent Workspace.

MULTIPLE AI AGENTS

Work with the agents you know.

Run Codex, Claude Code, Pi, or OpenCode in a Workspace or Fork, or open a Shell for commands. Install and configure your chosen agent’s CLI first.

Available now

Codex
Claude Code
Pi
OpenCode

01 / THE OPERATING MODEL

A place for every piece of work.

Building a sign-in feature? Put the frontend and backend repositories in one Project, create a Workspace for the feature, and use Forks for parallel validation and testing.

Treefold product architecture: a Project organizes repositories; a Workspace owns a feature, with isolated Forks for subtasks. Agent and Shell Sessions execute the work. Review Fork changes and merge into the parent Workspace, then deliver and archive the feature. — View full product architecture ↗

Isolation belongs to Workspaces and Forks. Multiple Sessions in the same Workspace or Fork can share a checkout.

From a Todo to delivered code.

Follow a sign-in task from its description through execution to the resulting code.

Add a Todo

Add “Validate auth edge cases” to the auth-flow Workspace.

Create a Fork

Create the validation Fork from the Todo and start an agent on the subtask.

Review the result

Inspect the diff, run tests, and check the changes against the task.

Deliver to the Workspace

Integrate the Fork into its parent and continue bringing the feature together.

02 / KEEP WORK MOVING

New Sessions. Work carries on.

Code, tasks, and delivery targets belong to a Workspace or Fork. Open multiple Sessions within that work, using your preferred agents or shells.

Keep the work

When a Session ends, the Workspace’s code and Todos remain ready for the next session.

Resume Codex conversations

Resume saved Codex conversations and continue where you left off.

Give agents the current context

Use the treefold CLI to inspect the Workspace, repositories, and Todos; add, edit, remove, or block a Todo. Codex also receives work context automatically at launch.

CURRENT WORK AND TASKS

Project: atlas
Workspace: auth-flow
Fork: validation

$ treefold current --json
$ treefold todo list --json

Use the treefold CLI in managed Sessions. The companion Skill helps agents understand work ownership and operation boundaries.

api · TTY

RUNNING

01$ amux run --name api -- cargo run
02Compiling service...
03Listening on 127.0.0.1:3001
04GET /api/health 200
05Agent Session ended · process remains active

03 / AMUX / MANAGED PROCESSES

Managed processes. Shared across sessions.

amux manages development services and long-running processes. You and your agent can read the same logs at the same time, then keep inspecting output and debugging across sessions.

✓Processes keep running independently of Agent Sessions
✓Humans and agents share live logs simultaneously
✓Read logs, interact, restart, or stop across sessions

Whether processes survive App exit follows the amux preference.

04 / REVIEW AND DELIVER

Review the changes. Choose how to deliver.

Inspect diffs and Git History, sync branches, and handle conflicts in the context of your work. Choose one delivery strategy for the Workspace or Fork, then check and execute it across repositories.

Review code and history

Inspect file changes, staged state, and commit diffs. Commit or tidy up history when needed.

Sync branches and resolve conflicts

Update code with rebase or merge. When conflicts arise, start a helper Session, review the resolution, and continue.

Continue interrupted delivery

Delivery progress is saved. After an interruption or conflict, recheck Git state and continue the remaining steps.

ChangesGit History

feature/auth-flow

Validate session ownershipMina · 09:42 · 4 files +86 −14

8f3ab21

Add delivery preflight checksLeo · Yesterday · 2 files +31 −5

62bd908

Refine Todo assignmentMina · Monday · 6 files +104 −28

1ca77ef

DELIVERY

One strategy, checked across repositories

Merge into target

Merge a Workspace into its local target or a Fork into its parent. Deliver progress and keep working, or finish and archive.

02OPTIONAL AT FINISH

Squash merge

When finishing and archiving, combine the result into one target commit while preserving the source branch and history.

Push feature branch

Push a Workspace branch for your team’s review and CI. You can also push intermediate results and keep working.

Preserve without delivery

Archive without merging or pushing. Keep the checkout to reopen later; explicit deletion handles resource cleanup.

Intermediate delivery keeps work active. Finishing archives it while retaining branches and worktrees. Remote PR review and merging happen on your Git hosting platform.

Two uses of Squash: rewriting history and delivering work

GIT HISTORY

Squash selected history

Select consecutive, unpublished commits and combine them into one. Treefold previews the rewrite, blocks unsafe ranges, and offers Undo while the result remains recoverable.

DELIVERY

Squash merge into target

Finish a Workspace into its local target, or a Fork into its parent, as one commit. The source branch and its original commits remain unchanged.

Neither operation pushes or force-pushes. Delivery checks both source and target before it starts.

05 / FITS THE REPOSITORY YOU HAVE

Bring related repositories into the same work.

Single repository

Give each feature its own Workspace so parallel tasks do not compete for the same checkout.

Multiple repositories

Build a feature across frontend and backend repositories. Organize their checkouts and track delivery in one Workspace.

Monorepo and multiple directories

Choose the directory where a Session starts while keeping repository-level Git ownership.

Context Directory

Mark specifications, notes, and other reference material as read-only context to consult while developing.

FREE AND OPEN SOURCE

Bring parallel work to a clear finish.

Free and open source for Apple Silicon Macs. Project state and orchestration data stay on your Mac, using standard Git branches and worktrees. Agent network access depends on your services and configuration.

Get Treefold Star on GitHub

If you find Treefold useful, consider giving it a star on GitHub to support the project.