Resuming session doesn't automatically fetch 'session.usage_info' until a prompt is sent

[bigguy345]

On py module. I'm creating a '{currentTokens}/{maxTokens}' indicator for the current session, and that data is only stored in SessionEvent 'session.usage_info', which only fires upon sending a prompt, and not on resuming a session through CopilotClient.resume_session. This causes a session init phase (period between session start and first prompt sent) where I just can't know what the current context tokens used are.

I know 'session.usage_info' is an event, but maybe also store this data directly onto the session object as well?

[github-actions]

Thanks for opening this issue @bigguy345!

I've labeled this as an enhancement for the Python SDK. Your use case makes sense — having session.usage_info available immediately when resuming a session would allow you to display token usage without waiting for the first prompt.

The suggestion to store usage info directly on the session object (in addition to the event) is a reasonable approach. The maintainers will review this and determine the best way to expose this data during session resumption.

AI generated by Issue Triage Agent

[patniko]

We'll work on saving this info in the session so you know where you left off.