wavves

wavves logo

one package for Cursor agents · on Agensi

Parallel agent loops with saved state and shared constraints. Through interaction with the moderator a user can set up a library of tasks that builds up through waves. An orchestration agent runs in the background. Runners run the scoped execution-layer work that the orchestration agent assigned to them. On pickup the moderator remeasures the JSON and log evidence saved in gate-captures for what the orchestration agent completed.

Package

On pickup the moderator remeasures the JSON and log evidence saved in gate-captures for what the orchestration agent completed. In /mod-rotate the next moderator term can also run a rotation history audit across the rotation files in a repo.


Package

$50 one-time

wavves

wavves skills and blank templates sit in the package. The README keeps product keep-terms with their plain meaning.

Through /remeasure the moderator turns an agent's "done" into a gate with a claim and a check someone else can rerun. JSON and log evidence lands on disk in gate-captures.

On pickup the next moderator term runs the pickup check in /mod-rotate. A fix row for messages in the output of either script sits in five recovery playbooks.

In /mod-rotate the next moderator term runs a rotation history audit across the rotation files in a repo in order. Gaps in the numbering and breaks in the chain of terms get an ERROR line.

Scripts in the wavves package need Python 3 and no other packages. Pickup commit checks and rotation history audit runs also need a local git binary.

Get on Agensi

Demos

The video below shows the wavves workflow written by a script with no live agent at the keyboard. Files in the sample project of the video are invented for the demo.


The wavves control surface

In the wavves workflow the moderator keeps plans and results for lanes of work as plain files under one wavves folder. On screen INDEX.md comes first, followed by the lane folders of the sample repo. Inside one lane the moderator keeps a waveset, the plan file with the waves and gates of the lane. An orchestration agent runs runners across the execution layer for a wave. The orchestration agent writes JSON and log evidence into gate-captures. On pickup the moderator remeasures that evidence before the next wave opens. At the end the rotations folder holds one rotation file for the handoff to the next moderator term. The same folders come from blank templates in the wavves package.