mirror of
https://github.com/Mintplex-Labs/anything-llm.git
synced 2026-07-19 14:13:35 -04:00
Closed
opened 2026-02-22 18:20:55 -05:00 by yindo
·
11 comments
No Branch/Tag Specified
master
5846-bug-when-scrolling-up-scrolling-jumps
refactor-remove-workspace-pfp
5969-bug-stopgenerationbutton-disappears-on-the-first-prompt-that-initiates-an-agent-session
2235-bug-how-to-upload-a-folder-with-subfolders-with-files-to-anythingllm
5990-workspace-update-fails-with-unknown-argument-router_id-v1130v1150-intel-mac
opencomputer-examples
pg
feat/image-generation-translations
feat/image-generation
5924-bug-meeting-summary-fails-with-sincludes-is-not-a-function-when-default-llm-is-anthropic-claude
render
feat/uniform-modal-component
5883-bug-unescaped-content-in-json-strings-being-passed-to-document-generator-tools
5901-bug-api-update-embeddings-fails-prisma-argument-filename-is-missing-on-workspace_documentscreate-desktop-windows-v1141
hybrid-search
1981-translations
5752-bug-prompts-to-local-jan-endpoint-unresponsive
feat-disable-native-tool-calling-env-var
5676-bug-non-ollama-agent-providers-do-not-parse-and-present-reasoning-content
feat/markdown-web-scraping
5717-bug-apiv1documentupload-silently-drops-metadata-field-in-desktop-1130-arg-count-mismatch-nested-payload-key
fix/aibitat-context-overflow
5711-bug-erratic-deepseek-v4-flash-the-agent-model-failed-to-respond-400-the-reasoning_content
5631-feat-custom-api-request-timeouts-for-ai-providers
feat-reasoning-control
feat-agent-clarifying-questions-translations
5583-bug-lm-studio-provider-does-not-present-reasoning-output
5313-normalize-translations
feat/memory-translations
5305-lemonade-embedding-engine-swallows-errors-falsely-reports-documents-as-embedded
5060-bug-agent-interactions-agent-are-not-persisted-to-thread-history-via-api
pptx-subagent
feat-render-images-from-mcp-tool-results
stt-provider-expansion-openai-api-compatible
feat-file-search-agent-tool
feat-native-embedder-job-queue
5189-normalize-translations
feat-file-search-agent-tool-translations
i18n-eslint
5140-auto-migration
5112-bug-openrouter-failed-message-bug
3506-feat-parameters-for-openrouter-models
4992-feat-preserve-scroll-position
4973-bug-markdown-numbered-list-display-in-reasoning-pane
desktop
4938-bug-pending-chat-rerendering-ui-bug
quickstart-env
node-llama-cpp-in-container-cuda
node-llama-cpp-in-container
ollama-in-container
4817-feat-set-cooldown-per-mcp-server
4845-keyboard-shortcuts-to-navigate-in-chat
4844-feat-reorder-threads-by-latest-interaction
standardize-username-constraints-normalize-translations
4792-feat-refactor-workspacepfp-image
1382-embed-ip-improvements
1382-bug-embed-api-improvements
refactor-eslint-frontend
4687-feat-refactor-vector-db-providers
4615-feat-disable-apidocs-with-environment-variable
4559-feat-agent-web-search-enable-ordering-of-results
4599-bug-ollama-race-condition-bug
4572-bug-lmstudio-provided-llm-stopped-working-with-anything-llm-after-upgrading-to-190
4508-agent-youtube-transcript-analysis
4497-feat-workspace-names
frontend-eslint
ollama-lmstudio-auto-context-window
4431-validate-vector-database-connectioN
2019-slash-command-keyboard-selection
microsoft-foundry-provider
4431-validate-vector-database-connection
4325-sys-prompt-var-improvements
3209-feat-apiv1workspacestream-chat-sources-citations
4210-bug-voice-to-text-overwrite
4136-feat-jan-as-a-backend-server-option
4172-feat-openai-o3-support
1.8.3-rerelease
web-push-notifications-service
tasks
3955-feat-jinaai-embedder-provider-support
3921-feat-agent-skills-uiux-improvements
3901-bug-validfunccall-checks-optional-arguments
keyboard-dev
1787-custom-roles-and-permissions
add-jira-slack-data-connector
office-extension-wip
lightmode-dropdown-color-update
3586-bug-agent-flow-function-description-provided-by-user-is-not-seen-in-the-llm-query
3463-bug-agent-continues-to-run-if-request-failed-even-after-exit
3439-feat-call-variables-within-the-flow-api-block-url-field
3282-manager-view-models-workspace
3280-token-counting-server-side-truncation-improvements
3147-bug-embedded-chat-widget---not-considering-query-mode-option-always-working-in-chat-mode
2995-feat-disable-temperature-setting-for-deepseek-r1-deepseek-reasoner-model
2827-feat-perplexity-citations
2866-feat-finally-a-gemini-models-endpoint
2647-feat-hpp-header-for-a-c++-code-file-mime-addition
lancedb-revert
1656-feat-implement-tooltip-ui-designs
2011-feat-bump-perplexity-models
1873-feat-auto-add-and-watch-folder-for-document-uploads
1297-feat-gemini-agent-support
1759-bug-ui-bug-fixes
1686-feat-implement-winston-for-logging
1536-bug-toggling-on-users-can-delete-workspaces-does-not-take-effect
agent-ui-mobile-styles
1522-feat-chromadb-support
1595-bug-unable-to-get-live-web-search-and-browsing-agent-working-using-google-custom-search-engine-error-getaddrinfo-enotfound-http-errno-3008
1582-bug-lm-studio-does-not-allow-for-different-model-selection
1312-bug-usernames-should-not-be-case-sensitive-when-logging-in
1029-feat-hf-serverless-inference-api
1086-feat-implement-normalized-input-fields
knowledge-graph-support
644-bug-uploaded-file-name-does-not-match-the-displayed-file-name-after-the-upload
v1.15.0
v1.14.2
v1.14.1
v1.14.0
v1.13.0
v1.12.1
v1.12.0
v1.11.2
v1.11.1
v1.11.0
v1.10.0
v1.9.1
v1.9.0
v1.8.5
v1.8.4
v1.8.3
v1.8.2
v1.8.1
v1.8.0
v1.7.8
v1.7.6
v1.7.5
v1.7.4
v1.4.0
v1.3.0
v1.2.4
v1.2.3
v1.2.2
v1.2.1
v1.2.0
v1.1.1
v1.1.0
v1.0.0
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
question
stage: specifications
wontfix
Mirrored from GitHub Pull Request
Milestone
No items
No Milestone
Projects
Clear projects
No project
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: Mintplex-Labs/anything-llm#706
Reference in New Issue
Block a user
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
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?
Originally created by @flefevre on GitHub (Apr 20, 2024).
Original GitHub issue: https://github.com/Mintplex-Labs/anything-llm/issues/1153
What would you like to see?
it would be great to be able to configure AnythingLLM with a Vllm model
https://github.com/vllm-project/vllm
@mkhludnev commented on GitHub (Apr 24, 2024):
I were able to use vllm selecting Local AI in AnythingLLM LLM Settings.
Enjoy.
@flefevre commented on GitHub (Apr 26, 2024):
Thanks for your advice.
I have tested but i failed.
I do confirm vllm instance is working fine since
https://vllm-mixtral.myserver.fr/v1/models
{"object":"list","data":[{"id":"mistralai/Mixtral-8x7B-Instruct-v0.1","object":"model","created":1714112327,"owned_by":"vllm","root":"mistralai/Mixtral-8x7B-Instruct-v0.1","parent":null,"permission":[{"id":"modelperm-76d249bf4f0e44698e3bb82a41424183","object":"model_permission","created":1714112327,"allow_create_engine":false,"allow_sampling":true,"allow_logprobs":true,"allow_search_indices":false,"allow_view":true,"allow_fine_tuning":false,"organization":"*","group":null,"is_blocking":false}]}]}
i have putted in the config: LocalAI with http://vllm-mistral:5002/v1
Anything is able to retrieve the model.
But when I tried to engage chat, i got an error:vCould not respond to message.
Request failed with status code 400
Looking to the log of Anythingllm , I ahev the following trace:
I would appreciate your help.
Thanks in advance.
Francois, from France
On Wed, Apr 24, 2024 at 2:52 PM Mikhail Khludnev @.***>
wrote:
--
@flefevre commented on GitHub (Apr 26, 2024):
If it could help you in your analysis:
it seems to ask for
https://vllm-mixtral.myserver.fr/v1/chat/completions
but when i go this url i got:
{"detail":"Method Not Allowed"}it is a problem of api between vllm and anythingllm ?
@timothycarambat commented on GitHub (Apr 26, 2024):
That endpoint is POST only, not GET - which is part of the reason you got method not allowed when going to the URL directly.
@alceausu commented on GitHub (Apr 28, 2024):
I have the same issue, no mather the integration (Local AI or Generic OpenAI).
The vllm server replies with:
ERROR` serving_chat.py:60] Error in applying chat template from request: Conversation roles must alternate user/assistant/user/assistant/...INFO:` "POST /v1/chat/completions HTTP/1.1" 400 Bad Request@flefevre commented on GitHub (Apr 28, 2024):
Dear all,
I have tested again and no way to use vllm directly even if I have exposed the port through the docker configuration.
Could you share exactly how did you do it?
Thanks again
@mkhludnev commented on GitHub (Apr 28, 2024):
@flefevre once again, I did it twice it works. Maybe it's a container connectivity issue? I remember that I use curl to check connectivity between containers. Can you tell how your containers,hosts and processes are aligned?
The simplest approach for me were launch vllm and AnythingLLM as a sibling containers under the single docker-compose.yml config and point anithingllm to vllm via container name.
Another approach was to run vllm in a host, then launch AnythingLLM via docker and point to vllm via
host.docker.internalbut iirc is a Docker Desktop only feature.@alceausu commented on GitHub (Apr 29, 2024):
It seems these are two different issues, one related to connectivity, and the other one on format.
Related to the request format, the anything-llm can reach vllm, but vllm throws an error of '400 Bad request'.
ERROR` serving_chat.py:60] Error in applying chat template from request: Conversation roles must alternate user/assistant/user/assistant/...For some hints on why, see vllm discussion Mixtral instruct doesn't accept system prompt
Is there a way to modify the template on the anything-llm side?
@flefevre commented on GitHub (May 1, 2024):
Dear all,
Normally i have simplified the test.
Docker configuration
Docker validation
When I connect to the anythingllm container, i am able to retrieve model of vllm through the command:
anythingllm@6de6c5255f33:~$ curl http://vllm-mixtral:5002/v1/completions -H "Content-Type: application/json" -d '{"model": "mistralai/Mixtral-8x7B-Instruct-v0.1", "prompt": "San Francisco is a", "max_tokens": 7,"temperature": 0}' {"id":"cmpl-0df1e0e95b4c46a78632936ba277e3ef","object":"text_completion","created":1714551853,"model":"mistralai/Mixtral-8x7B-Instruct-v0.1","choices":[{"index":0,"text":" city that is known for its steep","logprobs":null,"finish_reason":"length","stop_reason":null}],"usage":{"prompt_tokens":5,"total_tokens":12,"completion_tokens":7}}anythingllm@6de6c5255f33:~$Anythingllm Webui configuration
I am able to configure the default LLM preference by setting
Anythingllm Webui Test
When i create a workspace, open a new thread, and ask something, I got everytime a
Could not respond to message. Request failed with status code 400When i look at the Anythingllm logs, i have the following trace
httpVersionMajor: 1, httpVersionMinor: 1, httpVersion: '1.1', complete: true, rawHeaders: [Array], rawTrailers: [], joinDuplicateHeaders: undefined, aborted: false, upgrade: false, url: '', method: null, statusCode: 400, statusMessage: 'Bad Request', client: [Socket], _consuming: false, _dumped: false, req: [ClientRequest], responseUrl: 'http://vllm-mixtral:5002/v1/chat/completions', redirects: [], [Symbol(kCapture)]: false, [Symbol(kHeaders)]: [Object], [Symbol(kHeadersCount)]: 10, [Symbol(kTrailers)]: null, [Symbol(kTrailersCount)]: 0 } }, isAxiosError: true, toJSON: [Function: toJSON]Analysis
I agree with @alceausu , the problem seems not to come from a mis configuration of docker / vllm / anythingllm.
It seems more related to a misconfiguration between anlythingllm and vllm in the usage of a specific model which in my case mixtral8x7b.
A solution could be to be able to understand the specificity of each vllm/model system prompt, as proposed by @alceausu https://github.com/vllm-project/vllm/discussions/2112
Or perhaps to use a model proxy such as Litellm that will encapsulate the model interaction based on an uniform api which is inspired by openai.
I have created the following Feature proposal here #1154 , I do think it is the good solution.
Do you agree?
If yes, my ticket should perhaps invalidated since Anythingllm is compatible with vllm but not with all models served by vllm.
Mixtral8x7b is really a good model. It will be perfect to access to it through a proxy such as Litellm, ensuring the developer of Anythingllm do not have to adapt all their backend solution for prompting for each model.
Thanks for for your expertise.
@timothycarambat commented on GitHub (Jul 10, 2025):
Closin as not planned for now since you can leverage the Generic OpenAI connector provider to service VLLM endpoints since they are OpenAI compat
[FEAT]: Integration of Vllm as model serverto [GH-ISSUE #1153] [FEAT]: Integration of Vllm as model server@mekler22 commented on GitHub (Apr 7, 2026):
Found the solution for this. You need to run seperate dockers for each one (vllm, and anythingllm), but they both need to share the same network. You may need to use sudo chown -R 1000:1000 /path/to/docker and sudo chmod -R 775 /path/to/docker to make sure the docker gets all the write rights it needs.
This is the anythingllm docker-compose (running as a portainer stack):
version: '3.8'
services:
anythingllm:
image: mintplexlabs/anythingllm:latest
container_name: anythingllm
ports:
- "3001:3001"
cap_add:
- SYS_ADMIN
environment:
- STORAGE_DIR=/app/server/storage
- JWT_SECRET=20characterssecretgenerated
- LLM_PROVIDER=generic-openai
- GENERIC_OPEN_AI_BASE_PATH=http://vllm:8000/v1
- GENERIC_OPEN_AI_MODEL_PREF=Qwen/Qwen3-8B-AWQ
- GENERIC_OPEN_AI_MODEL_TOKEN_LIMIT=8192
- GENERIC_OPEN_AI_API_KEY=sk-123abc
- EMBEDDING_ENGINE=ollama
- EMBEDDING_BASE_PATH=http://OLLAMA:11434
- EMBEDDING_MODEL_PREF=nomic-embed-text
- EMBEDDING_MODEL_MAX_CHUNK_LENGTH=8192
- VECTOR_DB=lancedb
- WHISPER_PROVIDER=local
- TTS_PROVIDER=native
- PASSWORDMINCHAR=8
#
volumes:
- /volume1/docker/anythingllm:/app/server/storage
restart: always
networks:
- ollama_default
extra_hosts:
- "host.docker.internal:host-gateway"
networks:
ollama_default:
external: true
And this is the docker-compose for vllm (running as a portainer stack):
version: "3.9"
services:
vllm:
image: vllm/vllm-openai:v0.8.5
container_name: vllm
restart: always
ports:
- "8001:8000"
environment:
- HUGGING_FACE_HUB_TOKEN=hf_xxxxxx
- VLLM_ENABLE_CUDA_COMPATIBILITY=1
volumes:
- /volume1/docker/vllm/cache:/root/.cache/huggingface
ipc: host
deploy:
resources:
reservations:
devices:
- driver: nvidia
count: 1
capabilities: [compute,video,graphics,utility]
command: >
--model Qwen/Qwen3-8B-AWQ
--served-model-name Qwen/Qwen3-8B-AWQ
--enable-auto-tool-choice
--tool-call-parser hermes
--max-model-len 16384
--gpu-memory-utilization 0.85
--trust-remote-code
--enforce-eager
networks:
- ollama_default
extra_hosts:
- "host.docker.internal:host-gateway"
networks:
ollama_default:
external: true
This is engineered (through trial and error) for my own synology nas based server with RTX 3060 12g card, and driver limitation for Cuda 12.4 - that's why the vllm version is limited to 0.8.5 - as the newer versions are running with Cuda 13.0. Also, it limits which models you can use as some newer functions are not available so certain models simply will not run or require command parameters changes. Also notice that my embedding is running off my Ollama docker - so you may want to change that according to what you have. And of course, the relevant folders need to be created in advance. However, it all works great on my hardware. This is done with pieces of code that I found in vllm, and anythingllm related sites, with A LOT of tweaking.
I find that Vllm+Anythingllm is definitely faster in responding than Ollama+Openwebui. But.. with the former I can use latest images without issue, while with the latter I am more limited. Also downloading and switching between models is MUCH easier with Ollama+Openwebui.
Anyways, Enjoy! I hope it helps (and don't forget to enter your own HF token before running the stack).