Expose session history to Claude at start of new sessions

Resolved 💬 3 comments Opened Jan 29, 2026 by clashleyca Closed Feb 1, 2026

Problem

When a user accidentally closes their terminal or starts a new session the next day, Claude has no context about what was being worked on previously. This leads to users spending time trying to remember and re-explain what they were doing.

Observation

Command history is already persisted (users can up-arrow to see previous prompts), so the data exists - it's just not exposed to Claude when a new session starts.

Suggestion

At the start of a new session, provide Claude with recent command history (or at least a summary) so it can offer continuity. Something like:

  • Show the last N user prompts from the previous session
  • Optionally include timestamps
  • Could be opt-in via a flag for privacy-conscious users

This would help with the common scenario: "I closed the terminal mid-refactor, came back the next day, and couldn't remember what I asked Claude to do."

Complexity

Seems low - the history is already stored, just needs to be read and included in context.

View original on GitHub ↗

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