The continue loop as an hmz flow: the task once, then "continue" in the same session until the budget is spent.
One agent, one session: the task is its first turn, and continue is every turn after it. It
is the continue_loop that FlowBench scores.
You need hmz. In hmz, open /flow, go to
Flowverses → official → continue_loop and Install it.
To run a release without installing it, name it by its git ref:
hmz exec -f git+https://github.com/humanfia/continue-loop-flow@v0.1.0#continue_loop ...❯ $continue_loop the task
hmz exec -f continue_loop -a agent=claude/claude-opus-5:high \
-p budget.cost=5 "the task"| Role | Needs | |
|---|---|---|
agent |
nothing | Takes the task, then every continue. |
The flow takes no params of its own.
The budget: the turn that finds it spent ends the run. A turn that fails ends the run with that failure, once hmz has retried what could be retried.
There is nothing to pick up: a new run starts a new session on the task.
Another flow can call it by ref, load("continue_loop"); see
A flow that calls a flow.
@futrime, as listed in .github/CODEOWNERS.
Issues and pull requests are welcome. The flow is the continue_loop/ directory; its tests are in
tests/. With uv:
uv sync
uv run ruff check
uv run ruff format --check
uv run pytestCI runs the same on every pull request. A release is a vX.Y.Z tag on main; it reaches hmz
users once a flows/continue_loop/X.Y.Z/flow.yaml pointing at it is merged into
humanfia/flowverse.
Apache-2.0 © Humanfia