Vens makes LLM calls and has no idea what they cost. No ceiling, no warning, nothing stops a big scan from running up the bill. On a metered API key that's a real worry, especially the first runs where you don't know the batch count yet.
Would like a budget gate: cap a run at a rough token or dollar estimate and stop (or prompt) before it blows past. Something like --max-spend or --max-tokens, checked before each batch.
A rough estimate is fine, it doesn't need to be exact. The point is a guardrail so people can try vens without fear of draining their quota.
Ref: limitations #8 (no built-in cost control).
Vens makes LLM calls and has no idea what they cost. No ceiling, no warning, nothing stops a big scan from running up the bill. On a metered API key that's a real worry, especially the first runs where you don't know the batch count yet.
Would like a budget gate: cap a run at a rough token or dollar estimate and stop (or prompt) before it blows past. Something like
--max-spendor--max-tokens, checked before each batch.A rough estimate is fine, it doesn't need to be exact. The point is a guardrail so people can try vens without fear of draining their quota.
Ref: limitations #8 (no built-in cost control).