[GH-ISSUE #539] Hide Reasoning feeback after response generated #427

New issue

Closed

opened 2026-10-26 21:21:10 +00:00 by bsakaguchi · 4 comments

bsakaguchi commented

2026-10-26 21:21:10 +00:00

Owner

Originally created by @macdevign on GitHub (Mar 6, 2025).
Original GitHub issue: https://github.com/deepseek-ai/DeepSeek-R1/issues/539

Please hide the reasoning feedback after the response generated as it take up a lot of space. People generally are more interested in the answer than the how the reason arrive at its answer. If people interested, they can expand the feedback.

That's exactly how ChatGPT works too.

Example: Why this still appearing when response fully generated?

Originally created by @macdevign on GitHub (Mar 6, 2025). Original GitHub issue: https://github.com/deepseek-ai/DeepSeek-R1/issues/539 Please hide the reasoning feedback after the response generated as it take up a lot of space. People generally are more interested in the answer than the how the reason arrive at its answer. If people interested, they can expand the feedback. That's exactly how ChatGPT works too. ________________________________________ Example: Why this still appearing when response fully generated? ![Image](https://github.com/user-attachments/assets/bae518cd-7ecf-482f-9c28-c5e31f17a90b)

bsakaguchi

2026-10-26 21:21:10 +00:00

closed this issue
added the
stale

closed-as-stale
labels

bsakaguchi commented

2026-10-26 21:21:11 +00:00

Author

Owner

@zshuangyan commented on GitHub (Mar 7, 2025):

On the contrary, I believe that the process of thinking can also provide significant enlightenment, sometimes even greater than the value of the answer itself.

@zshuangyan commented on GitHub (Mar 7, 2025): On the contrary, I believe that the process of thinking can also provide significant enlightenment, sometimes even greater than the value of the answer itself.

bsakaguchi commented

2026-10-26 21:21:11 +00:00

Author

Owner

@macdevign commented on GitHub (Mar 7, 2025):

By all means , show it during generation of response, which I find it useful, but when the response is fully generated, collapse the feedback, and if user want to view it, can always expand it as needed. This behaviour is better because the feedback ocuppies space and cause more scrolling to view other response. Sure, the user can collapse it manually after the response, but why the extra step.

Look at how effective ChatGPT does it.

@macdevign commented on GitHub (Mar 7, 2025): By all means , show it during generation of response, which I find it useful, but when the response is fully generated, collapse the feedback, and if user want to view it, can always expand it as needed. This behaviour is better because the feedback ocuppies space and cause more scrolling to view other response. Sure, the user can collapse it manually after the response, but why the extra step. Look at how effective ChatGPT does it.

bsakaguchi commented

2026-10-26 21:21:12 +00:00

Author

Owner

@github-actions[bot] commented on GitHub (Apr 17, 2025):

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. If you believe this issue is still relevant, please leave a comment to keep it open. Thank you for your contributions!

@github-actions[bot] commented on GitHub (Apr 17, 2025): This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. If you believe this issue is still relevant, please leave a comment to keep it open. Thank you for your contributions!

bsakaguchi commented

2026-10-26 21:21:12 +00:00

Author

Owner

@github-actions[bot] commented on GitHub (May 20, 2025):

false

@github-actions[bot] commented on GitHub (May 20, 2025): false