🔴 Required Information
Describe the Bug:
When using OAuth in Gemini Enterprise, access tokens are correctly generated and refreshed when starting a new chat session. However, for previously created chats, each one retains its original (now expired) access token tied to its session state. These tokens are not refreshed automatically, even after reloading the page. As a result, tools within the agent that depend on a valid access token stop working in older chats.
Steps to Reproduce:
- Configure OAuth flow in Gemini Enterprise.
- Start a new chat and trigger token generation.
- Use a tool/agent that depends on the access token (works as expected).
- Wait until the access token expires.
- Return to the same (older) chat session.
- Attempt to use the same tool again.
- Observe failure due to expired access token.
- Refresh the page or reload the session.
- Try again — token is still not refreshed and the tool remains broken.
Expected Behavior:
Access tokens should be refreshed automatically (or re-issued) when expired, regardless of whether the chat session is new or old. Reloading the page or interacting with the agent should trigger token renewal so that dependent tools continue functioning.
Observed Behavior:
Access tokens are not refreshed for older chat sessions. Each chat appears to maintain its own session-bound token, and once expired, it is not renewed. This causes tools relying on the token to fail consistently in those chats.
🔴 Required Information
Describe the Bug:
When using OAuth in Gemini Enterprise, access tokens are correctly generated and refreshed when starting a new chat session. However, for previously created chats, each one retains its original (now expired) access token tied to its session state. These tokens are not refreshed automatically, even after reloading the page. As a result, tools within the agent that depend on a valid access token stop working in older chats.
Steps to Reproduce:
Expected Behavior:
Access tokens should be refreshed automatically (or re-issued) when expired, regardless of whether the chat session is new or old. Reloading the page or interacting with the agent should trigger token renewal so that dependent tools continue functioning.
Observed Behavior:
Access tokens are not refreshed for older chat sessions. Each chat appears to maintain its own session-bound token, and once expired, it is not renewed. This causes tools relying on the token to fail consistently in those chats.