Feature Enhancement: default to continue conversation instead of new #27
Comments
spachava753
pushed a commit
that referenced
this issue
Feb 6, 2025
…28) * Initialize PR for issue #27 * fix: store user input in conversation messages When listing conversations with -list-convo, the messages column was empty because the user input was not being stored in the userMessage field of executorWrapper. This commit fixes the issue by storing the input in userMessage before executing the wrapped executor, ensuring the messages column shows the actual user input. * feat: change default behavior to continue conversations This commit changes how conversations are continued in cpe: - Add new '-new' flag to explicitly start a new conversation - Change default behavior to continue from last conversation - Remove 'last' as a valid argument for '-continue' flag (use default behavior instead) - Update help text and documentation - Add proper error handling for invalid conversation IDs Old behavior: $ cpe 'Hello!' # Start new conversation $ cpe -continue last 'Hi again!' # Continue from last conversation $ cpe 'Good morning!' # Start new conversation New behavior: $ cpe 'Hello!' # Start new conversation $ cpe 'Hi again!' # Continue from last conversation $ cpe -new 'Good morning!' # Force new conversation The -continue flag now only accepts conversation IDs, as the default behavior handles the common case of continuing from the last conversation. * feat: use lowercase-only conversation IDs This commit changes the conversation ID generation to: - Use only lowercase letters (a-z) instead of alphanumeric characters - Add collision detection to ensure uniqueness - Keep 6-character length for good balance of readability and uniqueness This makes conversation IDs easier to read and type manually while maintaining uniqueness through collision detection (max 10 attempts). Example ID format: Old: 'c0nv1D' (alphanumeric, mixed case) New: 'eogyld' (lowercase only) The change improves user experience when copying or typing IDs manually, while the collision detection ensures we don't have duplicate IDs even with the reduced character set. --------- Co-authored-by: github-actions[bot] <github-actions[bot]@users.noreply.github.com>
|
Feature implemented |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
It is more common to use the flag
-continuethan to start a new conversation from scratch, as previous conversational context provides great value when doing iterative refinement, which is the mode development 80% of the time. We should change the behavior to continue the conversation be default. Also, provide some quality if life improvements, for example, the message column when listing conversations is empty, conversation IDs can constructed using just lowercase alphabet characters with length of six charactersThe text was updated successfully, but these errors were encountered: