Keep Codex chats by profile and project
If you use multiple Codex profiles, all your sessions get mixed together in the native CLI. CodexUse organizes every chat by the account and project it belongs to.
The problem: mixed sessions
The native Codex CLI saves session logs locally. Each session gets a timestamped directory with conversation history. The problem? There is no account association.
If you use multiple accounts (personal, work, clients), all sessions are mixed together. You cannot filter to show only client conversations or exclude personal chats from a work machine.
Why chat separation matters
1. Client confidentiality
When you are working on multiple client projects, you do not want to accidentally reference code or context from Client A while helping Client B. Separate chat histories by account prevent this.
2. Billing and audit
Some organizations require logs of AI-assisted work. Having clean per-account histories makes it easy to export relevant conversations for a specific client or project.
3. Context management
Resuming a session is more useful when you can quickly find the right conversation. Searching through hundreds of mixed sessions wastes time.
How CodexUse organizes chats
CodexUse tracks which Codex profile was active when each session started. This enables:
- Profile filtering: Show only chats from a specific account
- Search within profile: Find conversations without noise from other accounts
- Session resume: Continue a previous conversation with the correct account active
- Export by profile: Extract chat history for a specific client
The chat view in CodexUse
- Select a profile from the sidebar
- See all sessions associated with that account
- Search, filter, or sort by date
- Click to resume any session in the active context
Working with projects
Beyond profiles, you can organize chats by project directory. When you start Codex in a specific folder, CodexUse notes the working directory:
CodexUse can then filter chats by both profile AND project path, giving you fine-grained organization.
Resuming old sessions
When you resume a session in CodexUse, the app:
- Switches to the Codex profile that was active during that session
- Loads the conversation history
- Continues the context where you left off
This prevents the common problem of resuming a client session while accidentally using your personal account.
Best practices for chat organization
One Codex profile per client
If you work with multiple clients, create a CodexUse profile for each. This keeps conversations naturally separated and makes export straightforward.
Consistent project directories
Always run Codex from your project root directory. This makes project-based filtering reliable.
Name sessions meaningfully
When starting significant work, note what you are doing in your first message. This makes sessions easier to find later.
Troubleshooting
| Symptom | Likely cause | Action |
|---|---|---|
| Old sessions show wrong profile | Sessions created before CodexUse was installed | Historical sessions cannot be retroactively tagged; only new sessions are tracked |
| Cannot find a specific conversation | Searching in wrong profile or wrong date range | Check profile filter and expand date range in search |
| Session resume fails | Profile credentials expired | Re-authenticate the profile, then retry resume |
Export and backup
CodexUse lets you export chat history per profile:
- JSON export: Full conversation data for archiving or migration
- Markdown export: Human-readable format for documentation
- Filtered export: Only specific date ranges or search results
What to avoid
- Mixing client work across Codex profiles
- Ignoring which profile is active when starting new sessions
- Assuming old sessions (pre-CodexUse) are tagged. They are not
Related
Does the Codex CLI save chat history?
Yes, locally. But it does not organize by account. All sessions are mixed. CodexUse adds profile-based organization.
How does CodexUse organize chats by profile?
It tracks which profile was active when each session started, then lets you filter, search, and resume by profile.
Can I search through old Codex conversations?
The native CLI has limited search. CodexUse provides full-text search filtered by profile with session resume capabilities.