Theo, T3 Stack creator, uses OpenAI Codex and orchestrator scripts to automate GitHub PR triage · Digg

/Tech6h ago

Theo, T3 Stack creator, uses OpenAI Codex and orchestrator scripts to automate GitHub PR triage

Story Overview

Theo's demonstration pairs OpenAI Codex with reusable orchestrator scripts that wake on a schedule, scan open pull requests, sort them into autonomous versus owner-needed buckets, and spin up separate worker threads for builds, reviews, and revival attempts.

3487.1K46410.5K900.4K

Original post

Theo - t3.gg@theo#1325inTech

I underestimated how cool this workflow is.

Had Codex go through a bunch of stale PRs last night. Closed all the useless ones, revived all the out of date ones.

Each "revived" pr got a thread to build it and a 2nd to review it.

Peter Steinberger 🦞@steipete

Here's a simple loop: Tell codex to maintain your repos, wake up every 5 minutes and direct work to threads. That makes it easy to parallelize+steer work as needed.

I use a orchestrator skill combined with my triage+autoreview+computer use skills, so some work can land autonomously. https://github.com/steipete/agent-scripts/blob/main/skills/maintainer-orchestrator/SKILL.md https://github.com/steipete/agent-scripts/blob/main/skills/github-project-triage/SKILL.md

12:19 PM · Jun 18, 2026 · 184K Views

Developer Impact

Parallel threads shoulder the routine checks

Each loop classifies items, gathers diffs and CI signals, then delegates review or close actions to dedicated Codex sessions while a central monitor keeps logs and shuts down idle threads.

Open Question

Boundaries still depend on the owner

Exact repositories in use, success rates on revived PRs, and any custom tweaks to the triage rules stay visible only inside the individual runs shown in the task lists.

Sentiment

Many users praise AI orchestrator loops for autonomously triaging and reviving stale GitHub PRs as practical and genius, while others call the workflow cursed or express frustration with Codex access and reliability.

Pos

55.8%

Neg

44.2%

35 comments with sentiment.

Cluster Engagement

Digg Deeper

No Digg Deeper questions have been answered for this story yet.

Related links

agent-scripts/skills/github-project-triage/SKILL.md at main · steipete/agent-scripts

GITHUBVia

agent-scripts/skills/maintainer-orchestrator/SKILL.md at main · steipete/agent-scripts

Posts from X

Most Activity

VIEWS10.5KBOOKMARKS37LIKES59REPLIES6

Theo - t3.gg@theo

How did I do it? Handful of things:

1. Bumped the subagent parallelism limit in Codex from 3 to 20 2. Set up a well defined goal to port a big piece of software to Rust (more coming soon) 3. Revived an old project that needs a LOT of work 4. this

Theo - t3.gg@theo

I underestimated how cool this workflow is.

Had Codex go through a bunch of stale PRs last night. Closed all the useless ones, revived all the out of date ones.

Each "revived" pr got a thread to build it and a 2nd to review it.

6h10.5K5937

RETWEETS432

Peter Steinberger 🦞@steipete

Here's a simple loop: Tell codex to maintain your repos, wake up every 5 minutes and direct work to threads. That makes it easy to parallelize+steer work as needed.

I use a orchestrator skill combined with my triage+autoreview+computer use skills, so some work can land autonomously. https://github.com/steipete/agent-scripts/blob/main/skills/maintainer-orchestrator/SKILL.md https://github.com/steipete/agent-scripts/blob/main/skills/github-project-triage/SKILL.md

7d710.8K5.7K9.3K

Peter Steinberger 🦞@steipete

@jlave_dev My agent is making threads, it needs to be organized. Not me.

7d2.1K41

Peter Steinberger 🦞@steipete

@Upscalpfutures @jqlive Hey at least we’re not starting a 1.8GB VM on every app start like some competitor. 🙃

7d67931

Peter Steinberger 🦞@steipete

@slopwareindy No. Each project is it's own folder. Agents create the threads.

7d3.1K11

Theo - t3.gg@theo

@JakeLeventhal @OpenAIDevs @conductor_build All of these threads have their own worktrees so that doesn't work either.

Agreed that we need to figure out UX around these flows.

5h1903

Theo - t3.gg@theo

@FarzinNasirii Coming soon™

5h4233

Peter Steinberger 🦞@steipete

@latent_walk u wanna know all my secrets?\

7d1K1

JQ@jqlive

I've tried that and ended up messing up the codex app lol. Electron app did not like being messed with. I had to redownload and re-install. But I did learn that they're all stored in a sqlite database. So you can ask codex to search for them, if you remember the contents of your threads. But they're not visible in the codex app itself.

6d30

Virgil Maro@_virgil19

@theo 20 parallel agents just means 20 outputs to review. the bottleneck didnt move, it got 20 copies

6h722

Peter Steinberger 🦞@steipete

@ty_udy For some of the hairier issues, yes. For easier stuff where I can e2e verify, no.

6d6474

Ty Udy@ty_udy

@steipete Do you ever code review the code anymore?

6d630

Upscalp Futures Trading Assistant@Upscalpfutures

@steipete @jqlive They're not, Peter. And the most recent versions of the app have diabolical memory leak issues.

7d603

Theo - t3.gg@theo

@_virgil19 lmao no not at all

20 parallel agents means the code is being reviewed 20 times by bots before I ever have to look at it

6h861

Jake Leventhal@JakeLeventhal

@theo The problem with this workflow in tools like T3 code and the @OpenAIDevs Codex app is it gets impossible to organize threads at scale like this. Ideally they're grouped into workspaces per worktree like @conductor_build.

6h203

Upscalp Futures Trading Assistant@Upscalpfutures

@steipete @jqlive Oh yikes. Who's that?

Can't be Claude Code Desktop surely. It works very smoothly for me.

Whereas Codex Desktop last two versions grind my laptop to a halt within ten minutes.

I'm no Claude Maxi, by the way. I have a ChatGPT Pro subscription and a Pro Lite subscription 😂

7d141

Branavan Selvasingham@0_branavan_1

@steipete Super easy actually and it works really well.

7d1261

Antonin 🌞@antonincohen

@steipete @steipete Have you gotten this orchestrator loop working with Codex cloud threads? He doesn't want to create threads in my Cloud projects... he can spawn local threads but he said he can't list/read/create against the cloud project from the orchestrator

4d125

Farzin@FarzinNasirii

@theo @othman_tabeche please also added a "queue" option 🥲 instead of instant steering. it would mean a world to me

4h351

Theo - t3.gg@theo

@othman_tabeche @FarzinNasirii Far from useless. Still the best remote client by far and I use it a ton every day for that

4h79