Mintplex-Labs/anything-llm
1
0
Fork 0
mirror of https://github.com/Mintplex-Labs/anything-llm.git synced 2026-07-21 01:25:28 -04:00
Code Issues 328 Packages Projects Releases 10 Wiki Activity

[GH-ISSUE #3604] [FEAT]: Chat ID available for agent skills and flows #2326

New Issue
Open
opened 2026-02-22 18:29:11 -05:00 by yindo · 2 comments
yindo commented 2026-02-22 18:29:11 -05:00
Owner
Copy Link
Copy Source

Originally created by @Filaton on GitHub (Apr 7, 2025).
Original GitHub issue: https://github.com/Mintplex-Labs/anything-llm/issues/3604

What would you like to see?

For my API use by an agent I wanted to add some caching logic and other stuff, that needs to get the information in which chat it is right now, so like a unique chat/user id. But to send this to my API I need to have access to something like this in the agent skill and flows, for example that I can send it in the headers etc. This would improve the usability of agents massively for use cases like this, where a chat context is alo important for apis my agent is using.

Originally created by @Filaton on GitHub (Apr 7, 2025). Original GitHub issue: https://github.com/Mintplex-Labs/anything-llm/issues/3604 ### What would you like to see? For my API use by an agent I wanted to add some caching logic and other stuff, that needs to get the information in which chat it is right now, so like a unique chat/user id. But to send this to my API I need to have access to something like this in the agent skill and flows, for example that I can send it in the headers etc. This would improve the usability of agents massively for use cases like this, where a chat context is alo important for apis my agent is using.
yindo added the enhancementfeature request labels 2026-02-22 18:29:11 -05:00
yindo commented 2026-02-22 18:29:11 -05:00
Author
Owner
Copy Link
Copy Source

@timothycarambat commented on GitHub (Apr 7, 2025):

This sounds like something better suited for a custom fork of AnythingLLM. Until the chat is completed we would not yet have its known database ID. Kind of like a post-chat webhook is what this sounds like to where on each agent chat conclusion, an endpoint could be hit to forward this information.

Am i understanding this correctly?

@timothycarambat commented on GitHub (Apr 7, 2025): This sounds like something better suited for a custom fork of AnythingLLM. Until the chat is _completed_ we would not yet have its known database ID. Kind of like a post-chat webhook is what this sounds like to where on each agent chat conclusion, an endpoint could be hit to forward this information. Am i understanding this correctly?
yindo commented 2026-02-22 18:29:11 -05:00
Author
Owner
Copy Link
Copy Source

@Filaton commented on GitHub (Apr 8, 2025):

I was thinking more of a variable or more generally speaking metadata, which can be accessed in existing API calls in the agent flows/skills (before the real LLM request is started), like having information about the workspace and thread and maybe also the user from which the request is coming available for API calls. For example if I want to do an API call to my own service, I want the service to know from which chat the request is coming. With this I could cache data which normally would be retrieved in a resource-intensive process or do monitoring chat wise etc.

I'm not sure if this would be better of in a custom fork, because I see quite a few scenarios where this could be important information for external, but mainly self written APIs/services I want to call.

@Filaton commented on GitHub (Apr 8, 2025): I was thinking more of a variable or more generally speaking metadata, which can be accessed in existing API calls in the agent flows/skills (before the real LLM request is started), like having information about the workspace and thread and maybe also the user from which the request is coming available for API calls. For example if I want to do an API call to my own service, I want the service to know from which chat the request is coming. With this I could cache data which normally would be retrieved in a resource-intensive process or do monitoring chat wise etc. I'm not sure if this would be better of in a custom fork, because I see quite a few scenarios where this could be important information for external, but mainly self written APIs/services I want to call.
yindo changed title from [FEAT]: Chat ID available for agent skills and flows to [GH-ISSUE #3604] [FEAT]: Chat ID available for agent skills and flows 2026-06-05 14:45:55 -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 enhancement feature request
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#2326
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?