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:28:58 -05:00 by yindo
·
1 comment
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
No Label
possible bug
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#2280
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 @johnec2 on GitHub (Mar 25, 2025).
Original GitHub issue: https://github.com/Mintplex-Labs/anything-llm/issues/3538
How are you running AnythingLLM?
Local development
What happened?
Hello,
I am currently using the following stack with AnythingLLM:
AI Model: Llama 3.2: 1b
AI Model Provider: Ollama (version 0.5.12)
Vector DB: Qdrant (version 1.13.4)
Embed Model: nomic-embed-text:latest
UI Tool: AnythingLLM (version 0.2.0)
Configuration:
Chunk Size: 2000
Chunk Overlap: 200
Threshold Similarity Score: >= 0.25
I have a JSON file that contains structured questions and answers. After uploading the file to AnythingLLM, the responses are not being retrieved exactly as they appear in the file. Instead, additional information is being added, or generalized answers are being displayed.
The JSON file is structured as follows:
{
"id": "01",
"module": "Facility",
"category": "Add Facility to Complex",
"role": ["admin", "team staff"],
"questions": [
"How can I add facilities to a complex?"
],
"answer": "Facilities can be added to a complex either by creating a new complex or for an existing complex. To do so: Navigate to Facilities > All Complexes from the left menu. From the list, choose the complex to add facility. In the Actions column, click the vertical dots and select Update Complex. In the complex details page, select the Facilities tab. In the Facilities tab, select either Add 1 Facility or Add 5 Facilities to add facilities to the complex. While adding a facility, choose either Create New Facility or Select an Existing Facility. Click the Save button. Note: When creating a new facility inside a complex, the facility will inherit the complex properties (e.g., details, address, and timings). These properties can later be updated individually through the Update Facility page.",
"type": "verbatim"
}
Despite specifying the "type": "verbatim", the response is still being paraphrased. Additionally, the introductory portion of the answer, "Facilities can be added to a complex either by creating a new complex or for an existing complex...", is missing. To address this, I added an introduction field to the data like so:
{
"id": "01",
"module": "Facility",
"category": "Add Facility to Complex",
"role": ["admin", "team staff"],
"questions": [
"How can I add facilities to a complex?"
],
"answer": "To do so: Navigate to Facilities > All Complexes from the left menu. From the list, choose the complex to add facility. In the Actions column, click the vertical dots and select Update Complex. In the complex details page, select the Facilities tab. In the Facilities tab, select either Add 1 Facility or Add 5 Facilities to add facilities to the complex. While adding a facility, choose either Create New Facility or Select an Existing Facility. Click the Save button. Note: When creating a new facility inside a complex, the facility will inherit the complex properties (e.g., details, address, and timings). These properties can later be updated individually through the Update Facility page.",
"introduction": "Facilities can be added to a complex either by creating a new complex or for an existing complex.",
"type": "verbatim"
}
However, this did not change the result. I also modified the prompt in Chat Settings > Prompt > Chat Mode > Query to the following:
"You are a system that provides answers from a document. For entries with "type": "verbatim", output the "introduction" field (if present) followed by the "answer" field, exactly as written. Do not paraphrase, summarize, or reformat the text (e.g., do not convert paragraphs to lists). Do not add any additional text beyond what is in the "introduction" and "answer" fields, such as extra introductions or conclusions. Preserve all whitespace, punctuation, and structure as it appears in the file."
Unfortunately, this also did not resolve the issue.
Could you provide a solution to ensure that the responses are fetched exactly as they appear in the file, without any modifications or added information?
Are there known steps to reproduce?
No response
@timothycarambat commented on GitHub (Mar 26, 2025):
Your model is doing the paraphrasing, not AnythingLLM.
This model is very small and unless you specified pulling
Q8in ollamaollama pull llama3.2:1b-text-q8_0you are using theq4version of the model. So now not only do you have a small param model, but is is also compressed heavily. So it is no wonder why it does not follow instructions!Use a larger param model at Q4, or attempt to pull the Q8 version of 3.2:1b - I do think that even the 1B @ Q8 will still perform poorly here though. I would certainly recommend a larger model for this, smaller models almost always ignore specific prompt instructions.
If we have the context needed in the window, it is solely up to the model to then return the right information. That being said, verbatim recall is not an LLM strong suite. It sounds like you are doing just retrieval for RAG and dont even need an LLM in the middle though?
[BUG]: Response not retrieved exactly as in the uploaded JSON fileto [GH-ISSUE #3538] [BUG]: Response not retrieved exactly as in the uploaded JSON file