> For the complete documentation index, see [llms.txt](https://docs.lleverage.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.lleverage.ai/support/release-notes/february-2025.md). # February 2025 ## February 2025 Release Notes ### New Features #### Knowledge Base System We're excited to announce significant improvements to Lleverage that enhance document processing capabilities and workflow usability: * Replaced Vector Stores with new Knowledge Base system * Intelligent AI-powered document chunking * Automatic Weaviate vector store integration * Improved document processing pipeline #### New Search Capabilities * Added Web Search node for real-time internet searches * Enhanced search configuration options * Integrated search results processing ### Workflow Improvements * Introduced Output Chips for easier output visualization and copying * Improved node output management * Enhanced workflow debugging capabilities These updates significantly improve document handling capabilities while making workflows more intuitive and easier to develop. The new Knowledge Base system provides a more streamlined approach to document processing, while Web Search and Output Chips add powerful new tools to your workflow building toolkit. *The Lleverage Team* Posted: February 11, 2025\ Version: 0.8.0 --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://docs.lleverage.ai/support/release-notes/february-2025.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.