Skip to content
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

Chat Participant doc nits #7298

Closed
chrisdias opened this issue May 17, 2024 · 1 comment · Fixed by #7307
Closed

Chat Participant doc nits #7298

chrisdias opened this issue May 17, 2024 · 1 comment · Fixed by #7307
Assignees

Comments

@chrisdias
Copy link
Member

"They can choose to fully use AI for the query processing, or to forward the user request to a backend service."

Should also say that the participant can use local resources for query processing. iow, you don't have to use AI or a backend service, can use anything you want.

"Participants can also provide the language model access to tools. With the help of the language model, the participant might select a tool and define how to invoke it."

Other places in the document use upper case "Language Model".

"To help the user take the conversation further, participants can provide follow-ups for each response. "

Should we add a picture of a follow up, just for reference?

"Note: The Chat and Language Model API are finalized in VS Code Insiders and will be finalized in VS Code Stable release in July"

Should we say "July 2024"?

Image

Image needs to be updated, we no longer overlap the GH icon and the chat participant icon.

" Chat participants are best when you want to control the full prompt, including the system message and instructions to the model."

Is "system message" the same as the "system prompt"? If so, we don't allow for this in the stable API so maybe remove this or caveat it?

@ntrogh
Copy link
Contributor

ntrogh commented May 22, 2024

Should we add a picture of a follow up, just for reference?

We have a call-out for that in the chat user experience elements screenshot. I added a link to the section about registering follow-up questions.

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 a pull request may close this issue.

2 participants