Crystal alternatives: where to go after the February 2026 deprecation

Published August 11, 2026 · by the AQ team

Crystal, the open-source desktop app for running multiple Claude Code and Codex sessions in parallel git worktrees, was deprecated in February 2026. Its final release, v0.3.5, shipped on February 26, 2026, and the repository now states plainly that Crystal "will not be updated in the future" and recommends migrating to Nimbalyst, the successor product from the same developer, Stravu. The app still installs and still works, but it will receive no bug fixes or security patches. The practical question is what to replace it with, and the answer depends on which part of Crystal you actually used: the visual desktop workflow (Nimbalyst or Conductor), the worktree mechanics (Claude Squad or plain git), or the ability to run several agent sessions at once, which every option below covers.

What Crystal was, and why it earned its users

Crystal was an MIT-licensed Electron app that solved one problem well: running several AI coding sessions side by side without them trampling each other. You typed a prompt, Crystal created a git worktree with its own branch, and a Claude Code or Codex session went to work inside it. You could open three sessions on the same task and compare approaches, or spread sessions across unrelated tasks. Around that core it added the conveniences that made the workflow livable: a built-in diff viewer to review each session's changes, run scripts to test a worktree without leaving the app, one-click squash-and-rebase back to your main branch, session persistence so conversations could be resumed, and desktop notifications when a session needed input.

That feature list matters because it is the checklist for evaluating replacements. A good Crystal alternative needs parallel sessions, worktree isolation per session, a way to review diffs, and a way to get finished work back onto main.

What the deprecation actually means for you

Deprecated is not deleted. The GitHub repository remains online, the MIT license still permits use and forks, and an installed copy of Crystal keeps working today. But three clocks are ticking. First, agent CLIs move fast: Claude Code and Codex ship breaking changes and new capabilities monthly, and Crystal will never adapt to them. Second, unpatched Electron apps accumulate security debt, which is a real consideration for a tool that runs shell commands on your machine. Third, the ecosystem around Crystal (docs, issues, community fixes) has moved to its successor. Treat Crystal as safe to keep using this quarter and unwise to depend on this year.

Nimbalyst: the official successor

The path of least resistance is the one Stravu built. Nimbalyst is Crystal's successor, and as of August 2026 it is an open-source, MIT-licensed desktop app that is free to use, with builds for macOS, Windows, and Linux plus mobile companion apps for iOS and Android. It runs Claude Code and Codex, with OpenCode and Copilot support in alpha. The Crystal ideas carry over: sessions run in parallel, and any session can opt into its own git worktree with one click. Around them, Nimbalyst is a broader product than Crystal was: sessions are organized on a kanban board by phase, changes are reviewed in a red and green visual diff, and there are visual editors for markdown, mockups, diagrams, and spreadsheets, plus a built-in terminal.

If Crystal fit you well, Nimbalyst is the obvious first candidate: same developer, same core workflow, actively maintained, and the deprecation notice points there for a reason. The main thing to evaluate is whether you want the larger surface area; Crystal was a focused tool, and Nimbalyst is a full visual workspace.

Conductor: the polished Mac option

Conductor, by Melty Labs, is a free Mac app that runs parallel Claude Code and Codex agents, each in an isolated git worktree with its own branch, diff view, and integrated terminal. It is probably the most polished desktop take on the Crystal workflow, and you bring your own Claude or OpenAI subscription. The hard limit: as of August 2026 it is Mac-only, with Windows on a waitlist, so Windows and Linux developers are out. We keep a detailed and honest breakdown at Conductor alternatives and a direct AQ vs Conductor comparison.

Claude Squad: the terminal-native option

If Crystal's Electron shell was the part you tolerated rather than loved, Claude Squad inverts the trade. It is an open-source (AGPL-3.0) terminal UI that manages multiple agents (Claude Code, Codex, and other terminal agents) by combining the two primitives directly: a tmux session per agent for persistence and a git worktree per task for isolation, with a TUI to switch between them and review changes. No GUI, no diff panels beyond what the TUI offers, but also no desktop app to maintain, and it works anywhere tmux does.

Vibe Kanban: capable, with a caveat

Vibe Kanban offers a web-based kanban board where each task runs an agent in an ephemeral worktree, and it supports a wide agent roster. The caveat is stewardship: Bloop, the company behind it, shut down on April 10, 2026, and the project continues as community-maintained open source under Apache 2.0. That is a workable basis for adopting a tool, but it is the same "who maintains this next year" question that Crystal users are asking right now, so weigh it deliberately. Our Vibe Kanban alternatives page covers the landscape in detail.

No tool at all: worktrees and tmux by hand

Everything Crystal automated is scriptable. A git worktree per task keeps agents isolated; a named tmux session per worktree keeps them running and lets you switch between them; plain git diff and rebase close the loop. The git worktrees for AI coding agents guide covers the commands and the cleanup habits, and running multiple Claude Code sessions in parallel walks the whole workflow. This route has zero dependencies and zero deprecation risk. What you give up is everything visual: no session dashboard, no diff viewer, no notifications when an agent stalls.

The options at a glance

Where AQ fits

AQ is the multiplayer coding harness where engineering teams run AI coding agents like Claude Code and Codex together: shared live terminals, a code editor, and app previews, in your own cloud. Against the Crystal checklist, AQ covers the same mechanics: every workspace gets its own isolated git worktree on a branch named ai/{id}-{slug} with dependencies installed automatically, agents run as the real CLIs (Claude Code, Codex, Cursor Agent, Kimi, Grok, or plain shells), rebasing onto main is one click, and agents commit, push, and open PRs with each user's own GitHub auth. Each engineer signs into the CLIs with their own Claude or OpenAI account, so there is no markup on model usage.

The structural difference is where sessions live and who can see them. Crystal, Nimbalyst, and Conductor run agents on one person's machine, visible to one person. AQ runs them in persistent tmux sessions on your team's VM, streamed live to the browser: sessions survive a closed laptop, resume from any device, and a teammate can open the same workspace and watch the same live session. Typing into someone else's terminal is delegated, not open: the owner approves a control request in one click and keeps their own input. That single-player ceiling on desktop tools is not hypothetical: a July 2026 LeadDev analysis of 25,264 agent-generated pull requests across 2,361 popular GitHub repositories found that in 79 percent of agentic PRs the same developer both reviewed and modified the agent's contribution, and only about one in eight workflows involved multiple humans. Desktop tools make that isolation the default; AQ makes the shared session the default.

Honestly: if you are one developer on one machine and Crystal was enough, Nimbalyst or Conductor will be enough too, and they are free. AQ earns its place when the pain is team-shaped: sessions that need to outlive a laptop, work that teammates should be able to see and steer, previews to share outside the team, and Linear issues that should become workspaces (label an issue ai-task and the workspace appears, with status syncing both ways). The Free plan is a personal sandbox with nothing to install and no time limit, so you can compare it against any tool on this page before involving your team.