Skip to content

fix(amazonq): move context command provider to agentic chat controller #999

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Apr 18, 2025

Conversation

zixlin7
Copy link
Contributor

@zixlin7 zixlin7 commented Apr 18, 2025

Problem

  • moving contextComandProvider into agenticChatController instead

Solution

License

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

@zixlin7 zixlin7 marked this pull request as ready for review April 18, 2025 20:02
@zixlin7 zixlin7 requested a review from a team as a code owner April 18, 2025 20:02
@breedloj
Copy link
Contributor

Changes LGTM - this breaks a direct coupling between the low level context controller and the agentic server that was causing build issues resulting in inline changes needing to be reverted: #991

@zixlin7 zixlin7 merged commit 0ad24d4 into aws:main Apr 18, 2025
7 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants