
One GPU. Many Codex sessions. Less manual juggling.
My most-used local Codex tool. I use it every day to let multiple sessions share one Windows GPU. Jobs queue in the background, run when resources are available, and return results to each session, so I don't have to coordinate them manually.
Codex GPU Queue enables users to run GPU jobs from multiple Codex tasks through a single local Windows queue. It features an automatic broker for eligible work and provides a read-only CLI for inspecting confirmed waiting blockers.
Scored deterministically. Only candidates that fire a story trigger are sent to a model, so this one has no written angle.
Gaps in our data, not findings about the product. Their weight is redistributed across the 5 we did measure.
A source that found nothing is a measurement. A source that has not run is a gap. Neither means the launch lacks the thing.