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 #3260] [BUG]: fail to render latex and support 3rd api of supported open-source llm #2095

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

Originally created by @li-Ko-Ko on GitHub (Feb 18, 2025).
Original GitHub issue: https://github.com/Mintplex-Labs/anything-llm/issues/3260

How are you running AnythingLLM?

AnythingLLM desktop app

What happened?

  1. agent does not support 3rd party api:
    {chat api: 3rd party deepseek-r1 through generic openai, agent api: official deepseek r1} -> {chat api: normal, agent api: invalid json response body at https://api.deepseek.com/v1/chat/completions reason: Unexpected end of JSON input}
    {chat api: 3rd party deepseek-r1 through generic openai, agent api: 3rd party deepseek-r1 through generic openai} -> {chat api: normal, agent api: 400 status code (no body)}
    {chat api: official deepseek r1, agent api: 3rd party deepseek-r1 through generic openai} -> {chat api: busy (may need more attempts), agent api: 400 status code (no body)}
    {chat api: official deepseek r1, agent api: 3rd party deepseek-r1 through generic openai} -> {chat api: busy (may need more attempts), agent api: invalid json response body at https://api.deepseek.com/v1/chat/completions reason: Unexpected end of JSON input}

Hope the upcoming version can support 3rd party api that is the same as official ones.

  1. failed to render latex in answers.

Are there known steps to reproduce?

No response

Originally created by @li-Ko-Ko on GitHub (Feb 18, 2025). Original GitHub issue: https://github.com/Mintplex-Labs/anything-llm/issues/3260 ### How are you running AnythingLLM? AnythingLLM desktop app ### What happened? 1. agent does not support 3rd party api: {chat api: 3rd party deepseek-r1 through generic openai, agent api: official deepseek r1} -> {chat api: normal, agent api: invalid json response body at https://api.deepseek.com/v1/chat/completions reason: Unexpected end of JSON input} {chat api: 3rd party deepseek-r1 through generic openai, agent api: 3rd party deepseek-r1 through generic openai} -> {chat api: normal, agent api: 400 status code (no body)} {chat api: official deepseek r1, agent api: 3rd party deepseek-r1 through generic openai} -> {chat api: busy (may need more attempts), agent api: 400 status code (no body)} {chat api: official deepseek r1, agent api: 3rd party deepseek-r1 through generic openai} -> {chat api: busy (may need more attempts), agent api: invalid json response body at https://api.deepseek.com/v1/chat/completions reason: Unexpected end of JSON input} Hope the upcoming version can support 3rd party api that is the same as official ones. 2. failed to render latex in answers. ### Are there known steps to reproduce? _No response_
yindo added the possible bug label 2026-02-22 18:28:08 -05:00
yindo closed this issue 2026-02-22 18:28:08 -05:00
yindo commented 2026-02-22 18:28:08 -05:00
Author
Owner
Copy Link
Copy Source

@timothycarambat commented on GitHub (Feb 18, 2025):

agent does not support 3rd party API:
invalid json response body at https://api.deepseek.com/v1/chat/completions

The deepseek API integration only uses Deepseek - use the generic OpenAI connector if the endpoint is not officially deepseek.

failed to render latex in answers.

There are about 3 closed issues about LaTeX. TLDR; we render Latex fine, its up to your model to make good Latex and we support $,$$ and [..] notations.

@timothycarambat commented on GitHub (Feb 18, 2025): > agent does not support 3rd party API: > invalid json response body at https://api.deepseek.com/v1/chat/completions The deepseek API integration _only uses Deepseek_ - use the generic OpenAI connector if the endpoint is not officially deepseek. > failed to render latex in answers. There are about 3 closed issues about LaTeX. TLDR; we render Latex fine, its up to your model to make good Latex and we support `$`,`$$` and `[..]` notations.
yindo changed title from [BUG]: fail to render latex and support 3rd api of supported open-source llm to [GH-ISSUE #3260] [BUG]: fail to render latex and support 3rd api of supported open-source llm 2026-06-05 14:44: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#2095
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?