4 ms·
What’s the point of running /clear vs starting a brand new session. At least with the latter I have session history, no? Pardon my ignorance since Claude isn’t
by ahurmazda 2mo ago
What’s the point of running /clear vs starting a brand new session. At least with the latter I have session history, no? Pardon my ignorance since Claude isn’t my primary driver
- mikeocool 2mo agoAs far as I've seen /clear is the same thing as starting a new session. If you type /resume right after clear, the first thing in the list is the session you just cleared.
- atsaloli 2mo agoTrue. Some versions of Claude Code had memory leaks. Therefore or was better to exit Claude Code and start a new session rather than /clear.
- andai 2mo agoNot 100% sure what clear does, but starting a new session invalidates the cache*, whereas I assume clear only removes part of the context, so it should be cheaper and faster. * In theory the system prompt is always the same and should therefore be cached, but in practice there's some dynamic strings in there so it doesn't work that way. (Unless they changed this recently.)
- g4cg54g54 2mo agoIts all lies anyhow: - https://github.com/anthropics/claude-code/issues/47756 https://github.com/anthropics/claude-code/issues/47756 > [BUG] /clear bleeds into the next session (what also breaks cache) - https://github.com/anthropics/claude-code/issues/47098 https://github.com/anthropics/claude-code/issues/47098 > [BUG] new sessions will *never* hit a (full)cache