[FEATURE] New state marker to reflect Claude session state (idle vs input required)

Resolved 💬 4 comments Opened Mar 18, 2026 by cperalt Closed Apr 16, 2026

Preflight Checklist

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

Problem Statement

Claude Code currently exposes two session states to integrations:

  • Working — actively processing
  • Waiting — session is open but not processing

The "waiting" state conflates two meaningfully different situations:

  1. Idle — Claude finished its task. No action needed, user can check back later.
  2. Input required — Claude is mid-task but blocked on a required user response

(tool permission approval, clarifying question, yes/no prompt). User needs to
act now to unblock it.

Proposed Solution

Expose a third distinct state — something like input_required or awaiting_input
— for when Claude is actively waiting on a specific user response, separate from
the general idle/waiting state.

Alternative Solutions

_No response_

Priority

Low - Nice to have

Feature Category

Interactive mode (TUI)

Use Case Example

Integrations and tooling that surface Claude session state (e.g. terminal multiplexers,
worktree managers, status bars) can use this to signal when a session needs immediate
attention vs when it is simply idle between tasks. This is especially valuable when
running multiple parallel Claude sessions.

Additional Context

_No response_

View original on GitHub ↗

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