-
-
Notifications
You must be signed in to change notification settings - Fork 230
Closed
Labels
enhancementNew feature or requestNew feature or request
Description
Scope check
- This is core LLM communication (not application logic)
- This benefits most users (not just my use case)
- This can't be solved in application code with current RubyLLM
- I read the Contributing Guide
Due diligence
- I searched existing issues
- I checked the documentation
What problem does this solve?
Reading docs like:
I'm noticing that these providers respond with quite a bit of rich information about rate limits in the headers of the response.
I also know from working on #234 that there is extra information in the body of the response.
I could also see value in having access to the raw request for analysis which is available on the faraday response object.
Proposed solution
Make the faraday response object available on the message that is returned.
Why this belongs in RubyLLM
Similar to #265 which enabled custom inputs, this would help support custom outputs from the APIs.
compumike
Metadata
Metadata
Assignees
Labels
enhancementNew feature or requestNew feature or request