nhcarrigan/hikari-desktop
9
0
Fork 0
generated from nhcarrigan/template
Code Issues 9 Pull Requests 36 Actions Releases 22 Activity

feat: handle idle-return prompt after 75+ minutes of inactivity (v2.1.84) #255

New Issue
Closed
opened 2026-04-13 09:11:36 -07:00 by hikari · 1 comment
hikari commented 2026-04-13 09:11:36 -07:00
Owner
Copy Link
Copy Source

Context

Claude Code v2.1.84 added an idle-return prompt that fires after 75+ minutes of session inactivity. This appears as an interactive prompt in the CLI asking the user to confirm they want to continue.

In --output-format stream-json mode (which we use), this likely surfaces as either:

  • A system message with a specific subtype
  • A user prompt request requiring input
  • A special elicitation-style event

The exact stream-json representation needs investigation.

Why This Matters

If unhandled, this idle prompt could cause the session to stall silently in Hikari Desktop — the user may not realise Claude Code is waiting for confirmation, and the character would be stuck in an active state indefinitely.

Ideally we should:

  1. Detect the idle-return prompt in the stream
  2. Surface it to the user in the UI (e.g. a notification or inline prompt)
  3. Possibly trigger the Permission character state (confused shrug) since user input is required

Tasks

  • Investigate what the idle-return prompt looks like in stream-json output (run a long session to observe)
  • Add the appropriate type variant in src-tauri/src/types.rs if it's a new message type
  • Handle it in src-tauri/src/wsl_bridge.rs — surface to UI and/or trigger Permission state
  • Consider adding a UI notification for sessions idle > 75 minutes
  • Add tests once the event format is confirmed

References

  • Claude Code v2.1.84 changelog
  • src-tauri/src/types.rs
  • src-tauri/src/wsl_bridge.rs
  • Existing ElicitationEvent handling (similar pattern)

✨ This issue was created with help from Hikari~ 🌸

## Context Claude Code v2.1.84 added an **idle-return prompt** that fires after 75+ minutes of session inactivity. This appears as an interactive prompt in the CLI asking the user to confirm they want to continue. In `--output-format stream-json` mode (which we use), this likely surfaces as either: - A `system` message with a specific subtype - A `user` prompt request requiring input - A special elicitation-style event The exact stream-json representation needs investigation. ## Why This Matters If unhandled, this idle prompt could cause the session to stall silently in Hikari Desktop — the user may not realise Claude Code is waiting for confirmation, and the character would be stuck in an active state indefinitely. Ideally we should: 1. Detect the idle-return prompt in the stream 2. Surface it to the user in the UI (e.g. a notification or inline prompt) 3. Possibly trigger the `Permission` character state (confused shrug) since user input is required ## Tasks - [ ] Investigate what the idle-return prompt looks like in stream-json output (run a long session to observe) - [ ] Add the appropriate type variant in `src-tauri/src/types.rs` if it's a new message type - [ ] Handle it in `src-tauri/src/wsl_bridge.rs` — surface to UI and/or trigger `Permission` state - [ ] Consider adding a UI notification for sessions idle > 75 minutes - [ ] Add tests once the event format is confirmed ## References - Claude Code v2.1.84 changelog - `src-tauri/src/types.rs` - `src-tauri/src/wsl_bridge.rs` - Existing `ElicitationEvent` handling (similar pattern) ✨ This issue was created with help from Hikari~ 🌸
hikari commented 2026-04-13 09:59:11 -07:00
Author
Owner
Copy Link
Copy Source

Investigation Results

After digging into the installed Claude Code CLI source (cli.js), the idle-return prompt after 75+ minutes appears to be a TUI-only feature — it uses the terminal's interactive prompt system, not the hook/stream-json pipeline.

When running in --output-format stream-json mode (which is how Hikari Desktop communicates with Claude Code), interactive TUI prompts are suppressed entirely. There is no corresponding hook event type (no [IdleReturn Hook] or similar), and no stream-json message type for this event.

Conclusion

No action required for Hikari Desktop. The idle-return prompt does not surface in our communication channel.

If this assumption ever proves incorrect (e.g. a future CLI version adds an IdleReturn hook), we can revisit. Closing as won't fix / not applicable.

✨ This comment was added by Hikari~ 🌸

## Investigation Results After digging into the installed Claude Code CLI source (`cli.js`), the idle-return prompt after 75+ minutes appears to be a **TUI-only feature** — it uses the terminal's interactive prompt system, not the hook/stream-json pipeline. When running in `--output-format stream-json` mode (which is how Hikari Desktop communicates with Claude Code), interactive TUI prompts are suppressed entirely. There is no corresponding hook event type (no `[IdleReturn Hook]` or similar), and no stream-json message type for this event. ## Conclusion **No action required for Hikari Desktop.** The idle-return prompt does not surface in our communication channel. If this assumption ever proves incorrect (e.g. a future CLI version adds an `IdleReturn` hook), we can revisit. Closing as won't fix / not applicable. ✨ This comment was added by Hikari~ 🌸
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
aspect
code
Concerns the software code in the repository
aspect
dx
Concerns developers' experience with the codebase
aspect
interface
Concerns end-users' experience with the software
aspect
text
Concerns the documentation material in the repository
contribute
good first issue
A great opportunity for a team member to learn a new codebase
contribute
help wanted
Open for anyone on our team to grab.
contribute
staff only
Restricted to our executive leadership.
goal
addition
Addition of new feature
goal
fix
Bug fix
goal
improvement
Improvement to an existing feature
points
1
Very simple issue requiring minimal effort and complexity.
points
13
Extremely complex issue representing major undertakings. Should be broken down into smaller pieces.
points
2
Simple issue that requires a bit more thought or investigation.
points
3
Moderate complexity issue requiring more substantial work.
points
5
Complex issue requiring significant effort and expertise.
points
8
Very complex issue requiring extensive work and deep expertise.
priority
critical
1
Must be fixed ASAP
priority
high
2
Stalls work on the project or its dependents
priority
low
4
Low priority and doesn't need to be rushed
priority
medium
3
Not blocking but should be fixed soon
priority
none
5
No priority, should only be performed when a developer is available
status
awaiting triage
Has not been triaged & therefore, not ready for work
status
blocked
Blocked and therefore not ready for work
status
discarded
Will not be worked on
status
discontinued
Not suitable for work as repo is in maintenance
status
label work required
Needs proper labelling before it can be worked on
status
ready for dev
Ready for work
status
ticket work required
Needs more details before it can be worked on
talk
discussion
Open for discussions and feedback
talk
question
Can be resolved with an answer
time
1 day
Approximately one full day of development work.
time
1-2 weeks
One to two weeks of focused development effort.
time
2-3 days
Two to three days of development effort.
time
4-5 days
Approximately one week of development work.
time
<1 day
Less than one day of focused work. Quick fixes or simple tasks.
time
>2 weeks
More than two weeks of development work. Must be broken down into smaller pieces.
No Label
Milestone
No items
No Milestone
Assignees
Clear assignees
gurkirat hanna (Hanna Rose) hikari (Hikari) minori (Minori) naomi (Naomi Carrigan) rain teklu tim
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: nhcarrigan/hikari-desktop#255
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?