# flock-study **Repository Path**: simpletree/flock-study ## Basic Information - **Project Name**: flock-study - **Description**: No description available - **Primary Language**: Unknown - **License**: Apache-2.0 - **Default Branch**: master - **Homepage**: None - **GVP Project**: No ## Statistics - **Stars**: 0 - **Forks**: 0 - **Created**: 2025-04-14 - **Last Updated**: 2025-04-16 ## Categories & Tags **Categories**: Uncategorized **Tags**: None ## README ## ๐Ÿ“ƒ Flock (Flexible Low-code Orchestrating Collaborative-agent Kits)

็ฎ€ไฝ“ไธญๆ–‡ | English | ๆ—ฅๆœฌ่ชž | Getting Started

> [!NOTE] > > ### ๐ŸŽ‰ What's New 2025/3/10 > > - **MCP Tools Support**: Added MCP Node with support for Model Context Protocol (MCP) tools, enabling seamless integration with MCP servers! Key features: > - ๐Ÿ› ๏ธ Convert MCP tools into LangChain tools for use with LangGraph agents > - ๐Ÿ“ฆ Connect to multiple MCP servers and dynamically load tools from them > - ๐Ÿ”„ Support both stdio and SSE transport modes for flexible communication > - ๐Ÿ”— Seamless integration with existing LangChain workflows > mcp > > ### ๐ŸŽ‰ What's New 2025/2/25 > > - **Parameter Extractor Node**: Added parameter extraction node that can automatically extract structured information from text and output in JSON format! > > ### ๐ŸŽ‰ What's New 2025/1/21 > > - **Subgraph Node Support**: Added subgraph node that allows you to encapsulate and reuse complete sub-workflows! > > - ๐Ÿ“ฆ Modular: Encapsulate complex workflows as standalone subgraph nodes > - ๐Ÿ”„ Reusable: Reuse the same subgraph node across different workflows > - ๐ŸŽฏ Maintainable: Update and maintain sub-workflow logic independently > > ### ๐ŸŽ‰ What's New 2025/1/8 > > - **Human Node**: Added a new human-in-the-loop node supporting key scenarios: > - ๐Ÿ› ๏ธ Tool Call Review: Human review, edit, or approve tool calls requested by the LLM > - โœ… LLM Output Validation: Human review, edit, or approve content generated by the LLM > - ๐Ÿ’ก Context Provision: Enable LLM to request human input for clarification or additional details > > ### ๐ŸŽ‰ What's New 2024/12/23 > > - **Multimodal Chat Support**: Added support for multimodal chat (currently only supports image modality, with more modalities coming soon)! > multimodal > ### ๐ŸŽ‰ What's New 2024/12/18 > > - **If-Else Node**: Added If-Else node to support conditional logic in workflows! The node supports various condition types including Contains, Not contains, Start with, End with, Is, Is not, Is empty, and Is not empty. Multiple conditions can be combined using AND/OR operators for complex conditional logic, allowing you to create sophisticated branching workflows based on your data. > ### ๐ŸŽ‰ What's New 2024/12/7 > > - **Code Execution Node**: Added Python code execution capabilities to workflows! This node allows you to write and execute Python scripts directly within your workflow, supporting variable references and dynamic data transformations. Perfect for arithmetic operations, data processing, text manipulation, and custom logic that goes beyond preset node functionalities. > ### ๐ŸŽ‰ What's New 2024/11/12 > > - **Intent Recognition Node**: New Intent Recognition node that can automatically identify user input intent based on preset categories, supporting multi-classification routing! > intent recognition > > - **CrewAI Node Support**: Now you can leverage CrewAI's powerful multi-agent capabilities in your workflows! Create sophisticated agent teams and orchestrate complex collaborative tasks with ease. > crewai ### Flock is a workflow-based low-code platform for rapidly building chatbots, RAG applications, and coordinating multi-agent teams. Built on LangChain and LangGraph, it provides a flexible, low-code orchestrating solution for collaborative agents, supporting chatbots, RAG applications, agents, and multi-agent systems, with the capability for offline operation. ### ๐Ÿค–๏ธ Overview overview ### Work Flow overview ### Node Types and Functions Flock's workflow system consists of various node types, each serving a specific purpose: 1. Input Node: Processes initial input and converts it into a format the workflow can handle. 2. LLM Node: Utilizes large language models for text generation and processing. 3. Retrieval Node: Fetches relevant information from knowledge bases. 4. Tool Node: Executes specific tasks or operations, extending workflow functionality. 5. Retrieval Tool Node: Combines retrieval capabilities with tool functionality. 6. Intent Recognition Node: Automatically identifies user input intent based on preset categories and routes to different processing flows. 7. Answer Node: Generates final answers or outputs, integrating results from previous nodes. 8. Subgraph Node: Encapsulates a complete sub-workflow, allowing for modular design. 9. Start and End Nodes: Mark the beginning and end of the workflow. Future planned nodes include: - File Upload Node - Parameter Extraction Node These nodes can be combined to create powerful and flexible workflows suitable for various complex business needs and application scenarios. ### Image Tools use ![image](https://github.com/user-attachments/assets/4097b087-0309-4aab-8be9-a06fdc9d4964) ### Knowledge Retrieval ![image](https://github.com/user-attachments/assets/836fac80-ab49-4f6b-973c-25ba173149eb) ### Human in the loop (human approval or let the LLM rethink or ask human for help)

