Add persistent user preference recall across Codex CLI conversations

AGENTS.md helps, but it is not the same thing as what I’m asking for.

My request is about persistent preference recall across new Codex CLI conversations, especially for user-level habits that repeat across repos and sessions. An AGENTS.md file is repo-scoped and project-specific. That makes it useful for things like build commands, test workflow, architecture constraints, and repo conventions, but it is a weaker fit for personal preferences such as:

• my preferred commit message style
• my default PR description structure
• my preferred response format for recurring tasks

There are a few reasons I see them as different:

1. AGENTS.md is tied to a repository, while many preferences are tied to the user.
2. It requires creating and maintaining files in each repo, even when the preference is global.
3. It is better for project instructions than for lightweight personal defaults.
4. It does not really solve continuity across unrelated projects or fresh workspaces.

So yes, AGENTS.md is a reasonable workaround today, and I would probably use it for repo-level conventions. But I still think there is a product gap: Codex CLI should ideally support explicit, persistent user preferences separately from repo instructions.

A strong model would be:

• AGENTS.md for repository or team rules
• persistent profile/preferences for user-level defaults
• per-chat overrides when needed

That separation would be cleaner and closer to how engineers actually work.