Have you tried writing into the AGENTS.md something like, "Always be on the lookout for dead code, copy-pasta, and other opportunities to optimize and trim the codebase in a sensible way."
In my experience, adding this kind of instruction to the context window causes SOTA coding models to actually undertake that kind of optimization while development carries on. You can also periodically chuck your entire codebase into Gemini-3 (with its massive context window) and ask it to write a refactoring plan; then, pass that refactoring plan back into your day-to-day coding environment such as Cursor or Codex and get it to take a few turns working away at the plan.
As with human coders, if you let them run wild "improving" things without specifically instructing them to also pay attention to bloat, bloat is precisely what you will get.
Subject (((((Solar battery) costs) plummet) analysis) findings)
Verb [back]
Object (anytime (electricity availability))
Garden path sentence structure trap creation relies on initial word parse error encouragement. Brain pattern recognition system default subject-verb-object order preference exploitation causes early stop interpretation failure.
Solar battery costs plummet phrase acting as complex noun modifier group creates false sentence finish illusion. Real subject findings arrival delay forces mental backtrack restart necessity.
Noun adjunct modifier stack length excess impacts processing speed negatively. Back word function switch from direction noun to support verb finalizes reader confusion state.
We write to be understood. Short sentences and simple words make the truth easy to see.