• Commented in [crewAIInc/crewAI] on 2025-03-09.

  AI Summary: @Vidit-Ostwal has suggested a potential solution involving the creation of a session, providing code snippets for its instantiation and application within a crew setup. The suggested approach incorporates environment variables for AWS credentials and region configuration. However, @Vidit-Ostwal raises a question about potential redundancy, as the CrewAI framework might already

• Commented in [crewAIInc/crewAI] on 2025-03-09.

  AI Summary: @Vidit-Ostwal has suggested that the reported problem might be related to an issue with the "memory" function that has been observed and discussed by other users. The comment implies a potential connection between the current problem and previous reports regarding the behavior or functionality of the "memory" feature. It suggests

• Commented in [crewAIInc/crewAI] on 2025-03-07.

  AI Summary: Vidit-Ostwal has suggested exploring the reason behind the large number of arguments generated by the Large Language Model (LLM) before invoking the necessary tool. To gain a better understanding, they propose a strategic modification involving the LLM to discern whether the observed behavior is specific to the current LLM or

• Commented in [crewAIInc/crewAI] on 2025-03-07.

  AI Summary: Vidit-Ostwal has suggested passing a session key within the configuration attribute. This suggestion aims to potentially resolve an identified issue. The user proposes modifying the configuration to include session details. By incorporating this session information directly into the configuration, the system might handle connections and operations more effectively. Vidit-Ostwal mentions

• Commented in [crewAIInc/crewAI] on 2025-03-07.

  AI Summary: Vidit-Ostwal has suggested updating the crew version and attempting the process again. This recommendation implies that the current version might be outdated or causing issues, and updating to a newer version could potentially resolve those problems. Retrying the process after the update is crucial to determine if the changes have

• Commented in [crewAIInc/crewAI] on 2025-03-06.

  AI Summary: Vidit-Ostwal has suggested that the issue arises from using query as a parameter instead of sql_query when interacting with the tool. A correction in parameter naming is required. An updated version incorporating this change should be implemented and tested. It's expected that utilizing the correct parameter, sql_query, will resolve the

• Commented in [crewAIInc/crewAI] on 2025-03-06.

  AI Summary: @Vidit-Ostwal has suggested a potential solution for addressing the issue of calculating execution time or latency. The suggestion involves utilizing the output_log_file parameter. The commenter believes that this parameter captures the start_time and end_time at the task level, which could be helpful in determining the time taken by each execution.

• Commented in [crewAIInc/crewAI] on 2025-03-06.

  AI Summary: @Vidit-Ostwal has suggested following up on a community support post. The suggestion involves a request for additional information to better understand the context of the post. Specifically, the request is for the code related to the BaseTool implementation. Providing this code would offer a more comprehensive view of the issue

• Commented in [crewAIInc/crewAI] on 2025-03-06.

  AI Summary: Vidit-Ostwal has suggested providing the logs from the crew kickoff meeting. Sharing these logs will likely offer insights into the discussions, decisions, and action items that emerged during the kickoff. These logs can serve as a valuable reference point for team members to stay informed about the project's initial direction

• Commented in [crewAIInc/crewAI] on 2025-03-05.

  AI Summary: Vidit-Ostwal has suggested that the recipients try the latest version of the software or application. Vidit-Ostwal attempted to reproduce a particular issue but was unsuccessful. Therefore, updating to the newest version might resolve the problem the recipients are experiencing.

• Raised an issue in [crewAIInc/crewAI]: [BUG] Issue while trying to initializing a google ai studio embedder in knowledge (2025-02-28).

  AI Summary: Vidit-Ostwal has suggested that they are exploring knowledge implementation in CrewAI using a video as a guide and adapting the code for Google AI Studio compatibility. However, they encountered an issue where knowledge initialization fails due to a perceived missing google-generativeai package, despite it being installed. The provided code snippet

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

  AI Summary: Vidit-Ostwal has suggested exploring the potential benefits of a Human Input Tool within the CrewAI framework. This tool would function as an intermediary, requesting human input through a web user interface during agent operations. The intention is to allow agents to directly interact with humans for input, and once the

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

  AI Summary: Vidit-Ostwal has suggested there's an issue installing AutoGen in editable mode, encountering an error related to multiple top-level packages in a flat-layout. The error prevents setuptools from building due to potential inclusion of unwanted files, suggesting options like custom discovery, a src-layout, or explicit py_modules or packages declaration. They believe

• 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 that when running a crew with human_input set to True, the process fails due to an issue with lite llm not receiving the user role in the messages. The problem occurs when user input is required for tasks like validating Pokémon based on color and height. The

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

  AI Summary: Vidit-Ostwal has suggested assistance is needed due to encountering a BadRequestError while using the litellm library with the Google Studio API. The issue arises when attempting to utilize the gemini/gemini-1.5-pro model for a completion task. Despite providing a system message within the messages parameter, the API returns an error indicating

• Opened a PR in [crewAIInc/crewAI]: Pr branch (2025-03-08).

  AI Summary: Vidit-Ostwal has suggested a fix for issue #2307, building upon the work in #2309. The proposed solution addresses two distinct methods of crew initialization. The first scenario involves direct instantiation of a crew object. The second scenario covers cases where a function or class returns a crew instance. This includes

• Opened a PR in [crewAIInc/crewAI]: Added .copy for manager agent and shallow copy for manager llm (2025-03-03).

  AI Summary: @Vidit-Ostwal has suggested adding .copy for the manager agent and shallow_copy for the manager LLM. This enhancement likely aims to create copies of these objects, potentially for isolation, experimentation, or to prevent unintended modifications to the original instances. Using .copy likely creates a deep copy of the agent, ensuring complete

• Opened a PR in [crewAIInc/crewAI]: Adding streaming functionality, starting a discussion (2025-02-27).

  AI Summary: Vidit-Ostwal has suggested an approach to address issue #2206, involving changes to the crewai llm class by introducing a streaming = True argument, which is then passed to the .call function. This approach aims to modify the response handling by yielding consistent objects after receiving partial responses and removing the

• 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 by patching the get_crew() function. The patch aims to correct the object retrieval process within the function. The issue was caused by the function fetching the incorrect data. By implementing this patch, the get_crew() function should now return the correct object, resolving the underlying

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

  AI Summary: Vidit-Ostwal has suggested a fix for issue #2111. The suggestion involves adding a user message that is formatted by 'feedback'. This enhancement aims to improve the user experience by providing clearer and more informative feedback within the application. The updated message will likely guide users more effectively and ensure better

• Starred deepseek-ai/smallpond on 2025-03-01.
• Starred agno-agi/agno on 2025-02-26.
• Starred letta-ai/letta on 2025-02-25.
• Starred langchain-ai/langmem on 2025-02-24.
• Starred huggingface/picotron on 2025-02-20.

No repositories forked recently.