/Tech13h ago

Peter Steinberger, OpenClaw steward, shares a workflow automating open-source repository maintenance via recurring five-minute AI agent loops

Story Overview

Peter Steinberger posted details on a lightweight recurring loop that wakes every five minutes to hand OpenAI Codex a queue of open-source maintenance tasks across multiple GitHub repositories, routing work through custom skills so some items reach completion with minimal intervention.

2484.3K3276.9K345.3K
Nick Dobos
Peter Steinberger 🦞#382
Original post
Peter Steinberger 🦞@steipete#382inTech

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

2:09 AM · Jun 11, 2026 · 334.1K Views
Developer Impact

Two skill files now public for reuse

The maintainer-orchestrator and github-project-triage definitions sit in his agent-scripts repo, spelling out how the agent builds decision-ready cards, verifies PRs, and clears queues, though the exact list of covered repositories stays limited to the examples shown.

Open Question

Limits on full autonomy remain unclear

The setup still surfaces items for human review on higher-risk changes and the post offers no data on how often the loops run end-to-end without steering, leaving open how much oversight most maintainers would still need.

Sentiment

Many users praised the AI Codex Orchestrator and agent loops for automating OSS repo maintenance as brilliant and game-changing, while others called the token usage wasteful and elitist.

Pos
85.0%
Neg
15.0%
31 comments with sentiment.
Cluster Engagement
Posts from X
Most Activity
Most Activity
VIEWS13.1KBOOKMARKS251LIKES127RETWEETS1REPLIES10
Nick Dobos@NickADobos

Loops so hot right now Here are the loops I’m experimenting with:

Planners - morning brief, orient and context switch back into the flow. This pulls from outside data sources and also checks past chat logs to figure out our current progress. - daily planning - what did you get done this week? Friday end of week check in & review - Sunday/monday planning, 3 lanes, personal, side biz & projects, day job. Goal is top task prioritized and clear. - Monthly planning. Personal & side. business check in. Go over finances, etc.

Once weekly codebase / promptbase sweeps - code maid & janitor - code & prompt evolver & compounder - memory and docs cleanup consolidate dream sequence sweep

Watchers - sentry -> auto crash fix. Runs once a week and priorities top crashers - analytics alert -> auto fix. Fires when analytics trip. Usually when something breaks. - triager, scan bug reports and customer support requests from linear. Either fix or defer. When a fix is merged/shipped email the person who reported it.

Stock Day trader - once a day check portfolio, do research, check news, copy politicians, rebalance if needed

What loops are you using?

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

3hViews 13.1KLikes 127Bookmarks 251
Peter Steinberger 🦞@steipete

@eskoropisov You ask the man with unlimited tokens?

12hViews 3.1KLikes 48Bookmarks 2
Peter Steinberger 🦞@steipete

@hankyeolkyung codex mac/win app can spawn threads now!

12hViews 9KLikes 23Bookmarks 5
JQ@jqlive

@steipete That'd be nice to do. But my codex app likes to auto delete threads almost every time i launch the app, or when i use it for a long time. I don't trust it to maintain anything, if it can't even maintain its own state.

12hViews 8.6KLikes 17Bookmarks 2
Nick Dobos@NickADobos

I’m not giving you the exact prompts because they are 2-3 paragraphs max and all super jank & experimental.

Nick Dobos@NickADobos

Loops so hot right now Here are the loops I’m experimenting with:

Planners - morning brief, orient and context switch back into the flow. This pulls from outside data sources and also checks past chat logs to figure out our current progress. - daily planning - what did you get done this week? Friday end of week check in & review - Sunday/monday planning, 3 lanes, personal, side biz & projects, day job. Goal is top task prioritized and clear. - Monthly planning. Personal & side. business check in. Go over finances, etc.

Once weekly codebase / promptbase sweeps - code maid & janitor - code & prompt evolver & compounder - memory and docs cleanup consolidate dream sequence sweep

Watchers - sentry -> auto crash fix. Runs once a week and priorities top crashers - analytics alert -> auto fix. Fires when analytics trip. Usually when something breaks. - triager, scan bug reports and customer support requests from linear. Either fix or defer. When a fix is merged/shipped email the person who reported it.

Stock Day trader - once a day check portfolio, do research, check news, copy politicians, rebalance if needed

What loops are you using?

3hViews 802Likes 2Bookmarks 4
Peter Steinberger 🦞@steipete

@jqlive Most of these issues are fixed, but then again I'm on the alpha.

12hViews 7.5KLikes 24Bookmarks 1
Prince Bansal@princebansal94

Maybe yes. But not just skills, your channels setup and interaction with agents. Your agents composition and how you use them. Task orchestration and project management. Like with actual use case examples. I am very sure you just dont have a single telegram channel where you interact with the agent and manage the entire project. Or is it? 😳😳

12hViews 2KLikes 9Bookmarks 2
Marly@marlytokenman

@princebansal94 @steipete read his blog

11hViews 1.5KLikes 3Bookmarks 3
Peter Steinberger 🦞@steipete

@dan_spitzwieser Waking up and doing some API calls is fairly cheap, or opt for once per hour/day for lower token use.

12hViews 1.6KLikes 6Bookmarks 2
Luismi@EyLuismi

@steipete Hope you guys add "sub-threads" or "thread folders" in the future and make them available to agents to keep this more organised. I feel quite constrained right now. 😅 Also, Folders/Threads icons/avatars could be a nice addition

13hViews 3KLikes 5Bookmarks 2
Hankyeol Kyung@hankyeolkyung

@steipete The skill mentions "separate Codex threads" and worker thread naming/monitoring, but I couldn't find how the workers are actually created and managed. Are you using Codex subagents, multiple long-lived chats, or some custom orchestration layer?

12hViews 10.3KBookmarks 2
Prince Bansal@princebansal94

@steipete Hey Peter. Have you ever shared your setup publicly? I always doubt my setuo and get a feeling that there must be a more optimised way of doing things but then no credible references.

12hViews 8.5KLikes 7Bookmarks 1
Peter Steinberger 🦞@steipete

@lfji Do you even need issues? I just prompt whenever I have an idea.

12hViews 4KLikes 7
Vinay Varma@roronoazoro_189

@steipete

10hViews 445Likes 9Bookmarks 1
Peter Steinberger 🦞@steipete

@LonnyLot Way simpler to setup, and not as time critical as e.h. a comment bot.

12hViews 3.5KLikes 3Bookmarks 1
lonny@LonnyLot

@steipete Q: Why do this on a loop vs. a webhook action when e.g. a new GH issue or comment comes in?

12hViews 3.8KLikes 2Bookmarks 1
Evgeny Skoropisov@eskoropisov

@steipete fair. the invoice is the rate limiter

12hViews 1KLikes 11
Peter Steinberger 🦞@steipete

@EyLuismi possibly. I expect we'll learn more patterns as more folks start using this feature!

12hViews 2.5KLikes 5Bookmarks 1
Load more posts