claude-code - 💡(How to fix) Fix [FEATURE] Allow users to manually dismiss "Needs input" state in Claude Code Desktop

Preflight Checklist

• I have searched existing requests and this feature hasn't been requested yet
• This is a single feature request (not multiple features)

Problem Statement

In Claude Code Desktop, some sessions remain in a “Needs input” state even when I no longer intend to continue that interaction.

This becomes a problem when working across multiple sessions. The yellow “Needs input” indicator is useful when it means a session actually needs my attention, but it becomes noisy when old or intentionally abandoned sessions stay marked that way.

Right now, if I decide I do not want to respond to a session anymore, I still appear to have no clean way to clear that state. Sending a message just to end the interaction adds unnecessary noise to the conversation and may consume tokens. Deleting the conversation is also not ideal, because I may still want to keep the history for later reference.

The problem is not that Claude is asking for input. That part is fine. The problem is that the user has no way to say: “I’m done with this request; stop marking this session as needing my attention.”

Proposed Solution

Please add a manual action in Claude Code Desktop to dismiss or clear the “Needs input” state for a session.

Ideally, this would be available from the session list, for example as a right-click / overflow menu action:

• “Dismiss needs input”
• “Clear attention state”
• “Mark as idle”

Using this action should not send a message to Claude, should not modify the transcript, and should not delete or archive the session. It should only clear the UI attention state so the session no longer shows as needing input.

The session should remain available and resumable later. If the user opens it again and sends another message, the session can continue normally.

Alternative Solutions

I have tried the current available options, but none of them solve this cleanly:

• Sending a final message such as “never mind” or “stop” works around the state, but it adds unnecessary content to the transcript and may consume tokens.
• Clearing the conversation/session context is too destructive for this use case and does not necessarily address the UI state I want to dismiss.
• Deleting the session removes history that I may want to keep.
• Archiving can hide the session, but it is not the same as explicitly saying “this no longer needs my attention.”
• Leaving the yellow indicator there makes the session list noisy and reduces the usefulness of the indicator.

What I want is a non-destructive, local/UI-level dismissal action.

Priority

Medium - Would be very helpful

Feature Category

Interactive mode (TUI)

Use Case Example

Example scenario:

1. I ask Claude Code to investigate or modify something in a project.
2. Claude asks a follow-up question or waits for input.
3. After looking at the situation, I decide I do not want to continue that thread anymore.
4. I still want to keep the session history because it may contain useful context or commands.
5. I do not want to send a meaningless reply just to clear the state.
6. I right-click the session in Claude Code Desktop and choose “Dismiss needs input.”
7. The session remains in my history, but the yellow “Needs input” indicator disappears.

This would make the session list much easier to use, especially when working with several projects or experiments at the same time.

Additional Context

This is specifically about Claude Code Desktop session management.

A “Needs input” indicator is only useful if it represents something the user still intends to act on. When old sessions cannot be dismissed without replying, deleting, or archiving, the indicator becomes less actionable over time.

This feature should be local and non-destructive:

• no message sent to Claude
• no token usage
• no transcript changes
• no session deletion
• no archive required

It would simply let the user clear the attention state for a session they have intentionally decided not to continue.