Unclear What the change to the compacting check means for a user in practice is not stated.
What
When several usage pools could cover the same use, admin configuration (settings an organization's administrator manages) decides which one is used.
pooled_conflict_ruleset to "priority_list" now hands the order inpooled_priority_orderto the choice of pool. With any other rule, no order is passed. Before, the choice of pool took no priority order at all.- Admin configuration with
pooled_conflict_ruleset to "priority_list" is now rejected unlesspooled_priority_orderholds at least one group. The error reads "admin.pooled_conflict_rule: priority_list needs at least one group in admin.pooled_priority_order". - The
compact_not_needed_at_blocking_limitcheck, which concerns compacting (shortening) a conversation when it reaches its limit, also skips when a breaker was skipped, and it adds conditions about the context window, the amount of conversation Claude can hold at once.
Why
Admins can rank which pool pays when more than one applies. A priority list left empty is caught when the configuration is checked, not left to fail later.
Names in the bundleadmin.pooled_conflict_ruleadmin.pooled_priority_orderpriority_list
Something disagreesSomething we can check disagrees with this entry, or the writer said they could not settle it.
The writer flagged doubt
What the change to the compacting check means for a user in practice is not stated.