Basic 'chat agent' API #193152
Merged
Basic 'chat agent' API #193152
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
I basically copy/pasted @jrieken's chat slash command API and modified it to work for agents. This is leaving all the existing stuff in place so we can adopt this incrementally.
It's all a bit complicated right now, we have slash commands from two different sources, variables that still use
@(this will change), and now agents using@and agent subcommands using/. I imagine that both slash command APIs will go away in favor of this one.This API can drive remote agents and it can also drive the local agents that will absorb our existing slash commands.