You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When using Claude unattended in CI, it can be hard to setup guardrails that limit uncontrolled usage. We've been using naive timeouts as a means of achieving this, but this is not as fine-grained as it could be, because not all time spent in Claude Code costs us money. I'd rather have a 30 minute timeout, but set a $ cap for a given session.
The text was updated successfully, but these errors were encountered:
In unattended mode it must be scripted - so why not just have a project command /project:enforce-limits that runs /costs and analyzes the output? Long-term it should just be a built-in command like /cost or /compact - e.g. /enforce-limits which could be called and uses a config variable
When using Claude unattended in CI, it can be hard to setup guardrails that limit uncontrolled usage. We've been using naive timeouts as a means of achieving this, but this is not as fine-grained as it could be, because not all time spent in Claude Code costs us money. I'd rather have a 30 minute timeout, but set a $ cap for a given session.
The text was updated successfully, but these errors were encountered: