In version 0.46, I noticed that even when created files comply with the project rule’s auto-attach configuration, they still don’t automatically follow the rules, whereas this worked correctly in version 0.45.
Additionally, in 0.46, when one rule references another rule within the configuration - for example:
“Complete ■■■ feature, refer to @■■■.mdc”
The referenced documentation doesn’t get considered by the agent.
I believe these changes severely impact development efficiency.
After further investigation, I realized that in v0.46, the referenced rule’s Description field must be explicitly filled for the reference to take effect. This behavior differs from v0.45, where the rule could be triggered even if the Description was empty.
Further investigation reveals that in v0.45, the agent could recognize the globs parameter, allowing it to automatically select relevant rules when editing files matching specific patterns. However, in v0.46, the agent no longer detects the globs parameter. This results in unexpected behavior (e.g., rules are not triggered unless explicitly referenced via @rule-file ), potentially leading to code edits that violate project standards. Restoring globs awareness or providing alternative pattern-matching logic may be critical for maintaining workflow efficiency.