Skip to content

Feature/llm response history #133

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

Closed

Conversation

felixbouazza
Copy link

@felixbouazza felixbouazza commented Apr 14, 2025

Hello,

This pull request introduces a new feature for the MCP agent by exposing the response_history attribute in the AugmentedLLMs class. This update is a foundational improvement that supports enhanced observability into LLM operations. By making this attribute accessible, we enable a range of valuable analytics that can drive better insights and performance monitoring.

close #132

@saqadri
Copy link
Collaborator

saqadri commented Apr 17, 2025

Oh this is quite interesting, @felixbouazza, thanks for this change. I am open to accepting this contribution as-is. Just give me a couple more days to think about this in relation to some other changes that are currently in-flight, such as updating AugmentedLLMs and the workflows to support Temporal execution.

The other thing that I need to think about is whether AugmentedLLM class should use the model provider's types (as they do today), or if they should natively use MCP types.

@felixbouazza
Copy link
Author

Hi @saqadri,
Thank you very much for your positive feedback and for taking the time to review this PR!
We completely understand needing a few days to reflect on these changes.

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 this pull request may close these issues.

surfacing response_history attribute from AugmentedLLMs
2 participants