user input when using /goal should be printed even if there's error

Resolved 💬 2 comments Opened May 5, 2026 by JCSnap Closed May 5, 2026

What version of Codex CLI is running?

0.128.0

What subscription do you have?

PRO

Which model were you using?

gpt-5.5

What platform is your computer?

macOs

What terminal emulator and version are you using (if applicable)?

_No response_

What issue are you seeing?

I entered a long prompt when using the /goal feature and got this:
Failed to set thread goal: thread/goal/set failed in TUI

I lost the whole prompt which I spent 20 minutes crafting which is incredibly frustrating. It is not persisted in my sessions, nor captured as an event etc...

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.
alternatively, show something if the character limit is reached.

What steps can reproduce the bug?

/goal [some decently long prompt]

What is the expected behavior?

prompt is persisted and printed to the screen before surfacing the error.

or show something when the character limit is reached.

Additional information

_No response_

View original on GitHub ↗

This issue has 2 comments on GitHub. Read the full discussion on GitHub ↗