[FEATURE] context visibility for the agent so it can autonomously trigger a rule set in CLAUDE.md when reaching max context usage before compaction hits

Resolved 💬 3 comments Opened Feb 9, 2026 by elfegesMind Closed Feb 12, 2026

Preflight Checklist

  • [x] I have searched existing requests and this feature hasn't been requested yet
  • [x] This is a single feature request (not multiple features)

Problem Statement

The current flow requires me to manually alert Claude to apply a Rule set in CLAUDE.md as it has no visibility to its context usage.

Proposed Solution

Give Claude visibility to its context usage so it can apply required rules at required (by rule) threshold.

Alternative Solutions

_No response_

Priority

Medium - Would be very helpful

Feature Category

CLI commands and flags

Use Case Example

Example:
Despite it already great ability to transfer context, it still requires CLAUDE.md rules triggers, which cannot happen without context awareness.

Additional Context

Despite existing context transfer, still feel like an Alzheimer's patient; often breaking features. Tried to have clear rules set to prevent that but it simply forgets them for lack of proper trigger mechanism: will apply said rule only after compaction hit, instead of ahead of it. Rule includes updating handoff and historical documentation, critical for overall project consistency.

View original on GitHub ↗

This issue has 3 comments on GitHub. Read the full discussion on GitHub ↗