Glimmervoid

Mission control for coding agents: run and supervise any terminal coding agent in parallel git worktrees from one local browser dashboard.

The dashboard on a laptop. A session waiting on a question goes orange and moves to the top of the rail, so you always know which one needs you.

Cost / License

Free
Open Source (MIT)

Origin

United States

Since

Updated

Updated Nov 2026

Platforms

Mac
Windows
Linux

An agent mid-turn in its own git worktree, writing a migration plan. The box at the top of the rail counts finished sessions, and Alt+J jumps to the next one.

Focus view. Every session sits in the rail on the left, grouped by project, and the selected one shows its live terminal. This one finished a rename and committed it.

Glimmervoid alternatives

0likes

82alternatives

0articles

Properties

Lightweight
Support for Themes
Local-First

Features

No registration required
Extensible by Plugins/Extensions
Support for scripting
Command line interface
Dark Mode
Dashboard

Glimmervoid information

Developed by
John C. Waters
Licensing
Open Source (MIT) and Free product.
Written in
TypeScript
Alternatives
82 alternatives listed
Badge
Get an embeddable badge for Glimmervoid
Supported Languages
- English

AlternativeTo Category

AI Tools & Services

GitHub repository

5 Stars
2 Forks
7 Open Issues
Updated Nov 6, 2026

View on GitHub

Popular alternatives

View all

Glimmervoid was added to AlternativeTo by John-Waters on Nov 6, 2026 and this page was last updated Nov 6, 2026.

No comments or reviews, maybe you want to be first?

AppStores & Other Links

What is Glimmervoid?

Glimmervoid runs your coding agents in parallel and tells you which one needs you. Claude Code, Codex, Kimi Code, Gemini CLI, Copilot CLI, Qwen Code and Grok are built in, and any other agent that runs in a terminal can be added in the config.

It's an orchestrator, not a harness. Each agent runs unmodified as a real process in a real terminal on your own machine, with your own login, subscription, skills, hooks and settings. No cloud service and no account.

Every session in a git repo gets its own worktree, so agents never step on your checkout or each other. Status comes from the agents' own hooks (the screen is never scraped), so it knows exactly which session is working, which is waiting on you, and which is done. The one that needs you comes to the front.