Resuming the same session from multiple places multiple times

[DonJayamanne]

Assume you have a session in the terminal
Now open another terminal and try to resume this same session, it does allow you do to do this.
Now use the SDK as well to resume this same session

This leads to the confusion which session is the latest/accurate.
If we have a permission request in one terminal, should we see the same in the SDK as well?

Further to this

• If you resume the session in another terminal and continue working in that terminal session,
• The first session though not used anymore will always display stale information

[github-actions]

Thanks for opening this issue @DonJayamanne!

I've labeled this as question and enhancement since you're raising important concerns about the behavior when resuming the same session from multiple locations.

Your observations are valid:

• Multiple concurrent resume points for the same session can lead to state confusion
• Stale information in inactive sessions
• Unclear handling of permission requests across multiple session clients

Could you clarify:

1. What would be the ideal behavior in your view? Should concurrent resumes be blocked, or should there be state synchronization?
2. Are you encountering this in a specific use case or workflow?

This will help determine whether this is expected behavior that needs documentation or if there's a design improvement needed.

AI generated by Issue Triage Agent

[DonJayamanne]

Should concurrent resumes be blocked, or should there be state synchronization?

Simplest solution is to block resumes from multiple places
State synchronization would be an added bous if there's a concept of opening a session in read-only mode.

2. Yes