Many agents.
One direction.

See the work come together.
Before you commit.

Give every agent its own Git worktree. Let coord compose their changes into one live view — right where you already build.

Explore the workflow CLI first. GUI included.

GIT-NATIVELOCAL-FIRSTYOUR COMMIT

THE COMPOSER

checkout / workspace● LOCAL

main / checkout.tsunstaged preview

01const checkout = {

02 label: 'Pay securely',interface

03 gateway: 'connected',api

04 analytics: true,metrics

05};

Interactive model. Toggle a lane. Break something. See what lands.

YOUR AGENTS.
YOUR WAY OF WORKING.

Claude Code Codex Gemini Your terminal

01 / THE WORKFLOW

Parallel work.
Without the blind spots.

More agents should mean more progress.
Not more time piecing the project back together.

A real space for every agent.

Each lane is an ordinary Git branch and worktree. Separate files, dependencies and build artifacts. Use the tools you already know.

REAL WORKTREES. NO NEW GIT DIALECT.

The whole thing, as it happens.

The daemon watches your lanes and composes their changes. Your editor, dev server and git diff see the combined result in your main folder.

ONE VIEW. ALWAYS THE BIGGER PICTURE.

You make the final call.

The preview stays unstaged. No automatic merge commit. Inspect it, run your tests, and commit the combined work when it is ready.

git add . && git commit

02 / BUILT FOR THE COLLISIONS

Good work
gets through.
Conflicts wait.

When a lane cannot be integrated, coord holds back that entire lane. Healthy lanes can keep contributing. No half-integrated feature quietly sneaking into your preview.

Try a collision above

INTEGRATION CHECKPOINT03 LANES → 01 PREVIEW

feat/interfaceReady to compose

INCLUDED

feat/apiConflict in checkout.ts

BLOCKED

feat/metricsStill moving forward

INCLUDED

A clean composition.Two lanes land. The conflicting lane waits for an explicit retry.

Illustration of a blocked lane, not a running repository.

01Snapshot

Capture the lane changes.

02Compose

Build in a temporary worktree.

03Check

Validate main, index and preview.

04Publish

Apply the combined, unstaged diff.

Manual main-worktree edits, staged changes or a branch switch stop publication. Keep ongoing work in your lanes.

03 / YOU HAVE THE CONTROLS

A command line.
A bigger picture.

Drive it yourself. Put an agent at the controls. Or open the desktop app. It all talks to the same local daemon.

Made for a coordinating agent.JSON status, explicit sync, lane ordering and failure exit codes. A practical surface for your own orchestration.
A way back when you need it.Lane snapshots retain the latest ten distinct captured states. Inspect and restore them from the CLI or GUI.
AI on your terms.Manual by default. Opt into conflict resolution with an Anthropic key or a supported local CLI.

coord / control room

# In a clean target repository
$ coord init
$ coord daemon &

# Give each worker its own lane
$ coord lane add feat/interface --create
$ coord lane add feat/api --create

# Watch the work come together
$ coord status --watch

# Inspect the shared state
$ coord status --json

# Set the integration order
$ coord lane reorder feat/api feat/interface

# Retry explicitly, inspect the outcome
$ coord sync --json
# Exit 1 if a lane fails.
# Check stderr for command errors.

LOCAL DAEMONCLI ↔ shared protocol ↔ desktop

Examples assume the CLI is installed. You launch the worker agents; coord manages their lanes and composition.

SAME ENGINE. ANOTHER PERSPECTIVE.

Less guessing.
More seeing.

The Tauri desktop app puts lanes, diffs, backup history and conflict choices in one place. See what was integrated, what was adjusted, and what is waiting.

coordINTERFACE ILLUSTRATION

IntegrationLAST COMPLETED CYCLE

feat/interfaceIntegrated

feat/api◇ 1 file adjustedIntegrated

feat/metricsIntegrated

Merged on mainCombined changes · ready to inspect

+ 42 − 8

THE DETAILS MATTER.

Good questions.

Does coord commit or move my branches?

Normal merge cycles leave the base branch HEAD unchanged and publish unstaged changes. You review and commit the combined result yourself. coord creates branches only when you explicitly request a new lane with --create.

Does it launch and manage my agents?

Not yet. You or an external coordinator start the workers in their lane worktrees. coord provides the merge engine, lane controls and machine-readable status. A built-in task queue and agent-to-agent messaging are planned.

Does my code leave my machine?

The merge engine works locally. AI resolution is optional and manual by default. When you explicitly request an AI merge, the base and conflicting file contents go to your selected provider or CLI. Worktrees isolate files, not processes or access to shared Git history.

What is supported today?

The CLI targets macOS and Linux with Node.js 20+ and Git 2.40+. The desktop app uses Tauri. The 0.7.0 candidate has CLI integration and package-installation tests, plus a macOS app build/start check. Complete native GUI and live-provider acceptance are still pending. Native Windows is not supported.

Can I install it from npm already?

Not yet. The package @smart-byte/coord is prepared but unpublished. The repository is currently private while we review it for an open-source release. The examples on this page show the intended workflow once you have an installed candidate.

BUILD IN PARALLEL. MOVE TOGETHER.

A little coordination.
A lot more possibility.

Public release in preparation.
We’re reviewing the source before opening the repository.

Meet the makers 0.7.0 DEVELOPER PREVIEW npm COMING LATER

Many agents.One direction.

Parallel work.Without the blind spots.