image image

Inspired by the [StreetLamb](https://github.com/StreetLamb) project and its [tribe](https://github.com/StreetLamb/tribe) project , Flock adopts much of the approach and code. Building on this foundation, it introduces some new features and directions of its own. Some of the layout in this project references [Lobe-chat](https://github.com/lobehub/lobe-chat), [Dify](https://github.com/langgenius/dify), and [fastgpt](https://github.com/labring/FastGPT). They are all excellent open-source projects, thanks๐Ÿ™‡โ€. ### ๐Ÿ‘จโ€๐Ÿ’ป Development Project tech stack: LangChain + LangGraph + React + Next.js + Chakra UI + PostgreSQL > [!NOTE] > > ### ๐Ÿค– Model System > > Flock supports various model providers and makes it easy to add new ones. Check out our [Models Guide](./docs/Add_New_Model_Providers_Guide.md) to learn about supported models and how to add support for new providers. > ### ๐Ÿ› ๏ธ Tools System > > Flock comes with various built-in tools and supports easy integration of custom tools. Check out our [Tools Guide](./docs/Add_New_Tools_Guide.md) to learn about available tools and how to add your own. ### ๐Ÿ’กRoadMap 1 APP - [x] ChatBot - [x] SimpleRAG - [x] Hierarchical Agent - [x] Sequential Agent - [x] Work-Flow - [x] Intent Recognition Node - Automatically identify user input intent and route to different processing flows - [x] CrewAI Integration - [ ] More muti-agent ---On Progress 2 Model - [x] OpenAI - [x] ZhipuAI - [x] Siliconflow - [x] Ollama - [x] Qwen - [ ] Xinference 3 Ohters - [x] Tools Calling - [x] I18n - [ ] Langchain Templates ### ๐Ÿ˜๏ธHighlights - Persistent conversations: Save and maintain chat histories, allowing you to continue conversations. - Observability: Monitor and track your agents' performance and outputs in real-time using LangSmith to ensure they operate efficiently. - Tool Calling: Enable your agents to utilize external tools and APIs. - Retrieval Augmented Generation: Enable your agents to reason with your internal knowledge base. - Human-In-The-Loop: Enable human approval before tool calling. - Open Source Models: Use open-source LLM models such as llama, Qwen and Glm. - Multi-Tenancy: Manage and support multiple users and teams. ### How to get started #### 1. Deploy with Docker Compose ##### 1.1 Method 1: Pull Frontend and Backend Images from Docker Hub ```bash # Clone the repository git clone https://github.com/Onelevenvy/flock.git # Navigate to the docker directory cd flock/docker # Copy the environment configuration file cp ../.env.example .env # Start the docker compose docker compose up -d ``` #### 1.2 Method 2: Locally Build Frontend and Backend Images ```bash # Clone the repository git clone https://github.com/Onelevenvy/flock.git # Navigate to the docker directory cd flock/docker # Copy the environment configuration file cp ../.env.example .env # First, build the frontend and backend images docker compose -f docker-compose.localbuild.yml build # Then, start Docker Compose docker compose -f docker-compose.localbuild.yml up -d ``` #### 2. Start with Local Source Code #### 2.1 Preparation ##### 2.1.1 Clone the Code git clone https://github.com/Onelevenvy/flock.git ##### 2.1.2 Copy Environment Configuration File ```bash cp .env.example .env ``` ##### 2.1.3 Generate Secret Keys Some environment variables in the .env file have a default value of changethis. You have to change them with a secret key, to generate secret keys you can run the following command: ```bash python -c "import secrets; print(secrets.token_urlsafe(32))" ``` Copy the content and use that as password / secret key. And run that again to generate another secure key. ##### 2.1.4 Install postgres,qdrant,redis ```bash cd docker docker compose -f docker-compose.middleware.yml up -d ``` #### 2.2 Run Backend ##### 2.2.1 Installation of the basic environment Server startup requires Python 3.12.x. It is recommended to use pyenv for quick installation of the Python environment. To install additional Python versions, use pyenv install. ```bash pyenv install 3.12 ``` To switch to the "3.12" Python environment, use the following command: ```bash pyenv global 3.12 ``` Follow these steps : Navigate to the "backen" directory: ```bash cd backend ``` activate the environment. ```bash poetry env use 3.12 poetry install ``` ##### 2.2.2 initiral data ```bash # Run migrations alembic upgrade head ``` ##### 2.2.3 run unicorn ```bash uvicorn app.main:app --reload --log-level debug ``` ##### 2.2.4 run celery (Not necessary, unless you want to use the rag function) ```bash poetry run celery -A app.core.celery_app.celery_app worker --loglevel=debug ``` #### 2.3 Run Frontend ##### 2.3.1 Enter the web directory and install the dependencies ```bash cd web pnpm install ``` ##### 2.3.2 Start the web service ```bash cd web pnpm dev # or pnpm build then pnpm start ``` ## Star History [![Star History Chart](https://api.star-history.com/svg?repos=Onelevenvy/flock&type=Date)](https://star-history.com/#Onelevenvy/flock&Date)