Skip to content

[BUG] 🚨 --continue and -p are now seriously broken together in 2.1.90 #43013

New issue
New issue
Closed as not planned
Closed as not planned
[BUG] 🚨 --continue and -p are now seriously broken together in 2.1.90#43013
Labels
api:vertexIssue relates to GCP Vertexarea:clibugSomething isn't workingduplicateThis issue or pull request already existshas reproHas detailed reproduction stepsplatform:macosIssue specifically occurs on macOSregressionstaleIssue is inactive

Description

@stbenjam
stbenjam
opened on Apr 3, 2026

Preflight Checklist

  • I have searched existing issues and this hasn't been reported yet
  • This is a single bug report (please file separate reports for different bugs)
  • I am using the latest version of Claude Code

What's Wrong?

claude --continue -p "..." no longer works when the originating session was also started with -p.

WORKAROUND: export CLAUDE_CODE_ENTRYPOINT=sdk-cli (Just cli prior to 2.1.108)

Root Cause

This is caused by the 2.1.90 change: "Changed --resume picker to no longer show sessions created by claude -p or SDK invocations".

The flow is:

  1. claude -p "..." creates a session tagged with sessionKind = "print" (or similar)
  2. claude --continue -p "..." scans for the most recent session → the enrichment function filters it out because sessionKind is set → returns null
  3. loadInitialMessages sees null from the --continue block, silently falls through with no error, and starts a brand new empty session

The --continue flag should bypass the sessionKind filter, since its explicit purpose is to continue the most recent session regardless of how it was created.

Additionally, the silent fallthrough is a design issue — if --continue can't find a session, it should error rather than silently starting fresh.

What Should Happen?

--continue -p should continue the most recent session created by any previous invocation, including -p sessions. If no session can be found, it should emit an error rather than silently creating a new session.

Error Messages/Logs

No session to continue.

Steps to Reproduce

cd $(mktemp -d)
claude --max-turns 1 -p "The answer is 42. Reply only with: OK"
claude --continue # note the previous session isn't continued

Important: Must be run from a standalone shell, NOT from within a Claude session - having CLAUDE_CODE_ENTRYPOINT set masks the problem

Claude Model

Opus

Is this a regression?

Yes, this worked in a previous version

Last Working Version

2.1.89

Claude Code Version

v2.1.90, v2.1.91, v2.1.92

Platform

Google Vertex AI

Operating System

macOS

Terminal/Shell

iTerm2

Additional Information

We rely on this functionality to run Claude in CI for multi-stage workflows where each stage uses --continue -p to build on the previous stage's context.

Activity

  1. stbenjam
    added
    bugSomething isn't working
    on Apr 3, 2026
  2. github-actions
    added
    has reproHas detailed reproduction steps
    regression
    area:cli
    platform:macosIssue specifically occurs on macOS
    api:vertexIssue relates to GCP Vertex
    on Apr 3, 2026

  3. github-actions commented on Apr 3, 2026

    @github-actions
    github-actionsBot
    on Apr 3, 2026 – with GitHub Actions

    Found 1 possible duplicate issue:

    1. --continue on 2.1.90 silently drops conversation context (regression from 2.1.89) #42376

    This issue will be automatically closed as a duplicate in 3 days.

    • If your issue is a duplicate, please close it and 👍 the existing issue instead
    • To prevent auto-closure, add a comment or 👎 this comment

    🤖 Generated with Claude Code

  4. jocel1 commented on Apr 3, 2026

    @jocel1
    jocel1
    on Apr 3, 2026

    It's related to the change from 2.1.90: "Changed --resume picker to no longer show sessions created by claude -p or SDK invocations"

  5. stbenjam commented on Apr 3, 2026

    @stbenjam
    stbenjam
    on Apr 3, 2026
    Author

    Maybe similar to #42376? Some bad things happened to resume / continue.

    For me this is a workaround:

    export CLAUDE_CODE_ENTRYPOINT=cli
  6. github-actions
    added
    duplicateThis issue or pull request already exists
    on Apr 3, 2026
  7. stbenjam
    closed this as completedon Apr 3, 2026
  8. stbenjam
    reopened this on Apr 3, 2026

  9. stbenjam commented on Apr 3, 2026

    @stbenjam
    stbenjam
    on Apr 3, 2026
    Author

    Actually #42376 is not quite the same, they are not using -p, but I think the causes are related.

  10. stbenjam
    added a commit that references this issue on Apr 3, 2026

    Work around --continue + -p bug in Claude Code

    df5b419

  11. 15 remaining items

  12. stbenjam commented on May 24, 2026

    @stbenjam
    stbenjam
    on May 24, 2026
    Author

    This is still broken in 2.1.150.

    Image
  13. github-actions
    removed
    staleIssue is inactive
    on May 24, 2026

  14. stbenjam commented on Jun 1, 2026

    @stbenjam
    stbenjam
    on Jun 1, 2026
    Author

    Still broken in 2.1.159.

  15. fjglira
    added a commit that references this issue on Jun 3, 2026

    Work around --continue + -p bug in Claude Code (openshift#77369)

    1d4ffd2

  16. stbenjam commented on Jun 17, 2026

    @stbenjam
    stbenjam
    on Jun 17, 2026
    Author

    Still a problem in 2.1.179

    stbenjam@fedora:/tmp/tmp.o1TlosHU6j$ claude -p "Hello world"


Hello! How can I help you today?
stbenjam@fedora:/tmp/tmp.o1TlosHU6j$ claude --continue
No conversation found to continue
stbenjam@fedora:/tmp/tmp.o1TlosHU6j$ claude --version
2.1.179 (Claude Code)
  17. not-stbenjam
    added a commit that references this issue on Jun 17, 2026

    fix: set CLAUDE_CODE_ENTRYPOINT in build_local_env for --continue sup…

    c7bdfac
  18. github-actions
    added
    staleIssue is inactive
    on Jul 15, 2026

  19. github-actions commented on Jul 29, 2026

    @github-actions
    github-actionsBot
    on Jul 29, 2026 – with GitHub Actions

    Closing for now — inactive for too long. Please open a new issue if this is still relevant.

  20. github-actions
    closed this as not plannedon Jul 29, 2026
  21. malingatembo
    added a commit that references this issue on Aug 5, 2026

    Work around --continue + -p bug in Claude Code (openshift#77369)

    6f520aa

  22. github-actions commented on Sep 23, 2026

    @github-actions
    github-actionsBot
    on Sep 23, 2026 – with GitHub Actions

    This issue has been automatically locked since it was closed and has not had any activity for 7 days. If you're experiencing a similar issue, please file a new issue and reference this one if it's relevant.

  23. github-actions
    locked as resolved and limited conversation to collaborators on Sep 23, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    api:vertexIssue relates to GCP Vertexarea:clibugSomething isn't workingduplicateThis issue or pull request already existshas reproHas detailed reproduction stepsplatform:macosIssue specifically occurs on macOSregressionstaleIssue is inactive

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions