Use Case
After finding a session via ccvault search or ccvault tui, the natural next step is often to resume that session in Claude Code. Currently this requires manually copying the session ID and running claude --resume <session-id> separately.
Proposal
Add a resume command and integrate it into the TUI:
CLI:
ccvault resume <session-id>
Equivalent to running claude --resume <session-id> — just a convenience wrapper that passes the session ID through.
TUI:
Add a keybinding (e.g. r) in the session detail view to resume the selected session directly.
Why this fits ccvault
ccvault already handles the hard part: finding the right session. The resume step is the obvious completion of that workflow. Since claude --resume already exists, the implementation would be straightforward — essentially an exec call.
Use Case
After finding a session via
ccvault searchorccvault tui, the natural next step is often to resume that session in Claude Code. Currently this requires manually copying the session ID and runningclaude --resume <session-id>separately.Proposal
Add a
resumecommand and integrate it into the TUI:CLI:
Equivalent to running
claude --resume <session-id>— just a convenience wrapper that passes the session ID through.TUI:
Add a keybinding (e.g.
r) in the session detail view to resume the selected session directly.Why this fits ccvault
ccvault already handles the hard part: finding the right session. The resume step is the obvious completion of that workflow. Since
claude --resumealready exists, the implementation would be straightforward — essentially anexeccall.