Multiple sessions + RAM

Claude Code sessions use your computer's memory (RAM). A single session with a short conversation barely registers. A long session, or several sessions running in parallel, adds up fast. Left unchecked, your laptop starts struggling - video calls lag, the fan runs constantly, other apps slow down, and in extreme cases the machine crashes.

This lesson is about running multiple sessions without melting your laptop.

How it adds up

Each Claude Code session holds a context window - everything you've said, everything Claude has said, every file it's read. The longer the session, the bigger that context. Multiply by the number of sessions running, and your RAM bill climbs.

Typical usage

• 1 fresh session, short conversation - barely measurable, tens of MB
• 1 long session with large files - hundreds of MB
• 3-5 parallel sessions mid-workload - can hit several GB
• 10+ parallel sessions left running all day - heavy chunk of your machine's RAM

On a 16GB MacBook, 4-5 heavy Claude Code sessions can eat 6-8GB on top of what your browser, Slack, Zoom, and other apps already use. That's when things break.

Signs your machine is struggling

Watch for these

• Fans running loud and constant
• Laptop hot to touch
• Video calls (Zoom, Google Meet, Fathom) start stuttering, freezing, or dropping
• Other apps respond slowly
• Typing feels delayed in your terminal or browser
• Apps crash or refuse to open
• Worst case - full system freeze or crash

If you see any of these, it's usually Claude Code sessions + browser tabs + background apps together. Closing unused Claude sessions is the fastest fix.

How to run multiple sessions safely

Close sessions when you're done with them

End each session properly

terminal
/wrapup

Then close the terminal tab. Not closing means the session keeps running in the background eating memory even when you're not looking at it.

Know when to /wrapup mid-work

If a session has been running for hours and the context is getting huge (hundreds of messages, dozens of files read), end it before starting the next big task:

terminal
/wrapup

Then open a fresh session. The saved memory persists, so the next session picks up where you left off - without carrying the token bloat that was slowing things down.

Cap your parallel sessions

Rule of thumb on a typical 16GB laptop

• 1-2 sessions active - fine, no problem
• 3-5 sessions - OK if all are fresh, watch for slowdown
• 6+ sessions - you're pushing it; close some

On a 32GB+ machine you have more headroom. On 8GB, stay at 1-2.

Shut down your laptop occasionally

Don't just close the lid. Actually shut down (not sleep / restart) your laptop every few days. Claude Code leaves temp data behind in /private/var/folders/ (Mac) or %TEMP% (Windows) that can accumulate into tens of gigabytes over weeks. A full shutdown clears these caches.

Before a video call

If you have an important video call coming up

1. Close any Claude Code sessions you don't need
2. Check Activity Monitor (Mac) or Task Manager (Windows) - if RAM is over 80% used, close more apps
3. Close unused browser tabs
4. Give yourself 5 minutes of recovery time before the call starts

Treating Claude Code like other resource-heavy apps (Chrome, Figma, Photoshop) is the right mindset.

The "one big session" vs "many short sessions" question

Two patterns work

Pattern A - one long session per project

Keep Claude running in a project folder for hours, let context build up. Pros: Claude remembers everything you did that day. Cons: RAM climbs, responses slow as context fills.

Pattern B - many short sessions, memory saves the context

Start a session, do one thing, /wrapup, start a new session when you're ready for the next task. Pros: RAM stays low, each session is fast. Cons: requires /wrapup discipline to save what matters.

Pattern B is more efficient for daily work. The memory layer (covered in Module 04) makes "fresh session" feel like "continuation" because Claude loads the saved context instantly.

Action items

☐ End every session with /wrapup and close the terminal tab

☐ Keep parallel sessions under 5 on a 16GB laptop, under 2 on an 8GB laptop

☐ If a session has been running for hours, /wrapup and start fresh before your next big task

☐ Shut down your laptop fully every few days to clear temp caches

☐ Before important video calls - close extra Claude sessions + check RAM usage

Exercises

1. Review the concepts covered in this lesson: Multiple sessions + RAM.
2. Write down your key takeaway from this lesson.
3. Practice running any commands or prompts mentioned above inside your terminal.