Gate agentSessionsWelcome view behind ExP service using cached treatment values #290610
+78
−6
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The agentSessionsWelcome view needs to be controlled by the ExP service without blocking welcome page load on network calls.
Changes
Added
getCachedTreatment()toIWorkbenchAssignmentService: Returns synchronously from TAS client cache without awaiting network. Returnsundefinedif cache unavailable.Welcome page routing logic: Three entry points now check
agentSessionsWelcometreatment via cached value:AgentSessionsWelcomeRunnerContribution: Shows agent sessions welcome if treatment istrueOR config explicitly set toagentSessionsWelcomePageStartupPageRunnerContribution: Skips regular welcome when treatment istrueand config iswelcomePageworkbench.action.openWalkthrough: Redirects to agent sessions welcome when treatment istrueTreatment constant: Extracted
AGENT_SESSIONS_WELCOME_TREATMENT = 'agentSessionsWelcome'to shared locationBehavior
Fallback to regular welcome preserves backward compatibility when cache is unavailable or treatment unset.
Original prompt
💬 We'd love your input! Share your thoughts on Copilot coding agent in our 2 minute survey.