[BUG] Resuming a conversation by session ID broken in print mode
Status Fixed / completed
Maintainer reply ✓ Yes — igorkofman
Activity 8 comments · opened Jul 14, 2025 · closed Jul 21, 2025
💡 Likely answer: A maintainer (igorkofman, collaborator)
responded on this thread — see the highlighted reply below.
This is a duplicate of #1967. It is still broken in 1.0.51. Can we re-open that or do you need a new ticket?
8 Comments
/cc @igorkofman
Now we have
-session-idand it is still broken. :-/ You can only start new sessions with--session-idbut you can not continue them with--resume. That's sad ...Resuming a session creates a new session id - that is how the feature is designed to work (to allow working of sessions) and works the same in interactive mode.
@igorkofman Okay, then I misunderstood your comment over here.
So session-ids are supposed to change in every turn in a multi-turn conversation to the same session. That should really be reflected in the docs.
I was also surprised having recently read that comment. Furthermore, https://support.anthropic.com/en/articles/11014257-about-claude-s-max-plan-usage says there's a soft limit of 50 sessions per month which seems like it would be burned up quickly for any reasonable use of this unless 5 hour session windows can have multiple session IDs?
That's an estimate around typical interactive session use.
On Mon, Jul 21, 2025 at 6:55 AM Phil @.***> wrote:
It seems like it would make more sense to use the same session/session_id in --print mode
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.