errant plume
After one vibe request, 14 vibe requests consumed as shown in screenshot. Then I was working manually and building docker images through docker-compose, manual editing of files.
When I checked, 18 Vibe reques were additionally got consumed. What is happenning? My guess is the hooks are consuming the vibe requests. If it is so, please remove the hook feature, it is useless. If not removing then make it free.
loud furnace
You don't have any triggered hooks, right? cc:// @harsh ledge
harsh ledge
@errant plume Do you have multiple hooks setup for the project? Can you share the hook configuration? Trying to understand the workflow that led to the additional requests. For context, hook execution will consume vibe request/s based on its complexity.
errant plume
yes, I have only hook to update the documents after performing tasks. But it seems, it updates wheneverI do manual coding as well. SO to keep track of vibe/specs, need to switch off the hooks.
I switched my hooks off and now my vibe requests are not getting consumed.
harsh ledge
Thanks for clarifying Keddy! For this particular scenario, I'd recommend configuring the docs update hook to be a manual trigger instead of a file create/save update event where once the changes are in you can invoke the hook on-demand to update the README/docs. I personally find this workflow to be helpful.
jagged minnow
As recommended, the best practice is to configure the docs update hook to be manually triggered instead of having it automatically fire on file create/save events. This way, you can invoke the hook on-demand to update documentation only when needed, providing better control over when vibe requests are consumed.
The new credit system will also help as smaller requests will consume fractional credits. Please see "Announcing new pricing plans and Auto, our new agent"
native dirgeBOT
✅ - Why vibe request are consumed even I am executing manual commands in terminal or modify co...