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 #5065] [BUG]: Agent invocation not working #4898

New Issue
Closed
opened 2026-06-05 14:50:45 -04:00 by yindo · 7 comments
yindo commented 2026-06-05 14:50:45 -04:00
Owner
Copy Link
Copy Source

Originally created by @cam151 on GitHub (Feb 24, 2026).
Original GitHub issue: https://github.com/Mintplex-Labs/anything-llm/issues/5065

How are you running AnythingLLM?

AnythingLLM desktop app

What happened?

I am running AnythingLLM Desktop on Ubuntu (ARM64) on an NVIDIA DGX-Spark.
AppImage dated: February 24, 2026
LM Studio version: 0.4.4-1
Model: nvidia/nemotron-3-nano

PROBLEM:
When @agent is invoked, the UI correctly shows "Agent invoked" and
a thinking spinner, but the backend AgentHandler never initializes.
Every agent invocation is logged only as sent_chat with zero
[AgentHandler] entries following it.

WHAT THE LOG SHOWS (after @agent invocation):
{"level":"info","message":"[Event Logged] - sent_chat","service":"backend"}
--- nothing after this ---

WHAT SHOULD APPEAR BUT DOES NOT:
[AgentHandler] Start
[AgentHandler] Attached web-browsing plugin to Agent cluster
[AgentHandler] Calling tool: web-browsing

DATABASE IS CORRECTLY CONFIGURED (confirmed via sqlite3):

  • agentProvider: lmstudio
  • agentModel: nvidia/nemotron-3-nano
  • agent_search_provider: tavily-search
  • tavily_api_key: present
  • default_agent_skills: ["create-chart","web-browsing","save-file-to-browser"]
  • disabled_agent_skills: []

