← All terms

define session --plain-english

Illustration for "Session" — Day 13 of the Non-Technical Technical Dictionary

Session

TLDR:One continuous conversation with your AI.

I used to treat one chat like my one shot. Same conversation for days, the whole project crammed into a single thread, because starting over felt like throwing away progress. It wasn't progress. It was clutter I refused to put down.

Think of a session like a work shift. Everything that happens between clocking in and clocking out lives in that one shift. The next person who shows up knows nothing about it, unless somebody wrote it down and handed it over. That's a session with AI. Your first message, every reply, the files you dropped, the tangents, all of it lives inside that one stretch. Close the chat, open a new one, and a fresh worker walks in with a blank clipboard. (It's all happening inside one context window, that room the AI thinks in.)

Here's the part that matters: the slate wipes every time. That sounds like a bug. It's the feature.

When a long chat gets confused, loops, or goes sluggish, your instinct is to push harder. Re-explain. Argue. Correct it again. Don't. You're not broken and neither is the AI. The shift is just buried in three hours of noise, and a new shift starts clean.

The move takes thirty seconds:

  1. Notice the chat going dumb (forgetting, looping, contradicting itself).

  2. Ask it for a quick handoff note: where we are, what's decided, what's next.

  3. Open a fresh session and paste that note in.

You keep the gold, leave the trash. The new worker clocks in already knowing what matters, reading a clean page instead of digging through the mess. (Handoffs are worth a day of their own. Soon.)

One conversation, one session, one shift. Close it and the slate wipes. Once you know that, you stop being afraid to start over. Starting over is the feature.