Description
DeepCode CLI sometimes emits important user-facing information — including the final generated prompt, cost estimation, confirmation context, and task execution status — only inside Thinking messages.
These Thinking messages are visible during the live session, but after exiting and resuming the session they are permanently collapsed/not rendered to the user.
The underlying information is not actually lost from the model context: after resuming, I explicitly asked the agent to reproduce the previous final prompt and generation parameters without recalculating them, and it successfully returned the complete prompt and all parameters correctly.
Therefore, this appears to be a UI/message-routing issue rather than conversation-state loss.
Steps to reproduce
- Start DeepCode CLI and ask the agent to perform a task that produces substantial intermediate/final information before
AskUserQuestion.
- Observe that the agent places important user-facing content inside
Thinking. In my case this included:
- complete final video-generation prompt
- cost estimate
- generation parameters
- confirmation context
- Answer the
AskUserQuestion and continue the task.
- Exit DeepCode CLI.
- Resume the same session.
- Observe that the previous Thinking content is no longer accessible/rendered to the user.
- Ask the resumed agent to reproduce the previous information without recalculating it.
- The agent can reproduce it correctly, demonstrating that the content remains in the model/session context but is no longer visible in the CLI.
Actual behavior
Important user-facing information may exist only in Thinking. After session resume, this information becomes invisible to the user even though it remains available to the agent.
Expected behavior
Information required for user decisions, confirmations, or final task results should not depend exclusively on transient Thinking output.
Such information should be emitted as durable user-visible assistant/tool content and remain accessible after session resume.
Alternatively, if Thinking messages are intentionally part of the user-visible transcript, the CLI should provide a way to inspect historical Thinking after resume.
Additional evidence
The attached screenshots show:
- The complete final prompt and cost estimate being emitted inside
Thinking.
AskUserQuestion containing only a summarized confirmation context.
- After confirmation, additional task execution/status information continuing to be emitted through
Thinking.
After resuming the session, I asked the agent to reproduce the previous prompt and parameters without recalculating them. It successfully returned the complete prompt and all parameters, confirming that the information was retained in the model context but was no longer rendered to the user.

Description
DeepCode CLI sometimes emits important user-facing information — including the final generated prompt, cost estimation, confirmation context, and task execution status — only inside Thinking messages.
These Thinking messages are visible during the live session, but after exiting and resuming the session they are permanently collapsed/not rendered to the user.
The underlying information is not actually lost from the model context: after resuming, I explicitly asked the agent to reproduce the previous final prompt and generation parameters without recalculating them, and it successfully returned the complete prompt and all parameters correctly.
Therefore, this appears to be a UI/message-routing issue rather than conversation-state loss.
Steps to reproduce
AskUserQuestion.Thinking. In my case this included:AskUserQuestionand continue the task.Actual behavior
Important user-facing information may exist only in
Thinking. After session resume, this information becomes invisible to the user even though it remains available to the agent.Expected behavior
Information required for user decisions, confirmations, or final task results should not depend exclusively on transient
Thinkingoutput.Such information should be emitted as durable user-visible assistant/tool content and remain accessible after session resume.
Alternatively, if Thinking messages are intentionally part of the user-visible transcript, the CLI should provide a way to inspect historical Thinking after resume.
Additional evidence
The attached screenshots show:
Thinking.AskUserQuestioncontaining only a summarized confirmation context.Thinking.After resuming the session, I asked the agent to reproduce the previous prompt and parameters without recalculating them. It successfully returned the complete prompt and all parameters, confirming that the information was retained in the model context but was no longer rendered to the user.