Skip to content

feat: support amazonq #80

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.

Sign up for GitHub

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

Jump to bottom
Merged
merged 2 commits into from
Sep 10, 2025
Merged

feat: support amazonq #80

merged 2 commits into from
Sep 10, 2025

Conversation

35C4n0r
Copy link
Collaborator

@35C4n0r 35C4n0r commented Sep 10, 2025 •
edited
Loading

@35C4n0r 35C4n0r self-assigned this Sep 10, 2025
johnstcn
johnstcn reviewed Sep 10, 2025
View reviewed changes
Copy link
Member

@johnstcn johnstcn left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

If an agent works with the "generic" message formatting logic, do we really need to add a separate agent type for it?

@35C4n0r
Copy link
Collaborator Author

35C4n0r commented Sep 10, 2025

Yes, we'd still want to explicitly have it in our docs + support them in the type flag.

@35C4n0r 35C4n0r merged commit bf7acf8 into coder:main Sep 10, 2025
2 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

@johnstcn johnstcn johnstcn approved these changes

@matifali matifali Awaiting requested review from matifali

Assignees

@35C4n0r 35C4n0r

Labels

None yet

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

2 participants

@35C4n0r @johnstcn