claude-code - 💡(How to fix) Fix Add `/resume -` shortcut to return to previous session [1 participants]

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…
GitHub stats
anthropics/claude-code#46874Fetched 2026-04-12 13:30:47
View on GitHub
Comments
0
Participants
1
Timeline
3
Reactions
0
Author
Participants
Timeline (top)
labeled ×3

This is a small ergonomic improvement that would make /fork significantly more useful for exploratory workflows where you frequently branch and return.

Root Cause

This is a small ergonomic improvement that would make /fork significantly more useful for exploratory workflows where you frequently branch and return.

RAW_BUFFERClick to expand / collapse

Feature Request

After using /fork to branch a conversation, there's no quick way to return to the original/parent session. You have to manually track and type the full session ID.

Proposal

Add a /resume - shortcut (analogous to cd - or git checkout -) that resumes the most recent previous session. This would make the fork/resume workflow much more fluid:

  1. /fork → work on a tangent
  2. /resume - → back to the original conversation

Alternatives considered

  • /resume .. (parent notation) — but - is more familiar from shell conventions and works even when the previous session wasn't a parent (e.g., you just switched between two unrelated sessions)

Context

This is a small ergonomic improvement that would make /fork significantly more useful for exploratory workflows where you frequently branch and return.

extent analysis

TL;DR

Implementing a /resume - shortcut to resume the most recent previous session would likely address the issue.

Guidance

  • Consider adding a session history stack to store previous session IDs, allowing users to easily switch between them.
  • Consider implementing a "most recently used" (MRU) list to keep track of previous sessions and allow users to resume them using the /resume - shortcut.
  • Evaluate the feasibility of integrating this feature with existing session management functionality to ensure a seamless user experience.
  • Assess the potential impact on existing workflows and consider adding options for customizing the behavior of the /resume - shortcut.

Example

// Pseudocode example of a session history stack
sessionHistory = []
function forkSession() {
  // Store current session ID in history stack
  sessionHistory.push(currentSessionId)
  // Create new session
}
function resumeSession() {
  // Check if session history is not empty
  if (sessionHistory.length > 0) {
    // Resume previous session
    currentSessionId = sessionHistory.pop()
  }
}

Notes

The implementation details may vary depending on the underlying architecture and technology stack of the application.

Recommendation

Apply workaround: Implement the proposed /resume - shortcut to provide a quick way to return to the original/parent session, as it aligns with familiar shell conventions and enhances the usability of the /fork feature.

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING