Add persistent user preference recall across Codex CLI conversations

Yes, currently this has not been implemented in the way @adrian.a.adewunmi is describing it. My suggestion to use a master project to provide personal preferences to individual projects is just an idea for a workaround. I think it can work well across quite a few use cases, but it is definitely not the same as a central preference setting. Following this conversation, I just wanted to add one small detail that may be helpful when working with agents: there can be several agents.md files inside a project. For example, a large monorepo can benefit from this. Agents are trained to always read the nearest agents.md file. This is another way to stay in control. Codex, for example, re-reads agents.md after a context compaction.