Skip to content

RESUME_PROMPT.md

Latest commit

 

History

History
180 lines (119 loc) · 5.35 KB

RESUME_PROMPT.md

File metadata and controls

180 lines (119 loc) · 5.35 KB

Resume & Terminal Configuration

Resume Actions

When viewing a session in ccrider tui, you have multiple ways to resume:

  • r - Resume - Quit ccrider and launch Claude in the same terminal
  • f - Fork - Same as resume but creates a new session ID
  • o - Open in New Terminal - Launch Claude in a new terminal window (keeps ccrider open)
  • c - Copy Command - Copy the resume command to clipboard

Resume Prompt Customization

When you resume a session (via r, f, or o), ccrider sends a contextual prompt to Claude Code to help set the right context.

How It Works

  1. ccrider resumes from the original project directory - This is where Claude Code stores session files (in ~/.claude/projects/)
  2. A prompt is sent to Claude telling it:
    • Where you were actually working (last working directory from the session)
    • How long the session has been inactive
    • To check the current state before proceeding

This solves the problem of sessions that moved between directories (like git worktrees) - Claude can find the session files AND knows where to navigate.

Default Prompt Template

The default template is:

Resuming session from {{last_updated}}.{{#different_directory}} Started in your last working directory: {{last_cwd}}{{/different_directory}}

IMPORTANT: This session has been inactive for {{time_since}}. Before proceeding: check git status, look around to understand what changed, and be careful not to overwrite any work in progress.

Note: ccrider automatically starts Claude in the correct directory (preferring last_cwd over project_path), so the template doesn't need to tell Claude to navigate - it's already there!

Available Variables

You can use these variables in your custom template:

  • {{last_updated}} - Exact timestamp when session was last active (e.g., "2025-11-08T22:29:11.424Z")
  • {{last_cwd}} - Last working directory from the session (e.g., "/Users/you/project/.worktrees/feature")
  • {{time_since}} - Human-readable time ago (e.g., "6 hours ago", "2 days ago")
  • {{project_path}} - Original project directory where session started (e.g., "/Users/you/project")
  • {{#same_directory}}...{{/same_directory}} - Conditional: renders only if last_cwd == project_path
  • {{#different_directory}}...{{/different_directory}} - Conditional: renders only if last_cwd != project_path

Customizing the Prompt

Create a custom template file at ~/.config/ccrider/resume_prompt.txt:

mkdir -p ~/.config/ccrider
cat > ~/.config/ccrider/resume_prompt.txt << 'EOF'
Session resumed! Last active: {{time_since}}

You were in: {{last_cwd}}

Quick context refresh:
- Run git status and git log
- Check for uncommitted changes
- Look for any WIP or TODO comments

Let's pick up where we left off.
EOF

The template uses Mustache syntax ({{variable}}). ccrider will automatically load your custom template instead of the default.

Testing Your Template

Use the debug-prompt command to see what prompt will be generated for a session:

ccrider debug-prompt <session-id>

This shows:

  • The session info (paths, timestamps)
  • The template variables and their values
  • The final rendered prompt
  • The exact command that will be run

Examples

Minimal prompt:

Back in session from {{time_since}} ago.{{#different_directory}} You were in {{last_cwd}}{{/different_directory}}

Using conditionals for context:

Resuming from {{time_since}}.
{{#different_directory}}
Note: Started in {{last_cwd}} (you were working in a different directory than the project root).
{{/different_directory}}

Check git status before continuing.

Detailed prompt with checklist:

Resuming session: {{last_cwd}}
Last active: {{last_updated}} ({{time_since}})

Before continuing:
1. git status - check for uncommitted changes
2. git log -5 - review recent commits
3. ls - verify current directory state
4. Look for .md files with session notes

Context set. Ready to continue.

Worktree-aware prompt:

Session active {{time_since}}.

Original: {{project_path}}
Last dir: {{last_cwd}}

If this is a worktree: check git branch and verify you're on the right branch before making changes.

Terminal Spawn Customization

The o key opens a session in a new terminal window. ccrider auto-detects your terminal and uses the appropriate method.

Supported Terminals (Auto-Detected)

  • Ghostty - Uses ghostty +new-window (native IPC)
  • iTerm2 - Uses AppleScript
  • Terminal.app - Uses AppleScript
  • WezTerm - Uses wezterm cli spawn
  • Kitty - Uses kitty @ launch

Detection is based on the $TERM_PROGRAM environment variable.

Custom Terminal Command

If auto-detection doesn't work or you want to use a different method, create:

~/.config/ccrider/terminal_command.txt

Template variables:

  • {cwd} - Working directory (project path)
  • {command} - Full command to execute (includes claude --resume ... with prompt)

Example for Alacritty:

alacritty --working-directory {cwd} -e bash -l -c {command}

Example for custom Ghostty config:

ghostty +new-window --working-directory={cwd} --config=my-config -e {command}

Example for tmux (spawn new window in existing session):

tmux new-window -c {cwd} {command}

The custom command is run via bash -c, so you can use shell features like pipes, redirects, etc.