Possibly, but does it cost them extra money to add the words “in agent mode” (i.e. “to choose from in agent mode”)? 
What I’m curious about is — doesn’t it remember past conversation rules?
For example, if I tell it in my project that all buttons must always be red, and then we continue developing — when I ask it to add another button, shouldn’t it remember that the button should be red?
In my opinion, these rules files are more confusing than helpful.
They might seem useful at first, but they just add more clutter on top of the already heavy codebase, and having to deal with rule files can become frustrating.
What I don’t understand is — since the model can sometimes review past conversations and update its behavior accordingly, why not use that memory more intelligently?
It’s explained in Context Window - memory only happens if you stay in the very same chat. But the longer the chat goes, the more overwhelmed it will get and start causing a mess.
So you have to choose between long term memory and more quality answers.
1 Like
Yes, I’m aware of that. In fact, when the conversation gets too long, I usually close it and start a new one.
But I’ve seen many examples where it feels like you’re building an entire project on top of the rules defined in an MCP (Model Code Protocol).
You’re spending more time writing rules than actually writing code.
