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
{{ message }}
Repository navigation
Commit e449743
Browse filesBrowse the repository at this point in the historyBrowse files
**What & why.** Watches now honour a plan's watch limits. A watch whose
window exceeds the plan's `agentWatchMaxHours`, or that would push the
org past its `agentWatchers` count, is refused with a new
`watch_limit_reached` result and an upgrade hint (a chat line on the
card, HTTP 409 on the API).
**Key decisions.**
- Plan limits are a floor *below* the existing code ceilings: `min(plan,
WATCH_MAX_HOURS=24)` for the window, and the per-chat cap of 3 still
applies independently. Plans only tighten, never loosen.
- Watcher count is org-wide and checked only after the immediate check
declines, so a one-shot consumes no slot.
- Fails open: an absent limit resolves to the unlimited sentinel, so
self-hosted is unaffected; the upgrade nudge is gated on
`isBillingConfigured()`.
- Follow-up: quiet Pro-mark on the card's long-window options.
TRI-12863
Watches now respect your plan's limits: free plans can run a limited number of watches at once and for a shorter window, with a prompt to upgrade for more.
0 commit comments