claude-code - 💡(How to fix) Fix Bug: 2.1.120 crashes on resume via "claude -c" / "claude --continue" (interactive /resume works) [4 comments, 5 participants]

``` ERROR g9H is not a function. (In 'g9H(K)', 'g9H' is undefined) /$bunfs/root/src/entrypoints/cli.js:9251:5663 ```

Stack: ```

• <anonymous> (cli.js:9251:5663)
• WC (cli.js:492:63749)
• pj (cli.js:492:76948)
• fT (cli.js:492:76827)
• pj (cli.js:492:77745)
• fT (cli.js:492:76827)
• pj (cli.js:492:76926)
• fT (cli.js:492:76827)
• pj (cli.js:492:77745)
• fT (cli.js:492:76827)
• async <anonymous> (cli.js:18808:11089) ```

The minified site is in the `useScheduledTasks` / loop module init region — bundle shows the circular-import pattern `fL3=(LmH(),E8(ZmH))` wired up via `Bb8=Z(()=>{...})`. The recursive `pj`/`fT` frames suggest a state-update cascade during the auto-continue resume flow (`tM_` → `useScheduledTasks` mount). The fact that `/resume` from a fresh REPL works points to some difference in initialization order/state when `-c` is the entrypoint vs. when resume is dispatched after the REPL is already mounted.

TL;DR

The issue can be fixed by using the workaround claude + /resume instead of claude -c or rolling back to version 2.1.119.

Guidance

• The error message "g9H is not a function" suggests a problem with the useScheduledTasks module initialization, possibly due to a circular import issue.
• The fact that /resume from a fresh REPL works correctly implies a difference in initialization order or state when using the -c entrypoint.
• To verify the issue, try resuming a session using both claude -c and claude + /resume to see if the problem is specific to the auto-continue codepath.
• Consider rolling back to version 2.1.119, which is known to work correctly with claude -c, as a temporary solution.

Example

No code snippet is provided as the issue seems to be related to the internal implementation of the claude command and its dependencies.

Notes

The issue appears to be specific to version 2.1.120 and the -c entrypoint. The workaround using claude + /resume or rolling back to version 2.1.119 may not be a permanent solution, and further investigation is needed to resolve the root cause.

Recommendation

Apply the workaround by using claude + /resume instead of claude -c until a fixed version is available, as it is a simpler and less invasive solution compared to rolling back to a previous version.