-
Notifications
You must be signed in to change notification settings - Fork 91
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
[KE] Add assistant description #469
Conversation
it's better than nothing, but let's aim to have as much visibility as inference here. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for adding a callout to the core python README.
The Assistant representation in the typescript client is fairly detailed if you're interested in modeling it around that: https://github.com/pinecone-io/pinecone-ts-client?tab=readme-ov-file#pinecone-assistant
Thanks Austin! Because we are currently have separated repos for the Python SDK and the plugin, this adds another place we need to keep in sync. I hope soon we will be able to merge the plugin and add documentation only here. |
## Problem There were no info on assistant in the readme ## Solution Now there is info on assistant in the readme ## Type of Change - [ ] Bug fix (non-breaking change which fixes an issue) - [ ] New feature (non-breaking change which adds functionality) - [ ] Breaking change (fix or feature that would cause existing functionality to not work as expected) - [ ] This change requires a documentation update - [ ] Infrastructure change (CI configs, etc) - [x] Non-code change (docs, etc) - [ ] None of the above: (explain here) ## Test Plan Describe specific steps for validating this change.
## Problem There were no info on assistant in the readme ## Solution Now there is info on assistant in the readme ## Type of Change - [ ] Bug fix (non-breaking change which fixes an issue) - [ ] New feature (non-breaking change which adds functionality) - [ ] Breaking change (fix or feature that would cause existing functionality to not work as expected) - [ ] This change requires a documentation update - [ ] Infrastructure change (CI configs, etc) - [x] Non-code change (docs, etc) - [ ] None of the above: (explain here) ## Test Plan Describe specific steps for validating this change.
Problem
There were no info on assistant in the readme
Solution
Now there is info on assistant in the readme
Type of Change
Test Plan
Describe specific steps for validating this change.