e17994d8fe
* New Feature: Evaluations for AgentFlow v2 * New Feature: Evaluations for Assistants and minor tweaks on other evaluations. * do not store messages during evaluation for agent flows. * common cost formatting * moving the category names to description (in create dialog) and adjusting the side drawer label * lint fixes * Enhancement: Add auto-refresh toggle for evaluations with 5-second interval and adjust grid item size for metrics display. * 1) chatflow types are stored in additional config 2) messages are now stored with type "Evaluations" 3) Message Dialog has a new Type in the ChatType Filter Dropdown 4) Chatflow badges on the view page, have the right canvas URL 5) outdated API returns chatflow type along with the stale indicator. 6) UI - Flow Indicator Icons are shown in the Chatflows Used chips & side drawer * Refactor JWT error handling to return 401 status for expired refresh tokens. Update chat message ID assignment to remove UUID fallback. Enhance ViewMessagesDialog to set default chat type filters and implement a new method for determining chat type sources. Modify EvalsResultDialog to open links in a new tab and adjust icon sizes for better consistency. Clean up unused imports in EvaluationResultSideDrawer. * handling on Click for deleted flows and minor code cleanup * evals ui fix * Refactor evaluation service to improve error handling and data parsing. Update additionalConfig handling to default to an empty object if not present. Enhance type definitions for better clarity. Adjust MetricsItemCard to prevent overflow and improve layout consistency. --------- Co-authored-by: Henry <hzj94@hotmail.com> |
||
|---|---|---|
| .github | ||
| .husky | ||
| assets | ||
| docker | ||
| i18n | ||
| images | ||
| metrics | ||
| packages | ||
| .dockerignore | ||
| .eslintrc.js | ||
| .gitignore | ||
| .npmrc | ||
| CODE_OF_CONDUCT.md | ||
| CONTRIBUTING.md | ||
| Dockerfile | ||
| LICENSE.md | ||
| README.md | ||
| SECURITY.md | ||
| artillery-load-test.yml | ||
| package.json | ||
| pnpm-lock.yaml | ||
| pnpm-workspace.yaml | ||
| turbo.json | ||
README.md
English | 繁體中文 | 简体中文 | 日本語 | 한국어
Build AI Agents, Visually
⚡Quick Start
Download and Install NodeJS >= 18.15.0
-
Install Flowise
npm install -g flowise -
Start Flowise
npx flowise start
🐳 Docker
Docker Compose
- Clone the Flowise project
- Go to
dockerfolder at the root of the project - Copy
.env.examplefile, paste it into the same location, and rename to.envfile docker compose up -d- Open http://localhost:3000
- You can bring the containers down by
docker compose stop
Docker Image
-
Build the image locally:
docker build --no-cache -t flowise . -
Run image:
docker run -d --name flowise -p 3000:3000 flowise -
Stop image:
docker stop flowise
👨💻 Developers
Flowise has 3 different modules in a single mono repository.
server: Node backend to serve API logicsui: React frontendcomponents: Third-party nodes integrationsapi-documentation: Auto-generated swagger-ui API docs from express
Prerequisite
- Install PNPM
npm i -g pnpm
Setup
-
Clone the repository
git clone https://github.com/FlowiseAI/Flowise.git -
Go into repository folder
cd Flowise -
Install all dependencies of all modules:
pnpm install -
Build all the code:
pnpm buildExit code 134 (JavaScript heap out of memory)
If you get this error when running the above `build` script, try increasing the Node.js heap size and run the script again:export NODE_OPTIONS="--max-old-space-size=4096" pnpm build -
Start the app:
pnpm startYou can now access the app on http://localhost:3000
-
For development build:
-
Create
.envfile and specify theVITE_PORT(refer to.env.example) inpackages/ui -
Create
.envfile and specify thePORT(refer to.env.example) inpackages/server -
Run
pnpm dev
Any code changes will reload the app automatically on http://localhost:8080
-
🌱 Env Variables
Flowise support different environment variables to configure your instance. You can specify the following variables in the .env file inside packages/server folder. Read more
📖 Documentation
🌐 Self Host
Deploy Flowise self-hosted in your existing infrastructure, we support various deployments
☁️ Flowise Cloud
Get Started with Flowise Cloud
🙋 Support
Feel free to ask any questions, raise problems, and request new features in discussion
🙌 Contributing
Thanks go to these awesome contributors
See contributing guide. Reach out to us at Discord if you have any questions or issues.
📄 License
Source code in this repository is made available under the Apache License Version 2.0.