nikmcfly/MiroFish-Offline
Offline multi-agent simulation & prediction engine. English fork of MiroFish with Neo4j + Ollama local stack.
View Origin LinkProduct Positioning & Context
Offline multi-agent simulation & prediction engine. English fork of MiroFish with Neo4j + Ollama local stack.
Related Ecosystem & Alternatives
Discover adjacent products, open-source repositories, and developer tools sharing similar technical architecture.
Deep-Dive FAQs
What is nikmcfly/MiroFish-Offline?
nikmcfly/MiroFish-Offline is a digital product or tool described as: Offline multi-agent simulation & prediction engine. English fork of MiroFish with Neo4j + Ollama local stack.
Where did nikmcfly/MiroFish-Offline originate?
Data for nikmcfly/MiroFish-Offline was aggregated directly from the GitHub Open Source community ecosystem, representing raw developer and early-adopter sentiment.
When was nikmcfly/MiroFish-Offline publicly launched?
The initial public indexing or launch date for nikmcfly/MiroFish-Offline within our tracked developer communities was recorded on March 14, 2026.
How popular is nikmcfly/MiroFish-Offline?
nikmcfly/MiroFish-Offline has achieved measurable traction, logging over 1,184 traction score and facilitating 271 recorded discussions or engagements.
Which technical categories define nikmcfly/MiroFish-Offline?
Based on metadata extraction, nikmcfly/MiroFish-Offline is categorized under topics such as: ai, multi-agent, neo4j, offline.
Are there active development issues for nikmcfly/MiroFish-Offline?
Yes, we are currently tracking open architectural debates and bug reports for this project on GitHub. There are currently 3 active high-priority issues logged recently.
What are some commercial alternatives to nikmcfly/MiroFish-Offline?
Our semantic intelligence engine identifies potential commercial alternatives in the SaaS space, such as Monkey Morse, which offers overlapping value propositions.
How does the creator describe nikmcfly/MiroFish-Offline?
The original author or development team describes the product as follows: "Offline multi-agent simulation & prediction engine. English fork of MiroFish with Neo4j + Ollama local stack."
Active Developer Issues (GitHub)
Logged: Mar 22, 2026
Logged: Mar 19, 2026
Logged: Mar 18, 2026
Community Voice & Feedback
@kmckinley I try to do the same. Can you share more information how you pointed to LM Studio?
I wasn't able to get 3.5 to work within ollama, so instead I started qwen3.5-35b-a3b in LM Studio and pointed the project to use that. It worked well, though I did have to make a few changes to get it to work.
Increase the max_tokens. qwen3.5-35b-a3b is a thinking model so we needed to give it room for that.
```
def chat_json(
self,
messages: List[Dict[str, str]],
temperature: float = 0.3,
- max_tokens: int = 4096
+ max_tokens: int = 8192
) -> Dict[str, Any]:
```
Remove response_format: LM Studio doesn't support response_format: {"type": "json_object"} — only "json_schema" or "text". The chat_json method passes json_object mode which Ollama accepts but LM Studio rejects.
```
response = self.chat(
messages=messages,
temperature=temperature,
max_tokens=max_tokens,
- response_format={"type": "json_object"}
)
```
Increase the max_tokens. qwen3.5-35b-a3b is a thinking model so we needed to give it room for that.
```
def chat_json(
self,
messages: List[Dict[str, str]],
temperature: float = 0.3,
- max_tokens: int = 4096
+ max_tokens: int = 8192
) -> Dict[str, Any]:
```
Remove response_format: LM Studio doesn't support response_format: {"type": "json_object"} — only "json_schema" or "text". The chat_json method passes json_object mode which Ollama accepts but LM Studio rejects.
```
response = self.chat(
messages=messages,
temperature=temperature,
max_tokens=max_tokens,
- response_format={"type": "json_object"}
)
```
> 请问,qwen3.5的模型支持吗?
i would say possible but i have not got the base to work
i would say possible but i have not got the base to work
this also is happening to me, i just have some doubts, could it be related to the default ollama service having a really small max token value. Also why qwen2.5 instead of qwen3.5?
Maybe in the yaml file set the context for the compose to launch ollama.
Maybe in the yaml file set the context for the compose to launch ollama.
BTW, instruction on frontpage still mentioned Neojs 5.15, and should be updated to 5.18 for the docker run instruction.
Updated with Neo4j to 5.18. Didn't help.
Will investigate more later.
Will investigate more later.
Thanks for looking into this. It did per screenshot, however nothing in it.
Step 2
NAME ID SIZE MODIFIED
nomic-embed-text:latest 0a109f422b47 274 MB 22 minutes ago
glm-4.7-flash:latest d1a8a26252f1 19 GB 3 days ago
gpt-oss:20b 17052f91a42e 13 GB 2 months ago
qwen3:latest 500a1f067a9f 5.2 GB 5 months ago
qwen3:30b 19e422b02313 18 GB 5 months ago
qwen3:8b 500a1f067a9f 5.2 GB 5 months ago
llava:13b 0d0eb4d7f485 8.0 GB 5 months ago
llava:latest 8dd30f6b0cb1 4.7 GB 5 months ago
llava-llama3:latest 44c161b1f465 5.5 GB 5 months ago
llama3.2:latest a80c4f17acd5 2.0 GB 5 months ago
llama3.2-vision:latest 6f2f9757ae97 7.8 GB 5 month...
Step 2
NAME ID SIZE MODIFIED
nomic-embed-text:latest 0a109f422b47 274 MB 22 minutes ago
glm-4.7-flash:latest d1a8a26252f1 19 GB 3 days ago
gpt-oss:20b 17052f91a42e 13 GB 2 months ago
qwen3:latest 500a1f067a9f 5.2 GB 5 months ago
qwen3:30b 19e422b02313 18 GB 5 months ago
qwen3:8b 500a1f067a9f 5.2 GB 5 months ago
llava:13b 0d0eb4d7f485 8.0 GB 5 months ago
llava:latest 8dd30f6b0cb1 4.7 GB 5 months ago
llava-llama3:latest 44c161b1f465 5.5 GB 5 months ago
llama3.2:latest a80c4f17acd5 2.0 GB 5 months ago
llama3.2-vision:latest 6f2f9757ae97 7.8 GB 5 month...
Thanks for the report. The core issue is that your graph appears empty (0 nodes, 0 edges) — the simulation config generator can't proceed without graph data.
A few things to check:
1. Did Step 1 (graph building) complete successfully? Check the graph panel — do you see nodes and edges?
2. Is your Ollama embedding model loaded? Run `ollama list` and confirm you have an embedding model (e.g., `nomic-embed-text`)
3. The `created_at` property warning suggests the Neo4j schema may need updating — try running with Neo4j 5.18 (see PR #10)
Can you share:
- Your `.env` config (redact any API keys)
- Output of `ollama list`
- Whether Step 1 showed a populated graph
This will help narrow down whether it's a graph build failure or a config generation bug.
A few things to check:
1. Did Step 1 (graph building) complete successfully? Check the graph panel — do you see nodes and edges?
2. Is your Ollama embedding model loaded? Run `ollama list` and confirm you have an embedding model (e.g., `nomic-embed-text`)
3. The `created_at` property warning suggests the Neo4j schema may need updating — try running with Neo4j 5.18 (see PR #10)
Can you share:
- Your `.env` config (redact any API keys)
- Output of `ollama list`
- Whether Step 1 showed a populated graph
This will help narrow down whether it's a graph build failure or a config generation bug.
Discovery Source
GitHub Open Source Aggregated via automated community intelligence tracking.
Tech Stack Dependencies
No direct open-source NPM package mentions detected in the product documentation.
Media Tractions & Mentions
No mainstream media stories specifically mentioning this product name have been intercepted yet.
Deep Research & Science
No direct peer-reviewed scientific literature matched with this product's architecture.
SaaS Metrics