Archestra Apps HackathonJoin now

Thread

A
Aviral9:30 AMOpen in Slack
Hi team , I was confused about this , while reading the limits implementation, I noticed the frontend computes 75%/90% usage warnings but the backend only enforces the hard limit
was this intentionally kept as a UI-only signal, or was there ever discussion about exposing it as a backend event or alert?

5 replies
A
Aviral10:57 AMOpen in Slack
@user Hi sir , could you please help me with this?
IK
Innokentii Konstantinov (archestra team)3:52 PMOpen in Slack
Hi! I'm not sure I understand which backend event you would like to expose?
A
Aviral9:43 AMOpen in Slack
Thanks! I meant an “approaching limit” signal before the hard block, not a UI warning. Right now it looks like the frontend computes 75%/90% locally, but I was asking whether the backend should expose a signal when usage crosses a threshold so it can be used for alerts or automation.
IK
Innokentii Konstantinov (archestra team)4:27 PMOpen in Slack
We never planned it, if you have a specific use case or a problem you want to use it for - we will be happy to have it! If it's just a feature for a sake of feature - it doesn't work for us 😞
❤️1
A
Aviral7:46 PMOpen in Slack
Thanks! I was mostly brainstorming and trying to understand the design better. The use case I had in mind was long-running agents approaching their budget limit and taking some action before hitting the hard stop, but I agree that's just one possible scenario and may not be a strong enough use case . i'll keep exploring the codebase, and I'm sure I'll come across more questions as I understand the system better.