• Commented in [crewAIInc/crewAI-tools] on 2025-02-24.

  AI Summary: @Vidit-Ostwal has suggested that this issue is similar to another issue, which can be found at crewAIInc/crewAI#2209.

• Commented in [crewAIInc/crewAI] on 2025-02-24.

  *AI Summary: @Vidit-Ostwal has suggested major changes to the code, including:

• Removal of the asyncio library
• Elimination of the answer question queue
• Implementation of additional unspecified changes*

• Commented in [crewAIInc/crewAI] on 2025-02-24.

  AI Summary: @Vidit-Ostwal has suggested that there should be a separate section for guidelines for summarization. The section should contain the following: - Summarize the entire comment in exactly 100 words. - Ignore any @mentions or tagged users in the comment. - Provide the summary from the perspective of "@Vidit-Ostwal has suggested".

• Commented in [crewAIInc/crewAI] on 2025-02-24.

  AI Summary: @Vidit-Ostwal has checked the functionality of the input tool in a different project and found it to be working. They have shared a link to the GitHub repository where the tool is implemented successfully.

• Commented in [crewAIInc/crewAI] on 2025-02-24.

  AI Summary: @Vidit-Ostwal has suggested that the proposed solution should work well. He has also requested additional information on how the other dependent files were structured while creating the .exe file. He is seeking further clarification to improve the implementation.

• Commented in [explodinggradients/ragas] on 2025-02-24.

  AI Summary: @Vidit-Ostwal has suggested a change in src/ragas/testset/transforms/default.py file. They have suggested that line 157 should be modified from ner_overlap_sim to Parallel(cosine_sim_builder, ner_overlap_sim). @rgrizzo-linksmt has been requested to raise a PR for this change.

• Commented in [crewAIInc/crewAI] on 2025-02-24.

  AI Summary: @Vidit-Ostwal has suggested that the .kickoff() function currently returns a CrewOutput object. They believe it would be beneficial to yield the output of an input case as soon as it becomes available rather than waiting for all input cases to finish. To achieve this, they have proposed adding this capability

• Commented in [crewAIInc/crewAI] on 2025-02-23.

  AI Summary: @Vidit-Ostwal has suggested converting the provided bug (in an unknown format) to a Python-based format for improved readability. They believe the Python format will make it more accessible and straightforward for others to understand, thereby facilitating collaboration.

• Commented in [explodinggradients/ragas] on 2025-02-22.

  AI Summary: @Vidit-Ostwal has suggested obtaining a detailed description of the problem being faced. This will provide a better understanding of the issue and enable the community to provide more targeted assistance.

• Commented in [explodinggradients/ragas] on 2025-02-22.

  AI Summary: @Vidit-Ostwal has suggested that you share your code in order to help reproduce @zoey-lyu's issue. This would provide a better understanding of the root cause of the problem and facilitate finding a solution.

• Raised an issue in [crewAIInc/crewAI-tools]: Human Input Tool- Feature Request (2025-02-24).

  AI Summary: @Vidit-Ostwal has suggested exploring the development of a Human Input Tool. This tool would offer a web-based interface for humans to provide input during a training process. Unlike the existing human_input parameter, the tool would allow ongoing interaction between humans and agents throughout the training process, rather than a one-time

• Raised an issue in [microsoft/autogen]: Error while installing autogen in editable version (2025-02-18).

  AI Summary: @Vidit-Ostwal has suggested that the error encountered during the installation of autogen in editable version is likely due to a file structuring issue. The specific error message indicates that multiple top-level packages were discovered in a flat layout, which setuptools does not support. To resolve this, the user is advised

• Raised an issue in [crewAIInc/crewAI]: [BUG] LiteLLM call fails, when human_input set to True (2025-02-12).

  AI Summary: @Vidit-Ostwal has suggested adding feedback in the user role to resolve the issue where lite llm is not given the user role in the messages when called. This is causing the crew to fail for any input provided by the user. A screenshot and code snippet have been provided to

• Raised an issue in [BerriAI/litellm]: [Bug]: Support to Google AI Studio (2025-02-11).

  AI Summary: @Vidit-Ostwal has suggested a code snippet for using the LiteLLM library to perform text completion with the Gemini model. However, the code throws a BadRequestError due to an unspecified contents parameter in the GenerateContentRequest. They have also provided the error message and relevant version details (1.60.2).

• Raised an issue in [langfuse/langfuse]: bug: Running Langfuse Locally Dcoker (2025-02-08).

  AI Summary: @Vidit-Ostwal has suggested that the application is unable to start due to port 9000 being used by another process. They attempted to change the port but believe it is used elsewhere internally. They have also provided a log snippet showing the error message and are interested in contributing a fix.

• Opened a PR in [crewAIInc/crewAI]: Fixed the issue 2123 around memory command with CLI (2025-02-17).

  AI Summary: @Vidit-Ostwal has suggested resolving issue #2123. The get_crew() function was patched to retrieve the correct object.

• Opened a PR in [crewAIInc/crewAI]: Added user message before calling litellm (2025-02-12).

  AI Summary: @Vidit-Ostwal has suggested merging the fix for issue #2111 that adds a user message formatted by "feedback". This change addresses the issue where the user message was not being formatted correctly.

• Opened a PR in [crewAIInc/crewAI]: Added functionality to have any llm run test functionality (2025-02-09).

  AI Summary: @Vidit-Ostwal has suggested a change that resolves the problem outlined in issue #2067.

• Opened a PR in [crewAIInc/crewAI]: Added reset memories function inside crew class (2025-02-06).

  *AI Summary: @Vidit-Ostwal has suggested resolving the reset memories issue mentioned in #2023. They also propose additional changes:

1. Eliminating the CLI command for resetting memories.
2. Updating the documentation to reflect these modifications.

@Vidit-Ostwal is willing to implement these changes if the proposed solution is aligned with the desired outcome.*

• Opened a PR in [crewAIInc/crewAI]: Fixed the memory documentation (2025-02-04).

  AI Summary: @Vidit-Ostwal has suggested resolving the documentation issue discussed in issue #2030. The exact changes and resolutions are not specified in the comment, but it indicates that the necessary modifications have been made to address the concern raised in the referenced issue.

• Starred langchain-ai/langmem on 2025-02-24.
• Starred huggingface/picotron on 2025-02-20.
• Starred huggingface/datatrove on 2025-02-20.
• Starred CopilotKit/CopilotKit on 2025-02-20.
• Starred unslothai/unsloth on 2025-02-19.

• Forked crewAIInc/crewAI on 2025-01-27.