← backOps & AutomationFounding · Free forever

Save a long Claude session to a file before context limits hit

Do this before you hit the context limit. Starting a fresh session with this file loaded = picking up exactly where you left off.

by @whitney · recommended tool Claude · 0 unlocks

You'll need

CONNECTORS

Google Drive

EXAMPLES · WHAT THIS PROMPT PRODUCES

Sample output

# Session Save — Q3 Brand Relaunch Working Doc

## Goal
Define positioning + name a new sub-brand for our enterprise tier, and produce launch headlines, ready to resume in a fresh session.

## Key decisions
- Sub-brand targets IT directors at 500+ employee companies (not SMB).
- Positioning frame: "security-first automation," not "fast automation" — differentiates from Zapier/Make.
- Tone: confident, technical-credible, zero hype words ("unlock," "game-changer" banned).
- Name shortlist narrowed to 3: **Bastion**, **Ironclad Flow**, **Sentry**.

## Artifacts produced
- Positioning statement (40w) + 3 alternates — see below.
- 8 launch headlines; top pick: "Automation your security team signs off on."
- 5 name candidates with domain notes (bastion.io taken; trybastion.com open).

## Open threads / next steps
1. Trademark-check the 3 finalist names (not yet done — Claude flagged it can't verify availability).
2. Draft the landing page hero once name is locked.
3. Decide: keep parent brand visible ("Bastion by Acme") or standalone?

Format ready to re-upload — start the next session with: "Load this doc, we're picking the final name and writing the hero."

PRICE HISTORY0 cr · current

PROMPT TEMPLATE · v1.0.0

Save everything we just talked about as a structured file.
Include:
- The goal we set
- Key decisions we made
- Artifacts we produced (headlines, prompts, outlines)
- Open threads + next steps
Format: markdown, ready to upload back into a fresh session.