Go-MiroFish, lightweight and local-first
Canonical development: Go gateway in Docker on :3000; Vue locally via Vite on :5173. You need Docker, Node 18+, and a one-time npm run setup.
-
Clone
git clone https://github.com/go-mirofish/go-mirofish.git cd go-mirofish -
Configure and install
cp .env.example .env npm run setup
Edit
.envand setLLM_API_KEYandZEP_API_KEY. -
Start the API (Docker)
make up
- API / health: http://127.0.0.1:3000/health
-
Start the UI (local — second terminal)
npm run dev
- App: http://127.0.0.1:5173 (Vite proxies
/apito the gateway on :3000)
- App: http://127.0.0.1:5173 (Vite proxies
| MiroFish (upstream) | go-mirofish (this repo) | |
|---|---|---|
| Control plane | Python / Flask (plus JS frontend) | Go (gateway/) — all /api/* routes |
| Local dev | Python venv, Flask, often multi-service | Docker gateway + local Vite (make up + npm run dev) |
| Simulation worker | Python-side integration | Go-native worker in the gateway process |
| Benchmarks & examples | Mixed scripts | Go go-mirofish-examples + bench tools + mirofish-hybrid helpers |
| Product Python | Required on the hot path | Removed (no backend/.venv in this tree) |
| Design goal | Full MiroFish upstream feature set | Local-first: lower moving parts, one gateway binary, fewer host dependencies |
Note
RAM/startup “targets” depend on model provider, graph size, and simulation profile. For supported setup, see Installation.
- Static playground (zero-cost replay): gomirofish.vercel.app
.png)
Home / entry |
.png)
Simulation run |
.png)
Report generation |
.png)
Report timeline / tools |
.png)
Simulation history |
.png)
Deep interaction |
.png)
Split: graph, workbench & system terminal |
.png)
Graph view & node details |
| Device | RAM | Works? |
|---|---|---|
| Desktop / laptop | 8GB | Yes |
| Desktop / laptop | 4GB | Yes (smaller simulations) |
| Raspberry Pi 5 | 4GB | Yes (light workloads; validate locally) |
| Raspberry Pi 4 | 4GB | Limited (expect tight headroom) |
Warning
Large graphs, long simulations, or heavy models can exceed 4GB systems. Start with short runs and smaller seeds.
Issues and PRs are welcome. Use this repo for go-mirofish changes; upstream product discussion stays with MiroFish. Longer guides for contributors and the Phase 1–6 roadmap will live on go.mirofish.ai as the docs site grows.
Derived from MiroFish. Simulation is powered by OASIS—thanks to the CAMEL-AI team.