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

feat: detect and handle "Prompt is too long" errors from Claude CLI #158

New Issue
Closed
opened 2026-02-24 15:08:55 -08:00 by hikari · 0 comments
hikari commented 2026-02-24 15:08:55 -08:00
Owner
Copy Link
Copy Source

Overview

When the conversation history grows too large, the Claude CLI returns a "Prompt is too long" error. Currently this is displayed as a plain assistant message in the terminal, which is confusing — it looks like a normal response rather than an actionable error.

Current Behaviour

The error appears as a white assistant text block with no prefix:

02:58 PM   Prompt is too long

Expected Behaviour

  • The message should be displayed as an error line type (red, with [error] prefix) so it stands out clearly
  • A "Compact Conversation" button should appear in the terminal when this error is detected, allowing the user to trigger claude --compact (or equivalent) to summarise and truncate the history so the session can continue without starting over

Proposed Implementation

Detection

In wsl_bridge.rs → process_json_line, when processing ClaudeMessage::Assistant content blocks with ContentBlock::Text, check if the text is exactly (or starts with) "Prompt is too long". If so, emit the line with line_type: "error" instead of "assistant", and additionally emit a special line_type: "compact-prompt" event.

Alternatively, the Claude CLI may emit this as a result message with a specific subtype — worth investigating in the binary.

UI

When the compact-prompt line type is received, the terminal should render an inline action button:

[error] Prompt is too long
[action] ⚡ Compact Conversation   ← clickable button

Clicking the button sends a /compact command (or the equivalent CLI flag) to the active session, which summarises the conversation history and allows the user to continue.

Notes

  • Related to context window management
  • The compact action should be non-destructive — it summarises rather than deletes history

✨ This issue was created with help from Hikari~ 🌸

## Overview When the conversation history grows too large, the Claude CLI returns a `"Prompt is too long"` error. Currently this is displayed as a plain assistant message in the terminal, which is confusing — it looks like a normal response rather than an actionable error. ## Current Behaviour The error appears as a white assistant text block with no prefix: ``` 02:58 PM Prompt is too long ``` ## Expected Behaviour - The message should be displayed as an `error` line type (red, with `[error]` prefix) so it stands out clearly - A **"Compact Conversation"** button should appear in the terminal when this error is detected, allowing the user to trigger `claude --compact` (or equivalent) to summarise and truncate the history so the session can continue without starting over ## Proposed Implementation ### Detection In `wsl_bridge.rs` → `process_json_line`, when processing `ClaudeMessage::Assistant` content blocks with `ContentBlock::Text`, check if the text is exactly (or starts with) `"Prompt is too long"`. If so, emit the line with `line_type: "error"` instead of `"assistant"`, and additionally emit a special `line_type: "compact-prompt"` event. Alternatively, the Claude CLI may emit this as a `result` message with a specific `subtype` — worth investigating in the binary. ### UI When the `compact-prompt` line type is received, the terminal should render an inline action button: ``` [error] Prompt is too long [action] ⚡ Compact Conversation ← clickable button ``` Clicking the button sends a `/compact` command (or the equivalent CLI flag) to the active session, which summarises the conversation history and allows the user to continue. ## Notes - Related to context window management - The compact action should be non-destructive — it summarises rather than deletes history ✨ This issue was created with help from Hikari~ 🌸
naomi closed this issue 2026-02-24 20:48:51 -08:00
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#158
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?