gitwtfhub

wtf is l3-simulator?

czarandy/l3-simulator — explained in plain English

Analysis updated 2026-05-18

0TypeScriptAudience · developerComplexity · 3/5Setup · moderate

TL;DR

A command line tool that dispatches AI coding agents to work on your labeled GitHub issues and manages their pull requests for you.

Mindmap

mindmap
  root((L3 Simulator))
    What it does
      Dispatches AI coding agents
      Works labeled GitHub issues
      Opens and babysits PRs
    Tech stack
      TypeScript
      Node.js
      GitHub CLI
    Use cases
      Auto-fix failing PRs
      Plan then code workflow
      Cross-repo prerequisites
    Audience
      Developers
      Repo maintainers
    Safety
      Never merges code
      No git push for agents
      Human review required

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

Label a GitHub issue as ready and have an AI coding agent open a pull request for it automatically.

REASON 2

Let an agent fix its own pull request when CI fails or a reviewer leaves comments.

REASON 3

Run a terminal dashboard to watch multiple in-progress AI coding tasks at once.

REASON 4

Require an approved plan before an agent starts writing code on a task.

What's in the stack?

TypeScriptNode.jsGitHub CLI

How it stacks up

czarandy/l3-simulator0xkinno/astraea0xkinno/halcyon
Stars000
LanguageTypeScriptTypeScriptTypeScript
Setup difficultymoderatehardhard
Complexity3/54/54/5
Audiencedeveloperdeveloperdeveloper

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

How do you spin it up?

Difficulty · moderate Time to first run · 30min

Requires Node 22+, an authenticated gh CLI, and a Claude Code or Codex CLI installed.

The README does not state a license.

Wtf does this do

L3 Simulator is a tool that manages AI coding agents for you on top of GitHub issues. Instead of you manually asking an AI assistant to work on a task, you label a GitHub issue as ready and the tool claims it, dispatches an AI coding agent such as Claude Code or Codex into an isolated copy of your repository, and has it write code and open a pull request. From there it also watches over that pull request, reacting to failing checks, new review comments, or merge conflicts by sending the agent back in to fix things. GitHub labels are the whole system's memory. Labels like ready, in progress, blocked, and in review describe exactly where each issue stands, so if the tool crashes or restarts it can figure out the current state again just by reading labels and pull requests. You can watch and interact with everything either through a terminal dashboard or directly through the normal GitHub issues page. Importantly, the tool never merges anything itself. Merging and final code review stay entirely your responsibility. The agents are blocked from running git push or gh commands that would merge code, so they can open as many pull requests as they like, but shipping the result is always a human decision. The workflow supports optional planning steps, where an agent proposes a plan and waits for your approval before writing any code, and it can even handle situations where one repository's task turns out to depend on work in another repository, automatically filing the follow up issue there. It runs as a command line tool built with Node.js version 22 or newer, and needs the GitHub CLI and at least one of Claude Code or Codex installed to actually do the coding work.

Yoink these prompts

Prompt 1
Help me install l3-simulator and run init inside my repository.
Prompt 2
Explain how the ready and in-progress labels drive the l3-simulator workflow.
Prompt 3
Show me how to configure l3-simulator to use Claude Code for planning and Codex for fixes.
Prompt 4
Walk me through approving a plan an agent posted on a GitHub issue.
Prompt 5
Explain how l3-simulator prevents agents from merging their own pull requests.

Frequently asked questions

wtf is l3-simulator?

A command line tool that dispatches AI coding agents to work on your labeled GitHub issues and manages their pull requests for you.

What language is l3-simulator written in?

Mainly TypeScript. The stack also includes TypeScript, Node.js, GitHub CLI.

What license does l3-simulator use?

The README does not state a license.

How hard is l3-simulator to set up?

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

Who is l3-simulator for?

Mainly developer.

View the repo → Decode another repo

This repo across BitVibe Labs

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