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 #3423] [FEAT]: API for assigning a thread before calling /v1/openai/chat/completions #2208

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

Originally created by @GPTLocalhost on GitHub (Mar 8, 2025).
Original GitHub issue: https://github.com/Mintplex-Labs/anything-llm/issues/3423

What would you like to see?

Currently there are several useful API endpoints for workspaces and threads. But, is it possible to have an API to assign the thread (and its workspace) before calling OpenAI-compatible endpoints? We are trying to integrate AnythingLLM with Microsoft Word like the following. Implementing such an API could facilitate deeper integration and potentially increase user adoption of AnythingLLM. Thank you for your consideration or advice.

https://youtu.be/-Br_iDDVJBY

Originally created by @GPTLocalhost on GitHub (Mar 8, 2025). Original GitHub issue: https://github.com/Mintplex-Labs/anything-llm/issues/3423 ### What would you like to see? Currently there are several useful API endpoints for workspaces and threads. But, is it possible to have an API to assign the thread (and its workspace) before calling OpenAI-compatible endpoints? We are trying to integrate AnythingLLM with Microsoft Word like the following. Implementing such an API could facilitate deeper integration and potentially increase user adoption of AnythingLLM. Thank you for your consideration or advice. https://youtu.be/-Br_iDDVJBY
yindo added the enhancementfeature request labels 2026-02-22 18:28:39 -05:00
yindo closed this issue 2026-02-22 18:28:39 -05:00
yindo commented 2026-02-22 18:28:39 -05:00
Author
Owner
Copy Link
Copy Source

@timothycarambat commented on GitHub (Mar 9, 2025):

Are you not unable to use the workspace/thread endpoints? Those can CRUD threads that you can then manage if you nee those threads to show up in the UI as well. If you just want "threading" but without having to manage threads you can just as easily use the sessionId param in the workspace/*/chat endpoints. Obviously not OpenAI compatible.

Since OpenAI compatibility will break if we start adding custom fields, there isn't much wiggle room there as some SDKs will throw an error if our request/response body is not 100% comforming

@timothycarambat commented on GitHub (Mar 9, 2025): Are you not unable to use the workspace/thread endpoints? Those can CRUD threads that you can then manage if you nee those threads to show up in the UI as well. If you just want "threading" but without having to manage threads you can just as easily use the `sessionId` param in the `workspace/*/chat` endpoints. Obviously not OpenAI compatible. Since OpenAI compatibility will break if we start adding custom fields, there isn't much wiggle room there as some SDKs will throw an error if our request/response body is not 100% comforming
yindo changed title from [FEAT]: API for assigning a thread before calling /v1/openai/chat/completions to [GH-ISSUE #3423] [FEAT]: API for assigning a thread before calling /v1/openai/chat/completions 2026-06-05 14:45:11 -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#2208
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?