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

@steipete Ppl hate these takes because we actually have limited tokens

@eskoropisov You ask the man with unlimited tokens?

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

@princebansal94 I just did, including skills?

@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.

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

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

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? 😳😳

@princebansal94 @steipete read his blog

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

@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

@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?

@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.

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

@steipete

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

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

@steipete fair. the invoice is the rate limiter

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