Nethür
Sign in
macOS coming soon

Blog · November 9, 2026

Conductor alternatives for Linux and Windows

Conductor proved that parallel agents need isolated workspaces. Here is what to use on Linux and Windows now that the Mac-only app and its cloud are winding down.

Nethür running on desktop platforms with parallel agent workspaces

Conductor is a Mac app, so it is not an option if your team works on Linux or Windows. Use a cross-platform workspace instead: Nethür runs Claude Code, Codex and other CLI agents in isolated git worktrees on macOS, Windows and Linux, on your own machine or a shared server, with team collaboration built in.

Conductor did the hard product work of making parallel coding agents feel normal. One task per workspace, a clean diff, a review step before anything lands. If you work on a Mac, it is still a polished way to run Claude Code.

It is also Mac-only, and its cloud service is winding down. That leaves two groups of people looking for an alternative: developers on Linux or Windows who could never use it, and Mac users who do not want their workflow tied to a product that is changing shape.

What Conductor gets right

  • A focused Mac app built around isolated workspaces for each agent.
  • Checkpoints, pull request and CI pages, and in-diff editing in one flow.
  • Support for Claude Code, Codex and Cursor rather than a single model vendor.
  • A simple mental model: one task, one workspace, review the diff, ship it.

Any alternative should preserve that model. If it makes you manage branches and terminal tabs by hand, it is a step backwards, even if it runs on the right operating system.

Why people are looking elsewhere now

The platform limit is the obvious one. A team with a Mac laptop and a Windows desktop cannot standardize on a Mac-only tool, and a Linux CI or dev box cannot run it at all. Buying a Mac for every developer is not a serious answer for most teams.

The second reason is the product transition. According to our comparison, Conductor Cloud is going read-only on November 13 and shutting down on November 20, 2026. The local Mac app keeps working and gets fixes until early 2027. If your workflow depends on the cloud features, you need a plan before that date, not after it.

What a cross-platform alternative needs

  • Real desktop support for macOS, Windows and Linux, not a browser wrapper that assumes a Mac server.
  • A git worktree (or folder workspace) per task, with a branch and a clean diff.
  • Support for the agents you actually use: Claude Code, Codex, OpenCode, Gemini CLI and others.
  • A review flow: diff against the start-from ref, annotations, commit, push and pull request.
  • A team story that does not require a shared API key or a shared login.
  • A choice of execution host: your laptop, a teammate’s machine, a VPS or an SSH target.
  • Git provider coverage beyond GitHub when your team uses GitLab, Jira or Linear.

The realistic options on Linux and Windows

ToolPlatformsParallel work modelTeamNotes
ConductormacOS onlyIsolated workspaces per agentCloud winding downLocal app supported into early 2027
NethürmacOS, Windows, Linux; browser and phone clientsGit worktree or folder workspace per taskShared projects, chat, mentions, takeovers, own subscriptionsFree solo; team $3.99/seat/month
PaseomacOS desktop, web, iOS, AndroidWorktrees with 33+ agentsHub add-on; not a full team workspaceOpen source; Hub Pro $15/seat/month
CodecastmacOS desktop, web, iOSParallel agent sessionsTeam chat, calls, docs, tasksSelf-host on your AWS; team $20/seat/month (waitlist)
Manual git + Claude CodeAny OSYou create and track worktreesNoneFree, maximum control, most bookkeeping

The table is intentionally short. There are more tools in the category, but these are the ones with a clear answer to “what do I run on Linux or Windows tomorrow?” If you only need one developer on one machine, manual worktrees are a legitimate answer; the cost is everything around them.

Nethür on Linux and Windows

Nethür ships desktop builds for macOS, Windows and Linux. Linux packages include an AppImage plus .deb and .rpm; Windows has a standard installer. The Linux build targets glibc 2.31 and newer, which covers Ubuntu 20.04 and most current distributions. macOS 12 and Windows 10/11 are supported.

The desktop app is a full host, not a thin client. It can run the workspace server locally, so a Windows laptop or a Linux workstation gets the same worktrees, terminals, diffs and agent sessions as a Mac. For a team, the server can move to a VPS or an always-on machine and everyone connects from the desktop app or the browser.

Agent support is not limited to Claude Code. Nethür launches Claude Code, Codex, OpenCode, Gemini CLI, Cursor, GitHub Copilot and other terminal agents in the worktree, each with its own session. You bring the subscriptions; Nethür does not resell model access.

Moving from Conductor without losing work

  1. Inventory your active work before you change anything. Note the branch for each Conductor workspace and whether it has uncommitted changes. Commit or stash what you need to keep.
  2. Install Nethür on the machine where you want the work to run. For a single developer, the desktop app with a local server is the shortest path.
  3. Add the repository. Nethür can work with a normal checkout; it does not need to adopt Conductor’s directory layout.
  4. Create a worktree per active task. Pick the branch or commit you noted in step 1 as the start-from ref, or create from the base ref if the Conductor branch was only an experiment.
  5. Launch Claude Code in the new worktree. The session starts in that directory with that branch, so it behaves like the isolated workspace you came from.
  6. Review the diff, commit, push and open the pull request from Nethür. Then delete the worktrees you no longer need and keep the branches that still matter.
  7. Invite the team once your own flow works. Put the server on a shared host, assign projects and have each person connect their own Claude account.

You do not need to migrate old experiments. If a Conductor workspace was only there to compare a prompt, delete it. Migrate the branches that have work you intend to ship, and let the rest go.

The mixed-OS team is the real test

A cross-platform app is only useful if the whole team can meet in the same workspace. Nethür’s team server is the piece Conductor never had: one place where a Mac user, a Windows user and a Linux user see the same projects, the same worktrees and the same sessions. Team chat, @mentions and takeovers work across those clients, and each person keeps their own subscription.

That is also the main architectural difference. Conductor was a local Mac app with a cloud layer bolted on. Nethür treats the execution host as the center and the desktop, browser and phone as interchangeable clients. Moving from your laptop to a VPS does not move the work; it just changes where the agents run.

What you give up

Conductor’s Mac polish is real, and a cross-platform tool has to work on three operating systems instead of one. If you are a solo Mac developer and the local app still does everything you need, there is no urgency to switch before its support window ends. If you need Windows or Linux, a shared team workspace, or a path that does not depend on one vendor’s cloud, the trade-off points the other way.

Cost comparison

Nethür is free for solo use. Team workspaces are $3.99 per seat per month, or $35.99 per seat per year ($2.99 a month). Model usage stays on your own Claude, Codex or other provider subscription. There is no cloud-minute billing and no token markup.

Paseo’s app is open source and free, with a Hub Pro plan around $15 per seat per month. Codecast lists a team plan around $20 per seat per month on a waitlist and runs on your own AWS. Manual worktrees cost nothing but time. Price is only one column; the cost of a tool that does not run on half the team’s machines is usually higher.

Try the migration on one branch

Pick one active Conductor workspace, create the same branch in Nethür, and run the next agent task there. If the diff, review and push flow feels normal, move the rest. If it does not, you have lost an hour rather than a sprint.

The point of an alternative is not to replace Conductor feature for feature. It is to keep the part that worked — one task, one isolated workspace, one reviewable diff — on the machines your team actually uses.

Put the guide to work.

Download Nethür and run your first parallel agent in minutes, or set up a team workspace on a machine you already own.