Skip to content
PlanDrop

Session Continuity

Session continuity lets Claude Code remember your previous tasks within a project. Instead of starting fresh each time, you can build on previous work.

How It Works

When you complete a task, PlanDrop offers two options:

  • Continue in Session — Send another task in the same conversation
  • New Task — Start a fresh conversation

Choosing “Continue in Session” means Claude Code retains context from all previous tasks in that session.

Example Workflow

Task 1:

Create a Python script that loads data from sales.csv
and calculates monthly totals.

Claude creates analyze_sales.py. After execution…

Task 2 (Continue in Session):

Add a bar chart visualization and save as monthly_chart.png

Claude remembers analyze_sales.py and adds plotting code to it.

Task 3 (Continue in Session):

The chart looks good but the y-axis labels are overlapping.
Fix the formatting.

Claude remembers both the data loading and the chart code, and fixes the specific issue.

Benefits

Less Re-explanation

Without session continuity, you’d need to re-explain the entire context:

# Without continuity (verbose)
"In analyze_sales.py which loads data from sales.csv
and calculates monthly totals, and then creates a bar chart
saved as monthly_chart.png, fix the y-axis label overlap..."

With continuity:

# With continuity (concise)
"Fix the y-axis label overlap."

Iterative Development

Sessions are perfect for:

  • Debugging step by step
  • Refining analysis parameters
  • Adding features incrementally
  • Exploring different approaches

Context for Errors

When something fails, Claude knows:

  • What code it wrote
  • What you asked for
  • What’s been tried before

Managing Sessions

Viewing Session Info

The session ID is shown at the bottom of the Claude Code tab. Click “Reset” to start a new session.

Session History

Sessions are tracked in .plandrop/session_history.jsonl. Each entry contains:

  • Session ID
  • Start/end timestamps

Exporting Session Work

Use the gear menu → “Export History” to download a complete record of your session as markdown.

Session Limits

Sessions persist until:

  • You click “Reset”
  • You switch projects
  • The watcher restarts
  • Context limit is reached

Best Practices

  1. Group related work — Keep database queries in one session, UI work in another
  2. Reset when switching topics — Fresh context helps avoid confusion
  3. Use for debugging — Each error + fix builds understanding
  4. Export before reset — Save the history if you might need it later

Next Steps