codex - 💡(How to fix) Fix user input when using /goal should be printed even if there's error [2 comments, 3 participants]

This is not a bug but a UX issue. Even if there is a character limit for the /goal command, a better UX would be to print the prompt onto the screen before throwing the error. prompt is persisted and printed to the screen before surfacing the error.

TL;DR

The issue can be mitigated by printing the prompt to the screen before attempting to set the goal, allowing the user to recover their input in case of an error.

Guidance

• Consider modifying the /goal command to display the user's input before attempting to set the goal, ensuring that the input is not lost in case of an error.
• If a character limit exists for the /goal command, implement a check to display a warning or error message when the limit is reached, rather than silently failing.
• Review the current error handling for the /goal command to determine why the input is not being persisted or captured as an event.
• Investigate adding a feature to persist user input for the /goal command, allowing users to recover their work in case of an error.

Example

No code example is provided as the issue does not specify the programming language or implementation details.

Notes

The issue is reported as a UX issue rather than a bug, and the solution will depend on the specific implementation of the /goal command and the Codex CLI.

Recommendation

Apply workaround: Modify the /goal command to print the user's input before attempting to set the goal, and consider adding a character limit check to display a warning or error message when the limit is reached. This will improve the user experience and prevent loss of user input.