Repository navigation
fix(server): a usage limit no longer snoozes the thread - #142
Merged
nullStack65 merged 1 commit intoNov 20, 2026
Merged
Conversation
A limit stop stays in the inbox so the limited state is visible and the model can be switched. The per-thread "Snooze until reset" button still hides one thread until its allowance returns, and auto-resume is unchanged. Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com>
|
Important
This repository does not receive automatic reviews because it has fewer than 10 stars.
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Deploy: fleet
Summary
snoozeLimitedThreadssetting, which this fleet has turned on.Test plan
vp test run src/orchestration-v2/UsageLimitRecoveryWorker.test.ts src/storageCleanup.test.tsinapps/server: 231 passed, including a new case that a limit stop does not snooze even when the old flag is asked for.runtimeLayer.test.tsfiltered to the manual snooze case and the independent-patches case: both passed.packages/contracts,apps/web, andapps/mobileis clean.apps/serverandpackages/client-runtimeshow the same 7TS2366errors as base3ad1bfdd4f; none are in this diff.grok/grok-4.7): no Critical or Important findings.🤖 Generated with Claude Code