A Simple and Universal Swarm Intelligence Engine, Predicting Anything. 简洁通用的群体智能引擎,预测万物
Go to file
Dominik Seemann 960e3ba81d fix(i18n): externalize chinese ui strings in process and step views
Routes ~50 hard-coded Chinese literals across Process.vue, Step2EnvSetup.vue,
Step3Simulation.vue, Step4Report.vue and Step5Interaction.vue through
vue-i18n, with corresponding entries added in lockstep to locales/en.json and
locales/zh.json (1031 -> 1101 lines each, parity preserved). En-locale users
no longer see Chinese in headers, status messages, error fallbacks, project-
info modals, or chat-history prompt construction.

Backend-coupled regex parsers in Step4Report.vue (28 markers + no-reply
predicate + log-severity helper) are centralised into a frozen REPORT_MARKERS
block at the top of <script setup>, with each entry comment-anchored to its
canonical source line in backend/app/services/zep_tools.py. The block is
allowlisted in the audit script so future English alternates can be added
inline once the backend prompts are translated under spec
i18n-report-agent-prompts (issue #25). The Step2EnvSetup stage watcher gets
the same treatment: a STAGE_PHASE_MAP collapses three Chinese-string
equality checks into a lookup that already accepts both legacy Chinese
display strings and the snake_case backend identifiers.

Adds frontend/scripts/audit-i18n-strings.sh as a local verifier (the
referenced .kiro/specs/i18n-e2e-english-verification audit script no longer
exists). The script greps the five files for non-allowlisted CJK literals,
diffs en.json/zh.json key sets, and guards against an en.json CJK regression
(per #20 / spec i18n-backfill-zh-json). Exits 0 on success.

Closes #23
2026-05-07 21:57:06 +00:00
.claude Create done.md 2026-05-07 10:14:46 +02:00
.github/workflows feat(docker): add Docker support with Dockerfile, docker-compose.yml, and .dockerignore; update README for Docker deployment instructions 2026-01-22 14:35:41 +08:00
.kiro fix(i18n): externalize chinese ui strings in process and step views 2026-05-07 21:57:06 +00:00
.ticket feat(claude): add /ticket and /ticket-list commands for GitHub Issues (Step 3) 2026-05-06 17:55:42 +02:00
backend fix(graphiti): surface embedding failures and document ollama embedder 2026-05-07 20:39:42 +00:00
frontend fix(i18n): externalize chinese ui strings in process and step views 2026-05-07 21:57:06 +00:00
locales fix(i18n): externalize chinese ui strings in process and step views 2026-05-07 21:57:06 +00:00
scripts feat(i18n): externalize chinese log and api response strings 2026-05-07 13:52:22 +00:00
static/image feat(README): add demo video sections for Wuhan University Public Opinion and Dream of the Red Chamber simulations; include new image asset 2026-01-20 11:17:11 +08:00
.dockerignore feat(docker): add Docker support with Dockerfile, docker-compose.yml, and .dockerignore; update README for Docker deployment instructions 2026-01-22 14:35:41 +08:00
.env.example fix(graphiti): surface embedding failures and document ollama embedder 2026-05-07 20:39:42 +00:00
.gitignore feat(claude): add /ticket and /ticket-list commands for GitHub Issues (Step 3) 2026-05-06 17:55:42 +02:00
CLAUDE.md fix(graphiti): surface embedding failures and document ollama embedder 2026-05-07 20:39:42 +00:00
Dockerfile feat(docker): add Docker support with Dockerfile, docker-compose.yml, and .dockerignore; update README for Docker deployment instructions 2026-01-22 14:35:41 +08:00
LICENSE Add GNU AGPL v3 License 2025-12-19 15:24:16 +08:00
README-EN.md docs: update CLAUDE.md and resolve README merge conflicts (Step 1) 2026-05-06 17:38:44 +02:00
README-ZH.md docs: update CLAUDE.md and resolve README merge conflicts (Step 1) 2026-05-06 17:38:44 +02:00
README.md fix(graphiti): surface embedding failures and document ollama embedder 2026-05-07 20:39:42 +00:00
docker-compose.yml fix(graphiti): surface embedding failures and document ollama embedder 2026-05-07 20:39:42 +00:00
package-lock.json Change project license from Apache-2.0 to AGPL-3.0 in package.json, package-lock.json, and backend/pyproject.toml. 2025-12-22 16:41:45 +08:00
package.json Fix: Change backend dev color to green 2025-12-30 10:04:27 +00:00

README.md

MiroFish Logo

666ghj%2FMiroFish | Trendshift

简洁通用的群体智能引擎,预测万物
A Simple and Universal Swarm Intelligence Engine, Predicting Anything

666ghj%2MiroFish | Shanda

GitHub Stars GitHub Watchers GitHub Forks Docker Ask DeepWiki

Discord X Instagram

English | 中文文档

Overview

MiroFish is a next-generation AI prediction engine powered by multi-agent technology. By extracting seed information from the real world (such as breaking news, policy drafts, or financial signals), it automatically constructs a high-fidelity parallel digital world. Within this space, thousands of intelligent agents with independent personalities, long-term memory, and behavioral logic freely interact and undergo social evolution. You can inject variables dynamically from a "God's-eye view" to precisely deduce future trajectories — rehearse the future in a digital sandbox, and win decisions after countless simulations.

You only need to: Upload seed materials (data analysis reports or interesting novel stories) and describe your prediction requirements in natural language
MiroFish will return: A detailed prediction report and a deeply interactive high-fidelity digital world

Our Vision

MiroFish is dedicated to creating a swarm intelligence mirror that maps reality. By capturing the collective emergence triggered by individual interactions, we break through the limitations of traditional prediction:

  • At the Macro Level: We are a rehearsal laboratory for decision-makers, allowing policies and public relations to be tested at zero risk
  • At the Micro Level: We are a creative sandbox for individual users — whether deducing novel endings or exploring imaginative scenarios, everything can be fun, playful, and accessible

From serious predictions to playful simulations, we let every "what if" see its outcome, making it possible to predict anything.

🌐 Live Demo

Welcome to visit our online demo environment and experience a prediction simulation on trending public opinion events we've prepared for you: mirofish-live-demo

📸 Screenshots

Screenshot 1 Screenshot 2
Screenshot 3 Screenshot 4
Screenshot 5 Screenshot 6

🎬 Demo Videos

1. Wuhan University Public Opinion Simulation + MiroFish Project Introduction

MiroFish Demo Video

Click the image to watch the complete demo video for prediction using BettaFish-generated "Wuhan University Public Opinion Report"

2. Dream of the Red Chamber Lost Ending Simulation

MiroFish Demo Video

Click the image to watch MiroFish's deep prediction of the lost ending based on hundreds of thousands of words from the first 80 chapters of "Dream of the Red Chamber"

Financial Prediction, Political News Prediction and more examples coming soon...

🔄 Workflow

  1. Graph Building: Seed extraction & Individual/collective memory injection & GraphRAG construction
  2. Environment Setup: Entity relationship extraction & Persona generation & Agent configuration injection
  3. Simulation: Dual-platform parallel simulation & Auto-parse prediction requirements & Dynamic temporal memory updates
  4. Report Generation: ReportAgent with rich toolset for deep interaction with post-simulation environment
  5. Deep Interaction: Chat with any agent in the simulated world & Interact with ReportAgent

🚀 Quick Start

The Docker setup brings up the full stack — frontend, backend, and Neo4j — with a single command.

# 1. Copy and configure environment variables
cp .env.example .env
# Edit .env and fill in LLM_API_KEY (and Neo4j password if you want to override the default)

# 2. Pull images and start
docker compose up -d

Reads .env from the project root, exposes ports 3000 (frontend) and 5001 (backend).

A faster mirror address is provided as a comment inside docker-compose.yml; uncomment to use it.

Option 2: Source Code Deployment

Prerequisites

Tool Version Description Check Installation
Node.js 18+ Frontend runtime, includes npm node -v
Python ≥3.11, ≤3.12 Backend runtime python --version
uv Latest Python package manager uv --version
Neo4j 5.x Community Local knowledge graph database neo4j --version

Install Neo4j (choose one):

# macOS
brew install neo4j

# Linux (Debian/Ubuntu)
# See official docs: https://neo4j.com/docs/operations-manual/current/installation/linux/

# Windows / All platforms
# Download Neo4j Desktop: https://neo4j.com/download/

# Set password before first start, then launch
neo4j-admin dbms set-initial-password your_neo4j_password
neo4j start

1. Configure Environment Variables

# Copy the example configuration file
cp .env.example .env

# Edit the .env file and fill in the required API keys

Required Environment Variables:

# LLM API Configuration (supports any LLM API with OpenAI SDK format)
# Recommended: Alibaba Qwen-plus model via Bailian Platform: https://bailian.console.aliyun.com/
# High consumption, try simulations with fewer than 40 rounds first
LLM_API_KEY=your_api_key
LLM_BASE_URL=https://dashscope.aliyuncs.com/compatible-mode/v1
LLM_MODEL_NAME=qwen-plus

# Knowledge Graph — local Neo4j + Graphiti (free, no rate limits)
NEO4J_URI=bolt://localhost:7687
NEO4J_USER=neo4j
NEO4J_PASSWORD=your_neo4j_password

# Embedding model (uncomment if using a non-OpenAI provider, e.g. Gemini)
# EMBEDDING_MODEL=gemini-embedding-001

# Embedding model via local Ollama (free, no API key, OpenAI-compatible endpoint).
# Pre-requisite: `ollama pull mxbai-embed-large` (1024-dim, matches Graphiti).
# In Docker, host.docker.internal:11434 reaches the host daemon; in host mode
# (`npm run dev`) substitute http://localhost:11434/v1.
# EMBEDDING_BASE_URL=http://host.docker.internal:11434/v1
# EMBEDDING_API_KEY=ollama
# EMBEDDING_MODEL=mxbai-embed-large

Embedder smoke test (recommended before the first graph build):

curl -s "$EMBEDDING_BASE_URL/embeddings" \
  -H "Authorization: Bearer $EMBEDDING_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"model":"'"$EMBEDDING_MODEL"'","input":"ping"}' \
  | jq '.data[0].embedding | length'
# Expected output: 1024

Optional — Accelerated LLM Configuration:

If you have a faster/cheaper provider, you can route auxiliary calls through it. Omit these entirely if not used (do not leave placeholder values).

LLM_BOOST_API_KEY=your_api_key_here
LLM_BOOST_BASE_URL=your_base_url_here
LLM_BOOST_MODEL_NAME=your_model_name_here

Note: MiroFish has migrated from Zep Cloud to local Graphiti + Neo4j. No third-party knowledge-graph account is required — completely free with no rate limits.

2. Install Dependencies

# One-click installation of all dependencies (root + frontend + backend)
npm run setup:all

Or install step by step:

# Install Node dependencies (root + frontend)
npm run setup

# Install Python dependencies (backend, auto-creates virtual environment)
npm run setup:backend

3. Start Services

# Start both frontend and backend (run from project root)
npm run dev

Service URLs:

  • Frontend: http://localhost:3000
  • Backend API: http://localhost:5001

Start Individually:

npm run backend   # Start backend only
npm run frontend  # Start frontend only

📬 Join the Conversation

QQ Group

 

The MiroFish team is recruiting full-time/internship positions. If you're interested in multi-agent simulation and LLM applications, feel free to send your resume to: mirofish@shanda.com

📄 Acknowledgments

MiroFish has received strategic support and incubation from Shanda Group!

MiroFish's simulation engine is powered by OASIS (Open Agent Social Interaction Simulations), We sincerely thank the CAMEL-AI team for their open-source contributions!

📈 Project Statistics

Star History Chart