[FEATURE] 02-FEATURE-REQUEST-ux-improvements Session state persistence

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

Feature Requests: UX Improvements

Submitted: 2024-11-12
Reporter: Bruce (@energyscholar)
Category: User Experience
Priority: Medium-High

---

1. File Upload Progress Indicator

Problem:
When uploading files (images, PDFs, archives), no visual feedback indicates:

• Upload in progress
• Upload completion
• Upload failure
• File size/transfer rate

User Impact:

• Uncertainty whether upload succeeded
• Repeated upload attempts (wasting bandwidth/time)
• Poor UX for large files on slow connections
• No way to know if upload stalled

Proposed Solution:

Display upload progress in chat interface:

⬆ Uploading: high-guard-page-14.png ████████░░░░ 67% (3.4 MB / 5.1 MB) 2.1 MB/s

On completion:

✓ Uploaded: high-guard-page-14.png (5.1 MB)

On failure:

✗ Upload failed: connection_timeout (retry?)

Implementation Notes:

• Show progress for files >1MB or uploads >2sec
• Display: filename, progress bar, percentage, size, transfer rate
• Allow cancellation for large uploads
• Persist indicator during Claude's processing time

Priority Justification:
File upload is a core interaction pattern. Progress indicators are standard UX (browsers, OSes, apps). Absence creates friction and uncertainty.

---

2. Session State Persistence / Recovery

Problem:
Session crashes or network failures result in total context loss with no recovery mechanism.

User Impact:

• Lost work after hours-long sessions
• No way to resume interrupted conversations
• Fear of session instability reduces trust
• Related to crash bug (see separate report)

Proposed Solution:

Minimal Implementation:

• Autosave session state to browser localStorage every N messages
• On tab reload/crash, offer: "Resume previous session?"
• Restore conversation history + working directory context

Enhanced Implementation:

• Cloud-backed session persistence (optional, user control)
• "Save session checkpoint" manual command
• Export/import session JSON for backup
• Session branching (fork conversation at any point)

Use Cases:

1. Crash recovery - Resume after unrecoverable errors
2. Intentional refresh - Reload browser without losing context
3. Session migration - Continue work on different device
4. Backup - Save important sessions before risky operations

Technical Considerations:

• Privacy: local-first, opt-in cloud sync
• Size limits: compress/summarize old messages
• Security: sanitize before export (no credentials)

Priority Justification:
High-value sessions (complex debugging, long implementations) are vulnerable to catastrophic loss. Session recovery is standard in IDEs (VSCode, IntelliJ), terminals (tmux), and even browser tabs.

---

Additional Context

Reporter Background:

• 51 years CLI experience (DEC-10, ARPAnet 1975)
• Professional developer (Traveller Combat VTT, QRR research)
• Power user expectations: terminal-grade reliability

Related Issues:

• Crash bug report (multiple large posts)
• Scroll issue (fullscreen mode)

Both issues reflect need for production-grade session management and state persistence.

---

Submission

Submit to: https://github.com/anthropics/claude-code/issues

Contact: @energyscholar on GitHub
File: /home/bruce/software/bug_reports_claude/02-FEATURE-REQUEST-ux-improvements.md

Proposed Solution

See report

Alternative Solutions

_No response_

Priority

Low - Nice to have

Feature Category

CLI commands and flags

Use Case Example

_No response_

Additional Context

Also uploading report as a file. Duplicate of first field.

02-FEATURE-REQUEST-ux-improvements.md