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

[GH-ISSUE #2593] [BUG]: Problem using VoyageAI embedders #1682

New Issue
Closed
opened 2026-02-22 18:26:01 -05:00 by yindo · 2 comments
yindo commented 2026-02-22 18:26:01 -05:00
Owner
Copy Link
Copy Source

Originally created by @PetrAPConsulting on GitHub (Nov 6, 2024).
Original GitHub issue: https://github.com/Mintplex-Labs/anything-llm/issues/2593

Originally assigned to: @shatfield4 on GitHub.

How are you running AnythingLLM?

AnythingLLM desktop app

What happened?

When using embedders voyage-3 or voyage-3 lite picked up from the VoyageAI embedder choices (Intel based Mac AnythingLLM-desktop app), I received information from VoyageAI API usage statistics that was used model voyage-01 model instead.
API usage statistics
App embedder settings

Are there known steps to reproduce?

No response

Originally created by @PetrAPConsulting on GitHub (Nov 6, 2024). Original GitHub issue: https://github.com/Mintplex-Labs/anything-llm/issues/2593 Originally assigned to: @shatfield4 on GitHub. ### How are you running AnythingLLM? AnythingLLM desktop app ### What happened? When using embedders **voyage-3** or **voyage-3 lite** picked up from the VoyageAI embedder choices (Intel based Mac AnythingLLM-desktop app), I received information from VoyageAI API usage statistics that was used model voyage-01 model instead. <img width="1849" alt="API usage statistics" src="https://github.com/user-attachments/assets/18228668-966d-475b-a1c2-52696254d8ee"> <img width="983" alt="App embedder settings" src="https://github.com/user-attachments/assets/ed8efcf9-ec8e-4c11-bbe9-3ce223196c17"> ### Are there known steps to reproduce? _No response_
yindo added the possible bug label 2026-02-22 18:26:01 -05:00
yindo closed this issue 2026-02-22 18:26:02 -05:00
yindo commented 2026-02-22 18:26:02 -05:00
Author
Owner
Copy Link
Copy Source

@timothycarambat commented on GitHub (Nov 6, 2024):

I have responded to this over email, but those models keys are directly from their docs and all we do is passthrough the model used. Can you open the desktop apps storage folder

Then open the file named .env and paste exactly what value is for the EMBEDDING_MODEL_PREF line item in the env. Unless VoyageAI does some kind of fallback for voyage-3 to voyage-01 we are passing exactly what is provided to us.

If the EMBEDDING_MODEL_PREF ENV is indeed as you see in the AnythingLLM UI you need to contact VoyageAI - as their dashboard clearly does not reflect the proper model used.

When attempting to repro I can confirm that the model key passed is indeed relayed to the Voyage API. So I am unable to repro this and its possible the dashboard on Voyage is incorrect

@timothycarambat commented on GitHub (Nov 6, 2024): I have responded to this over email, but those models keys are directly from their docs and all we do is passthrough the model used. Can you open the [desktop apps storage folder](https://docs.anythingllm.com/installation-desktop/storage) Then open the file named `.env` and paste exactly what value is for the `EMBEDDING_MODEL_PREF` line item in the env. Unless VoyageAI does some kind of fallback for voyage-3 to voyage-01 we are passing exactly what is provided to us. If the `EMBEDDING_MODEL_PREF` ENV is indeed as you see in the AnythingLLM UI you need to contact VoyageAI - as their dashboard clearly does not reflect the proper model used. When attempting to repro I can confirm that the model key passed is indeed relayed to the Voyage API. So I am unable to repro this and its possible the dashboard on Voyage is incorrect
yindo commented 2026-02-22 18:26:02 -05:00
Author
Owner
Copy Link
Copy Source

@timothycarambat commented on GitHub (Nov 6, 2024):

Fixed, will be in next desktop version. Upstream dep changed interface and that was the result and somehow did not throw errors in the provider.

@timothycarambat commented on GitHub (Nov 6, 2024): Fixed, will be in next desktop version. Upstream dep changed interface and that was the result and somehow did not throw errors in the provider.
yindo changed title from [BUG]: Problem using VoyageAI embedders to [GH-ISSUE #2593] [BUG]: Problem using VoyageAI embedders 2026-06-05 14:42:06 -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#1682
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?