Ringlet vs Conductor — CLI orchestrator vs Mac visual orchestrator

Conductor is a Mac app for running parallel AI coding agents — Claude Code and Codex — on git worktrees. It’s polished, native, and a good choice if you’re on macOS and want a visual orchestrator.

Ringlet is a cross-platform CLI orchestrator with an optional web dashboard. It’s a better choice if you want long-lived per-project context, cost tracking, or you work on Linux.

These tools sit at different points on two axes: macOS-only vs cross-platform, and parallel-task vs long-lived-context.

The mental model

Conductor optimises for a specific workflow: a senior developer with a backlog of independent tasks, working on macOS, who wants to dispatch them to parallel agents and review diffs visually. Its mechanic is git worktrees, like Claude Squad — but with a visual dashboard instead of a TUI.

Ringlet optimises for a different workflow: a developer (on any platform) managing multiple long-lived project contexts, each with their own credentials, providers, and accumulated agent memory. The mechanic is HOME isolation per profile; parallelism is intentionally not the headline.

Where the audiences split

Question	Conductor	Ringlet
Platform	macOS only	macOS, Linux (x86_64, aarch64)
Primary interface	Native Mac app	CLI + optional dashboard
Primary unit of work	Parallel task	Long-lived profile
Provider switching per agent	No (agent defaults)	Yes (any agent → any provider)
Cross-agent cost tracking	Per-task	Cross-profile SQLite ledger
Keychain-backed credentials	Inherits env	Keychain / Secret Service / WinCred
Sandboxed exec	Worktree-only	bwrap (Linux) / sandbox-exec (macOS)
Remote PTY sessions	No	Yes, with web UI
Event hooks	No	Yes (pre-tool-use, tool-use, cost-threshold, …)

What Conductor does better than Ringlet

• Visual polish on Mac. The Mac app feels like a native Mac app. Ringlet’s web dashboard is functional; it’s not the same polish.
• Diff-review UI. Conductor’s diff-review experience is purpose-built and good. Ringlet doesn’t have an equivalent.
• Discoverability. Conductor is one app to launch; everything is on screen. Ringlet’s CLI surface is more powerful but takes more learning.

What Ringlet does better than Conductor

• Cross-platform. Linux is first-class. Many engineering teams have at least one Linux dev box; Ringlet works there.
• Cost transparency. ringlet usage aggregates across every agent and every provider. Conductor tracks per-task; cross-task accounting is something you’d build separately.
• Provider switching. Point Claude Code at MiniMax, OpenRouter, or a self-hosted gateway with one TOML stanza. Conductor uses the agent’s default provider.
• Long-lived context. A Conductor task is a git worktree — it ends when the task ends. A Ringlet profile is a long-running context that persists across sessions.
• Remote terminal sessions. Run agents on a server, access the PTY from a browser. Useful for big indexing jobs or for working from an iPad.
• Hooks and audit. Pre-tool-use guards, audit logs, Slack alerts — the building blocks for team-level guardrails.

Using them together

Less obvious than the Ringlet + Claude Squad combo, but workable. Conductor as the visual layer over Claude Code and Codex on macOS; Ringlet for cost tracking and credential isolation when you’re not in Conductor.

Pragmatically, most people pick one or the other. If you’re macOS-only and your workflow really is “parallel tasks, review diffs,” Conductor is excellent and you won’t miss what Ringlet adds. If you’ve ever found yourself wishing you could pin Claude Code to a different provider for one project or you’ve watched a Linux teammate hit “you must be on macOS,” Ringlet is the answer.

What we ended up doing

Internally at Neul Labs we use Ringlet. The CLI fits how we already work, Linux support is non-negotiable for us, and the cost-tracking + provider-switching combo is what we built Ringlet to solve. We respect Conductor a lot — it’s polished software for a real audience — but it’s not our audience.

If you’re picking between them and your primary workflow is “I want to run five Claude Code agents in parallel on git worktrees, on my Mac,” install Conductor. If you’re picking between them and your primary workflow is “I need clean isolation across multiple projects/accounts, on whatever OS I happen to be on,” install Ringlet.

Honest things to know

Conductor is reportedly working on a richer feature set (audit, cost, teams). When that ships, the comparison page will need updating. We’ll keep this honest as their roadmap moves.

Ringlet’s web dashboard is the area we’d most like to invest in visual polish next. If the CLI is the right primitive but the dashboard is what gets your team to adopt it, file an issue — that’s the kind of feedback that moves our priority list.