ADDITIONAL NOTES:

  • Regular chat works perfectly
  • LM Studio API confirmed working (curl http://127.0.0.1:1234/v1/models returns models)
  • Tavily API confirmed working (direct curl test returns results)
  • Agent was working on the January 16 AppImage version
  • Rolling back is not possible — old AppImage triggers database schema
    reset warning due to migration mismatch
  • This appears to be a regression introduced in the February update

SYSTEM:

  • Hardware: NVIDIA DGX-Spark
  • OS: Ubuntu Linux ARM64 (aarch64)
  • AnythingLLM: Desktop AppImage (Feb 24 2026 build)
  • LM Studio: 0.4.4-1 ARM64

Are there known steps to reproduce?

No response

Originally created by @cam151 on GitHub (Feb 24, 2026). Original GitHub issue: https://github.com/Mintplex-Labs/anything-llm/issues/5065 ### How are you running AnythingLLM? AnythingLLM desktop app ### What happened? I am running AnythingLLM Desktop on Ubuntu (ARM64) on an NVIDIA DGX-Spark. AppImage dated: February 24, 2026 LM Studio version: 0.4.4-1 Model: nvidia/nemotron-3-nano PROBLEM: When @agent is invoked, the UI correctly shows "Agent invoked" and a thinking spinner, but the backend AgentHandler never initializes. Every agent invocation is logged only as sent_chat with zero [AgentHandler] entries following it. WHAT THE LOG SHOWS (after @agent invocation): {"level":"info","message":"[Event Logged] - sent_chat","service":"backend"} --- nothing after this --- WHAT SHOULD APPEAR BUT DOES NOT: [AgentHandler] Start [AgentHandler] Attached web-browsing plugin to Agent cluster [AgentHandler] Calling tool: web-browsing DATABASE IS CORRECTLY CONFIGURED (confirmed via sqlite3): - agentProvider: lmstudio - agentModel: nvidia/nemotron-3-nano - agent_search_provider: tavily-search - tavily_api_key: present - default_agent_skills: ["create-chart","web-browsing","save-file-to-browser"] - disabled_agent_skills: [] ADDITIONAL NOTES: - Regular chat works perfectly - LM Studio API confirmed working (curl http://127.0.0.1:1234/v1/models returns models) - Tavily API confirmed working (direct curl test returns results) - Agent was working on the January 16 AppImage version - Rolling back is not possible — old AppImage triggers database schema reset warning due to migration mismatch - This appears to be a regression introduced in the February update SYSTEM: - Hardware: NVIDIA DGX-Spark - OS: Ubuntu Linux ARM64 (aarch64) - AnythingLLM: Desktop AppImage (Feb 24 2026 build) - LM Studio: 0.4.4-1 ARM64 ### Are there known steps to reproduce? _No response_
yindo added the possible bugneeds info / can't replicateinvestigating labels 2026-06-05 14:50:45 -04:00
yindo closed this issue 2026-06-05 14:50:45 -04:00
yindo commented 2026-06-05 14:50:46 -04:00
Author
Owner
Copy Link
Copy Source

@timothycarambat commented on GitHub (Feb 25, 2026):

Can you confirm if the chat request ever reaches your LMStudio instance in the server logs for LMStudio? Agent chats are still very much sent to LMStudio so you would see them there. I am wondering if they are being dropped or pruned or something on the LMStudio side?

<!-- gh-comment-id:3960153734 --> @timothycarambat commented on GitHub (Feb 25, 2026): Can you confirm if the chat request ever reaches your LMStudio instance in the server logs for LMStudio? Agent chats are still very much sent to LMStudio so you would see them there. I am wondering if they are being dropped or pruned or something on the LMStudio side?
yindo commented 2026-06-05 14:50:46 -04:00
Author
Owner
Copy Link
Copy Source

@cam151 commented on GitHub (Feb 25, 2026):

Chat prompt is delivered to LM Studio and response is generated and delivered back to AnythingLLM. However, if the default agent is engaged, nothing appears in the LM Studio log. In AnythingLLM, the UI indicates that the agent has been invoked, spins for a while and announces "Agent session complete". No response delivered.

<!-- gh-comment-id:3961148336 --> @cam151 commented on GitHub (Feb 25, 2026): Chat prompt is delivered to LM Studio and response is generated and delivered back to AnythingLLM. However, if the default agent is engaged, nothing appears in the LM Studio log. In AnythingLLM, the UI indicates that the agent has been invoked, spins for a while and announces "Agent session complete". No response delivered.
yindo commented 2026-06-05 14:50:46 -04:00
Author
Owner
Copy Link
Copy Source

@cam151 commented on GitHub (Feb 25, 2026):

Hello @timothycarambat, and thank you for the quick response. I've responded to your query in my previous comment. Could you please take another look and possibly reopen this issue? Please let me know if I misunderstood your request. Thanks!

<!-- gh-comment-id:3961218090 --> @cam151 commented on GitHub (Feb 25, 2026): Hello @timothycarambat, and thank you for the quick response. I've responded to your query in my previous comment. Could you please take another look and possibly reopen this issue? Please let me know if I misunderstood your request. Thanks!
yindo commented 2026-06-05 14:50:46 -04:00
Author
Owner
Copy Link
Copy Source

@timothycarambat commented on GitHub (Feb 25, 2026):

We just close issues that dont have an actionable item on them yet to keep the board clean, I still have the notifications on. Are you able to pull the backend logfiles for AnythingLLM Desktop? They are located here https://docs.anythingllm.com/installation-desktop/storage#where-is-my-data-located

There should be at least some error trace or something for why it suddenly drops the socket

<!-- gh-comment-id:3963657784 --> @timothycarambat commented on GitHub (Feb 25, 2026): We just close issues that dont have an actionable item on them yet to keep the board clean, I still have the notifications on. Are you able to pull the `backend` logfiles for AnythingLLM Desktop? They are located here https://docs.anythingllm.com/installation-desktop/storage#where-is-my-data-located There should be at least some error trace or something for why it suddenly drops the socket
yindo commented 2026-06-05 14:50:46 -04:00
Author
Owner
Copy Link
Copy Source

@cam151 commented on GitHub (Feb 26, 2026):

@timothycarambat, Thanks very much for the response and directions to the files. Here are the backend logs for February 24, 25, and 26.

backend-2026-02-24.log

backend-2026-02-25.log

backend-2026-02-26.log

<!-- gh-comment-id:3968300288 --> @cam151 commented on GitHub (Feb 26, 2026): @timothycarambat, Thanks very much for the response and directions to the files. Here are the backend logs for February 24, 25, and 26. [backend-2026-02-24.log](https://github.com/user-attachments/files/25584058/backend-2026-02-24.log) [backend-2026-02-25.log](https://github.com/user-attachments/files/25584087/backend-2026-02-25.log) [backend-2026-02-26.log](https://github.com/user-attachments/files/25584130/backend-2026-02-26.log)
yindo commented 2026-06-05 14:50:46 -04:00
Author
Owner
Copy Link
Copy Source

@cam151 commented on GitHub (Mar 5, 2026):

@timothycarambat, Important Update:

  • Not an AnythingLLM bug
  • Port 3001 conflict with another local server causes silent agent WebSocket timeout
  • AnythingLLM should either make port 3001 configurable or show a better error message when the WebSocket fails
<!-- gh-comment-id:4007729939 --> @cam151 commented on GitHub (Mar 5, 2026): @timothycarambat, Important Update: - **Not an AnythingLLM bug** - Port 3001 conflict with another local server causes silent agent WebSocket timeout - AnythingLLM should either make port 3001 configurable or show a better error message when the WebSocket fails
yindo commented 2026-06-05 14:50:46 -04:00
Author
Owner
Copy Link
Copy Source

@timothycarambat commented on GitHub (Mar 5, 2026):

related to #5114

<!-- gh-comment-id:4008105708 --> @timothycarambat commented on GitHub (Mar 5, 2026): related to #5114
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 investigating needs info / can't replicate 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#4898
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?