-
Notifications
You must be signed in to change notification settings - Fork 13.3k
Store /side chats in session logs #20262
Copy link
Copy link
Open
Labels
TUIIssues related to the terminal user interface: text input, menus and dialogs, and terminal displayIssues related to the terminal user interface: text input, menus and dialogs, and terminal displayenhancementNew feature or requestNew feature or requestsessionIssues involving session (thread) management, resuming, forking, naming, archivingIssues involving session (thread) management, resuming, forking, naming, archiving
Metadata
Metadata
Assignees
Labels
TUIIssues related to the terminal user interface: text input, menus and dialogs, and terminal displayIssues related to the terminal user interface: text input, menus and dialogs, and terminal displayenhancementNew feature or requestNew feature or requestsessionIssues involving session (thread) management, resuming, forking, naming, archivingIssues involving session (thread) management, resuming, forking, naming, archiving
Type
Fields
Give feedbackNo fields configured for issues without a type.
What variant of Codex are you using?
cli
What feature would you like to see?
/side is ephemeral by design, but the chats that you might have there are sometimes end up producing useful context for future work. Would be nice to be able to easily store these without having to tell the chat export some sort of handoff markdown. Instead I'd like to be able to resume / point codex at a session file for context.
The ask here is to manually opt in to transitioning from ephemeral to a non-ephemeral thread somehow. It's possible that this is available through some path already, but I didn't see it. (Asking codex to find a way to do this didn't turn up anything obvious - I resorted to letting it write out a markdown handoff doc instead).
Additional information
No response