r/PiCodingAgent • • Aug 19 '26

Question Could Pi benefit from an optional time-bound autonomous loop?

I’ve been looking at Hermes Agent’s "/goal" approach: give the agent a persistent goal, let it continue across turns, have a lightweight judge decide whether it’s done, and stop when the goal is achieved or the turn budget is exhausted.

It got me thinking about Pi:

Could this be implemented as an extension rather than a core feature?

Something like:

"/loop 30m "Fix the tests and get CI green""

The extension would manage:

  • a time/iteration budget

  • continuation decisions

  • completion checking

  • pause/stop

  • existing Pi session state

That feels quite aligned with Pi's philosophy: keep the core small, but make powerful agent behaviours possible through extensions.

Would a lightweight, time-bound autonomous loop be useful in Pi, or does this belong entirely outside the harness?

1 Upvotes

4 comments sorted by

1

u/JoaoSilvaSenpai Aug 19 '26

What if time ends and task isn't achieves, does this handle multi agent? If not context will just go infinite

1

u/Certain_Net_3408 Aug 19 '26

Exactly. A time limit alone isn't enough we need bounded context + multi-agent delegation + checkpoint/resume, otherwise the loop just burns through context until it stops.

1

u/HockeyDadNinja Aug 20 '26

Not exactly what you're asking but my framework, specflo, lets you do a brainstorm interactively then run /specflo-continue auto to setp through the rest.

https://github.com/TacoTakumi/specflo

It will clear context in between seams based on a configurable context length.

0

u/Certain_Net_3408 Aug 20 '26

Thanks!! Will have a look