Mintplex-Labs/anything-llm
1
0
Fork 0
mirror of https://github.com/Mintplex-Labs/anything-llm.git synced 2026-07-19 22:23:50 -04:00
Code Issues 328 Packages Projects Releases 10 Wiki Activity

[GH-ISSUE #2428] [BUG]: AnythingLLM consistently recognised ollama/qwen2.5:1.5b as Claude by Anthropic #1576

New Issue
Closed
opened 2026-02-22 18:25:29 -05:00 by yindo · 1 comment
yindo commented 2026-02-22 18:25:29 -05:00
Owner
Copy Link
Copy Source

Originally created by @evian999 on GitHub (Oct 4, 2024).
Original GitHub issue: https://github.com/Mintplex-Labs/anything-llm/issues/2428

How are you running AnythingLLM?

AnythingLLM desktop app

What happened?

As the title and followed picture indicated. I had tried the same question in ollama, qwen worked well (fig. 1). This issue still exists even though I changed both the LLM preference and the workspace LLM provider to ollama/qwen2.5 (fig. 2-3). Interestingly, this issue does not raise when I switched the LLM to ollama/llama (fig. 4).

So, I am curious if the AnythingLLM might have trouble with dealing the point in "2.5" so that the qwen cannot be recognised properly, and hence the system just switch Claude to me? But why Claude, because I do not have any Claude API or account at all.

image (fig. 1 same question in anythingLLM and ollama with same LLM)

image (fig. 2 workspace LLM provider)

image (fig. 3 LLM preference)

image (fig. 4 llama3 do not have the same issue)

Are there known steps to reproduce?

No response

Originally created by @evian999 on GitHub (Oct 4, 2024). Original GitHub issue: https://github.com/Mintplex-Labs/anything-llm/issues/2428 ### How are you running AnythingLLM? AnythingLLM desktop app ### What happened? As the title and followed picture indicated. I had tried the same question in ollama, qwen worked well (fig. 1). This issue still exists even though I changed both the LLM preference and the workspace LLM provider to ollama/qwen2.5 (fig. 2-3). Interestingly, this issue does not raise when I switched the LLM to ollama/llama (fig. 4). So, I am curious if the AnythingLLM might have trouble with dealing the point in "2.5" so that the qwen cannot be recognised properly, and hence the system just switch Claude to me? But why Claude, because I do not have any Claude API or account at all. ![image](https://github.com/user-attachments/assets/d0f0a420-e61f-416c-b030-b867b0da4ff0) (fig. 1 same question in anythingLLM and ollama with same LLM) ![image](https://github.com/user-attachments/assets/3b96a05e-66cb-4c18-be4b-79bfe7dec5a9) (fig. 2 workspace LLM provider) ![image](https://github.com/user-attachments/assets/497d3e50-a731-4b8f-b806-2cd9e4e97774) (fig. 3 LLM preference) ![image](https://github.com/user-attachments/assets/69f9f3aa-37f8-4ac5-aa5e-40a403a3dc1d) (fig. 4 llama3 do not have the same issue) ### Are there known steps to reproduce? _No response_
yindo added the possible bug label 2026-02-22 18:25:29 -05:00
yindo closed this issue 2026-02-22 18:25:29 -05:00
yindo commented 2026-02-22 18:25:29 -05:00
Author
Owner
Copy Link
Copy Source

@timothycarambat commented on GitHub (Oct 5, 2024):

This is not a bug with AnythingLLM. What you are seeing is a model hallucination, the difference between the CLI example and our UI was the use of a system prompt, but you can see that whole chain.

In general, you should never rely a model to tell you what it is. this is doubly true for OSS models. This is just a model quirk and is the LLM just hallucinating an answer. Go through everywhere in the code and you'll see we make no mention of trying to give an LLM an identity. The default system prompt just says it is "a useful assistant"

@timothycarambat commented on GitHub (Oct 5, 2024): This is not a bug with AnythingLLM. What you are seeing is a model hallucination, the difference between the CLI example and our UI was the use of a system prompt, but you can see that whole chain. In general, you should never rely a model to tell you what it is. this is doubly true for OSS models. This is just a model quirk and is the LLM just hallucinating an answer. Go through everywhere in the code and you'll see we make no mention of trying to give an LLM an identity. The default system prompt just says it is "a useful assistant"
yindo changed title from [BUG]: AnythingLLM consistently recognised ollama/qwen2.5:1.5b as Claude by Anthropic to [GH-ISSUE #2428] [BUG]: AnythingLLM consistently recognised ollama/qwen2.5:1.5b as Claude by Anthropic 2026-06-05 14:41:31 -04:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
Desktop
Docker
Integration Request
Integration Request
OS: Linux
OS: Mobile
OS: Windows
UI/UX
blocked
bug
bug
core-team-only
documentation
duplicate
embed-widget
enhancement
feature request
github_actions
good first issue
investigating
needs info / can't replicate
possible bug
pull-request
Mirrored from GitHub Pull Request
 question
stage: specifications
wontfix
No Label possible bug
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
yindo
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: Mintplex-Labs/anything-llm#1576
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?