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

[Feature]: AI Suite integration #534

Open
1 of 3 tasks
areibman opened this issue Nov 25, 2024 · 3 comments
Open
1 of 3 tasks

[Feature]: AI Suite integration #534

areibman opened this issue Nov 25, 2024 · 3 comments
Labels
enhancement New feature or request

Comments

@areibman
Copy link
Contributor

💡 Feature Description and Proposed Solution

A new LLM chat framework called AI Suite just launched from Andrew Ng's team
https://github.com/andrewyng/aisuite

Adding observability callbacks would be a huge value-add for their project. This would involve:

  1. Building a custom instrumentor
  2. If needed, raise a PR to AI suite to improve observability handlers
  3. Add an optional dependency to AI suite to include AgentOps
  4. Updating our docs to show support
  5. Updating their docs to show support

🤔 Related Problem

No response

🤝 Contribution

  • Yes, I'd be happy to submit a pull request with these changes.
  • I need some guidance on how to contribute.
  • I'd prefer the AgentOps team to handle this update.
@areibman areibman added enhancement New feature or request and removed enhancement New feature or request labels Nov 25, 2024
@TKTSWalker
Copy link
Contributor

Looking at this, right now it looks like the system handles only sync chat completions so it doesn't seem to be anything hard or particularly taxing to work on!

Having observability handlers for LLMEvent, ActionEvent and ActionEvent seems simple enough, but I did have an idea I wanted to get greenlit! I'm thinking about putting this as a sort of simple wrapper and basically making it so if you set more than one provider on the AI Suite side it automatically initializes multi sessions under (providername.agentops_session) and logs the different sessions within each! Users can set a (start_multisession) bool to false to stop this and have it all go under one session.

@TKTSWalker
Copy link
Contributor

I'm halfway through right now and am at the handle_response area; would you rather the entire output is logged with AgentOps as one big message with the different providers all working or the different choices as separate outputs? Or would you rather have an option to toggle between??

@TKTSWalker
Copy link
Contributor

Going to wait until everything is all done to send to the provider; going to take a little time since AISuite doesn't natively have an event for telling when something is finished (Meaning i'll have to make conditionals for each based on the delta block or what other system they might use) but i'm confident I can make instrumentors now so it's more of a time issue than a skill issue!

It pretty much goes down to making a callback for each (which shouldn't take too long thanks to AgentOps having a lot of these already set up to reference) and then doing a wait until complete call! As mentioned in the OP's post, i'll have to make a pull request at the AISuite side for this to work!

@teocns teocns added the enhancement New feature or request label Dec 9, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

3 participants