Closing after opening an existing session will result in events.jsonl file being modified

[DonJayamanne]

If no changes are made to the session (nothing emitted), then I would expect nothing to change in the session.
I.e. it should be possible to open and close a session without making changes to the session, when user didn't invoke any methods that could cause the session to mutate (e.g. sending prompts etc)

The closeSession method wil always emit a session.shutodnw even which is written into the file.
This results in multiple session.shutdown being written when a session is opened just to look at some events.

[nathan815]

I see the same issue. Each time I open a session, its get marked as modified at the current time.

As a temporary workaround in my app, I'm maintaining some minimal custom metadata (session id to last activity time mapping).