gitwtfhub

wtf is iudex?

rengwu/iudex — explained in plain English

Analysis updated 2026-05-18

14TypeScriptAudience · developerComplexity · 3/5Setup · moderate

TL;DR

A desktop app that runs several AI coding agents in parallel git worktrees, each ticket reviewed by a QA agent before a human approves the merge.

Mindmap

mindmap
  root((iudex))
    What it does
      Runs agents in parallel
      Isolated git worktrees
      Human review gate
    Tech stack
      TypeScript
      Go
      Tauri
      Git
    Use cases
      Run multiple agents at once
      Review diffs before merge
      Track tickets through a pipeline
      Drive work from CLI or GUI
    Audience
      Engineering teams
      Solo developers

Code map

Detail Auto

An interactive map of this repo's files and how they connect — its source is parsed live in your browser. Click Visualize to build it.

filefunction / class

Why would anyone build with this?

REASON 1

Run multiple AI coding agents on separate tickets at the same time without their work colliding.

REASON 2

Review each agent's diff through a QA step before it can reach your main branch.

REASON 3

Track work as tickets moving through a pipeline from queued to done.

REASON 4

Drive the same agent workflow from either a desktop GUI or the command line.

What's in the stack?

TypeScriptGoTauritmuxGit

How it stacks up

rengwu/iudex0xbebis/hyperpayalfredxw/nova
Stars141414
LanguageTypeScriptTypeScriptTypeScript
Setup difficultymoderatehardmoderate
Complexity3/55/53/5
Audiencedeveloperdeveloperwriter

Figures from each repo's GitHub metadata at analysis time.

How do you spin it up?

Difficulty · moderate Time to first run · 30min

Requires tmux 3.2 or newer for the desktop app, and at least one configured command line coding agent.

No license information was found in the explanation provided.

Wtf does this do

Iudex is a desktop app for running several AI coding agents at once, treated like a small engineering team instead of one assistant in a terminal. You describe work as tickets, the app spins up a separate git worktree and branch for each one, an agent implements it there, a QA agent reviews the diff, and a human makes the final call on whether it merges to main. The problem it addresses is that running multiple agents in parallel by hand gets messy fast: branches overlap, it becomes unclear what has been reviewed, and you stop trusting your main branch. Iudex adds a structured pipeline around that without becoming another agent itself. Everything it tracks lives as plain git history plus an append only event log on disk, with no background service and no database, so deleting the app still leaves your git history intact. The interface is built around seven views: a dashboard showing the pipeline and a live event feed, a tabbed terminal for interacting with running agent sessions, a tickets table, a live view into each agent's activity, a per worktree diff inspector, a review screen that is the human approval gate, and a settings page for configuring agent commands and prompts. Automation features like auto QA or auto retire are opt in and only apply for the current session, so nothing spends effort on its own by default. It works with any command line coding agent you configure, including Claude Code or Aider, and is agent agnostic by design. A ticket moves through defined states from queued to active to pending QA to pending human review to done, and if QA rejects it too many times it lands in a failed state waiting for a retry. Everything can also be driven directly from the command line using commands like iudex init, iudex queue, iudex activate, and iudex human-qa approve, since the desktop app and terminal are two interfaces to the same underlying engine. The desktop app ships for macOS on Apple Silicon and Linux x86_64, bundles its own command line tool, and needs tmux 3.2 or newer for the terminal and agent views. A standalone command line build only needs Go 1.22 or newer and git.

Yoink these prompts

Prompt 1
Explain how iudex keeps parallel coding agents from colliding using git worktrees.
Prompt 2
Walk me through running iudex init and queuing my first ticket from the command line.
Prompt 3
What is the difference between iudex's QA approval step and the human approval step?
Prompt 4
How does iudex handle a ticket that gets rejected too many times by QA?

Frequently asked questions

wtf is iudex?

A desktop app that runs several AI coding agents in parallel git worktrees, each ticket reviewed by a QA agent before a human approves the merge.

What language is iudex written in?

Mainly TypeScript. The stack also includes TypeScript, Go, Tauri.

What license does iudex use?

No license information was found in the explanation provided.

How hard is iudex to set up?

Setup difficulty is rated moderate, with roughly 30min to a first successful run.

Who is iudex for?

Mainly developer.

View the repo → Decode another repo

This repo across BitVibe Labs

Don't trust strangers blindly. Verify against the repo.