claude-code - 💡(How to fix) Fix /resume picker: show first message instead of last message [2 comments, 2 participants]

TL;DR

Reverting the session picker to show the first message of each conversation instead of the last message is likely the most straightforward fix.

Guidance

• Investigate the recent changes made to the session picker to identify the specific code modification that caused the switch from showing the first message to the last message.
• Review the database schema or data storage to understand how conversation messages are stored and retrieved, which will be essential for reverting or configuring the message display.
• Consider adding a configuration option to allow users to choose between displaying the first or last message, enhancing user experience and flexibility.
• Evaluate the impact of this change on other parts of the system that might rely on the current behavior of the session picker.

Example

No specific code example can be provided without more context, but the fix would likely involve modifying the query or function that retrieves conversation previews to sort or select messages based on their order (first or last) instead of the current last message approach.

Notes

The exact implementation details depend on the underlying technology stack and database structure, which are not specified in the issue. This guidance assumes a typical web application with a relational or NoSQL database.

Recommendation

Apply a workaround by modifying the session picker to display the first message of each conversation, as this directly addresses the user's request and provides a more useful preview for identifying sessions.