Can users stack Quibblers, so Quibbler 2 corrects Quibbler 1 if, say, it fabricates an issue in the code it's reviewing? If so, have you found an optimum number of Quibblers for the Quibbler stack? Also, might users form a Quibbler council such that multiple Quibblers review the same thing and form a consensus before proceeding?
An agent's agent?
In other words, the Quibbler siphons wrackspurts away from your code.
More explanation here that I found by Googling around. Though not sure it has more info than the Github page.
https://fulcrumresearch.ai/2025/10/22/introducing-orchestra-...
hey HN! happy to answer any questions
this kind of tool is especially useful in longer running tasks to enforce your intent without having to check in on your agent all the time
Can users stack Quibblers, so Quibbler 2 corrects Quibbler 1 if, say, it fabricates an issue in the code it's reviewing? If so, have you found an optimum number of Quibblers for the Quibbler stack? Also, might users form a Quibbler council such that multiple Quibblers review the same thing and form a consensus before proceeding?
I love the pixel-perfect precision with which this comment is straddling the Poe's Law line.
That aside I also love the concept of Quibbler Council and I'd get a kick out of seeing it in action.
Vibeception
But who polices the vibe police?
“Well, who’s gonna monitor the monitors of the monitors?” — Enemy of the State (Movie)
> We’ve found Quibbler useful in preventing agents from: 1) fabricating results without running commands
What a world we've created for ourselves
Next step is critics for the critics.