The following comment was made by an LLM, it may be inaccurate:

Based on my search, here are the potentially related PRs (excluding PR #18951, which is the current PR):

Related/Duplicate PRs:

1. PR feat(session): add custom compaction thresholds along with prevention of continuous compaction #10123 - feat(session): add custom compaction thresholds along with prevention of continuous compaction

   • feat(session): add custom compaction thresholds along with prevention of continuous compaction #10123
   • Directly addresses custom compaction thresholds and prevents continuous compaction - very similar scope

2. PR fix(session): prevent infinite loop in auto-compaction when assistant ended its turn #15532 - fix(session): prevent infinite loop in auto-compaction when assistant ended its turn

   • fix(session): prevent infinite loop in auto-compaction when assistant ended its turn #15532
   • Related to the same auto-compaction logic and preventing loops during assistant turns

3. PR feat(compaction): configurable threshold and model (global + per-model) #11931 - feat(compaction): configurable threshold and model (global + per-model)

   • feat(compaction): configurable threshold and model (global + per-model) #11931
   • Addresses configurable compaction thresholds with global and per-model settings

4. PR fix(session): preserve wait-for-user state after compaction #18941 - fix(session): preserve wait-for-user state after compaction

   • fix(session): preserve wait-for-user state after compaction #18941
   • Recently merged PR addressing session compaction state management

These PRs should be reviewed to ensure PR #18951 doesn't duplicate existing work, particularly #10123 and #11931 which explicitly address configurable compaction thresholds.

I checked the existing compaction flow before implementing this. This PR does not add a separate compaction mechanism - it reuses the current backend summarize/compaction path and makes it trigger proactively at the configured threshold while deduping in-flight compactions to avoid loops.

Thanks for updating your PR! It now meets our contributing guidelines. 👍

Automated PR Cleanup

Thank you for contributing to opencode.

Due to the high volume of PRs from users and AI agents, we periodically close older PRs using automated criteria so maintainers can focus review time on the most active and community-supported contributions.

This PR was closed because it matched the following cleanup criteria:

• The PR was created more than 1 month ago
• The PR had fewer than 2 positive reactions
• Positive reactions are counted as thumbs-up, heart, celebration, or rocket reactions on the PR

PRs created within the last month are not affected by this cleanup.

If you believe this PR was closed incorrectly, or if you are still actively working on it, please leave a comment explaining why it should be reopened. A maintainer can review and reopen it if appropriate.

Thanks again for taking the time to contribute.