[Bug] Status line disappears during "accept edits?" prompt
Resolved 💬 4 comments Opened Jan 22, 2026 by vyasgiridhar Closed Jan 25, 2026
Bug Description
Issue: Status line disappears during "accept edits" prompt
Current behavior:
- Custom status line (configured via statusLine.command in settings.json) displays correctly during normal operation
- When Claude Code shows the "accept edits?" prompt, the status line disappears
- Status line only reappears after the next API call completes
Expected behavior:
Status line should either:
- Persist above the prompt (recommended)
- Be redrawn after prompt is dismissed
- Be refreshed on every terminal re-render
Configuration:
"statusLine": {
"type": "command",
"command": "~/.claude/statusline.sh"
}
Workaround:
None available - CLI controls when statusline command is invoked
Impact:
User loses visibility into context usage, cost, and session stats during interactive prompts
Environment Info
- Platform: darwin
- Terminal: iTerm.app
- Version: 2.1.2
- Feedback ID: 69570342-8382-4f50-a170-a71b51b00e55
Errors
[{"error":"Error: Request was aborted.\n at _createMessage (/$bunfs/root/claude:446:3157)\n at processTicksAndRejections (native:7:39)","timestamp":"2026-01-22T05:29:16.615Z"},{"error":"Error: Request was aborted.\n at makeRequest (/$bunfs/root/claude:871:3940)\n at processTicksAndRejections (native:7:39)","timestamp":"2026-01-22T05:30:23.210Z"},{"error":"Error: Request was aborted.\n at makeRequest (/$bunfs/root/claude:871:3940)\n at processTicksAndRejections (native:7:39)","timestamp":"2026-01-22T05:48:15.479Z"},{"error":"Error: Request was aborted.\n at makeRequest (/$bunfs/root/claude:871:3940)\n at processTicksAndRejections (native:7:39)","timestamp":"2026-01-22T06:21:09.755Z"},{"error":"Error: Request was aborted.\n at makeRequest (/$bunfs/root/claude:871:3940)\n at processTicksAndRejections (native:7:39)","timestamp":"2026-01-22T06:27:12.846Z"},{"error":"Error: Request was aborted.\n at makeRequest (/$bunfs/root/claude:871:3940)\n at processTicksAndRejections (native:7:39)","timestamp":"2026-01-22T06:29:12.857Z"},{"error":"Error: Request was aborted.\n at makeRequest (/$bunfs/root/claude:871:3940)\n at processTicksAndRejections (native:7:39)","timestamp":"2026-01-22T06:35:22.552Z"},{"error":"Error: Request was aborted.\n at makeRequest (/$bunfs/root/claude:871:3940)\n at processTicksAndRejections (native:7:39)","timestamp":"2026-01-22T06:53:56.747Z"},{"error":"Error: EISDIR: illegal operation on a directory, read\n at readSync (unknown)\n at <anonymous> (/$bunfs/root/claude:12:783)\n at z2 (/$bunfs/root/claude:11:34141)\n at readSync (/$bunfs/root/claude:12:661)\n at ph (/$bunfs/root/claude:4745:113)\n at d5 (/$bunfs/root/claude:4747:206)\n at Tl7 (/$bunfs/root/claude:2637:6826)\n at Tl7 (/$bunfs/root/claude:2637:7712)\n at J (/$bunfs/root/claude:2637:6031)\n at J (/$bunfs/root/claude:2637:6327)","timestamp":"2026-01-22T07:00:29.173Z"},{"error":"Error: EISDIR: illegal operation on a directory, read\n at readFileSync (unknown)\n at <anonymous> (/$bunfs/root/claude:12:528)\n at z2 (/$bunfs/root/claude:11:34141)\n at readFileSync (/$bunfs/root/claude:12:487)\n at d5 (/$bunfs/root/claude:4747:231)\n at Tl7 (/$bunfs/root/claude:2637:6826)\n at Tl7 (/$bunfs/root/claude:2637:7712)\n at J (/$bunfs/root/claude:2637:6031)\n at J (/$bunfs/root/claude:2637:6327)\n at <anonymous> (/$bunfs/root/claude:2637:6360)","timestamp":"2026-01-22T07:00:29.174Z"}]This issue has 4 comments on GitHub. Read the full discussion on GitHub ↗