I have a Gitops project with Fluxcd used in two Kubernetes clusters. I can't allow the agent to commit and push to GitHub without manual review first, as this could lead to something going wrong and compromising the production infrastructure.
I have an explicit rule prohibiting commit+push, and this works fine until the session is compacted and a new session starts.
It seems that after compaction, the rules are lost. I believe a safer approach would be to compact the conversation and include the user-defined rules in their entirety in the new context after compaction. Otherwise, it poses a significant risk in some use cases.

I have some rules in an AGENTS.md file and also in a custom agent called coder.

This seems like a bug, or at least a shortcoming, in the current workflow.

Is there a way I can explicitly configure it somewhere to ALWAYS include the agent contents and local settings after compaction?