Failed to load history: history unavailable for session "session-60f25624-ff09-469e-a9fa-316df171d773": RangeError: Maximum call stack size exceeded (internal)

[spgsroot]

Harness breaks down with the current error during long sessions.
Failed to load history: history unavailable for session "session-60f25624-ff09-469e-a9fa-316df171d773": RangeError: Maximum call stack size exceeded (internal)

[xiaoyuyu6420]

This thread has been sitting for a month, so a belated workaround in case you (or anyone landing here from search) still has the session around:

RangeError: Maximum call stack size exceeded during history load on a long session is a recursion-depth problem in the reader. If the recursion is merely deep (giant session) rather than infinite, raising Node's stack usually lets the history open:

NODE_OPTIONS="--stack-size=4000" dsh web

(same env var works with npx @deepseek-ai/dsh web). Then try opening the session again:

• It loads → you're unblocked; treat that mega session as an archive reference and start a fresh one for day-to-day work so you stay under the default stack.
• Still throws → that's infinite recursion rather than depth, and it needs an upstream fix. Worth a fresh report on the current version (the loader has changed a lot since this early-DP thread) with the session's rough size attached.

Either way the session file itself is intact — this is a read-side failure, not data loss.