Enhance secondary sessions with problem statement retrieval from Jobs API #7429
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.
This PR addresses an issue where secondary sessions (sessionIndex > 0) were not attempting to retrieve problem statements from request turn messages, unlike initial sessions which already had this functionality.
Problem
Previously, only the initial session (sessionIndex === 0) would try to fetch problem statements from the Jobs API using
getJobBySessionId()
. Secondary sessions would only look at timeline events (comments/reviews) for prompts, missing potentially valuable problem statement context that could improve the session's understanding of the user's intent.Solution
Enhanced the
getFollowUpSessionPrompt()
method to mirror the problem statement retrieval logic fromgetInitialSessionPrompt()
:capi.getJobBySessionId()
/TITLE: \s*(.*)/i
) to extract meaningful prompts from problem statementsChanges Made
getFollowUpSessionPrompt()
method signature to acceptsession
,pullRequest
, andcapi
parametersdetermineSessionPrompt()
to pass the required parametersBackward Compatibility
This change is fully backward compatible. The existing timeline event-based fallback logic remains unchanged, ensuring that secondary sessions continue to work as before when no problem statement is available.
The enhancement follows the established pattern from initial session handling, maintaining code consistency and ensuring that all sessions now have equal access to problem statement context.
Created from VS Code via the GitHub Pull Request extension.
💬 Share your feedback on Copilot coding agent for the chance to win a $200 gift card! Click here to start the survey.