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 #3428] Integration with Microsoft Word by selecting both workspace and thread #2210

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

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

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

Thanks for your helpful guidance.

use the sessionId param in the workspace/*/chat endpoints. Obviously not OpenAI compatible

If so, we plan to migrate OpenAI compatible code and parameters to the "workspace/*/chat" endpoints. In this case, is there any sample code you can advise? We are working on integrating AnythingLLM with Microsoft Word locally like this:

https://youtu.be/-Br_iDDVJBY

The thread is always the "default" one when using OpenAI-compatible endpoints. It will be great to have a deeper integration for selecting both workspace and thread. This is the reason why asking. Thanks again.

Originally posted by @timothycarambat in #3423

Originally created by @GPTLocalhost on GitHub (Mar 9, 2025). Original GitHub issue: https://github.com/Mintplex-Labs/anything-llm/issues/3428 > 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 Thanks for your helpful guidance. > use the sessionId param in the workspace/*/chat endpoints. Obviously not OpenAI compatible If so, we plan to migrate OpenAI compatible code and parameters to the "workspace/*/chat" endpoints. In this case, is there any sample code you can advise? We are working on integrating AnythingLLM with Microsoft Word locally like this: https://youtu.be/-Br_iDDVJBY The thread is always the "default" one when using OpenAI-compatible endpoints. It will be great to have a deeper integration for selecting both workspace and thread. This is the reason why asking. Thanks again. _Originally posted by @timothycarambat in [#3423](https://github.com/Mintplex-Labs/anything-llm/issues/3423#issuecomment-2708784435)_
yindo closed this issue 2026-02-22 18:28:40 -05:00
yindo commented 2026-02-22 18:28:40 -05:00
Author
Owner
Copy Link
Copy Source

@shatfield4 commented on GitHub (Mar 20, 2025):

You should be able to access the swagger documentation and this would be the endpoint you would want to use http://localhost:3001/api/docs/#/Workspaces/post_v1_workspace__slug__stream_chat for streaming chats to a specific workspace.

The documentation will tell you what response you can expect back from the API and your code will just need to handle the stream chunks of data.

@shatfield4 commented on GitHub (Mar 20, 2025): You should be able to access the swagger documentation and this would be the endpoint you would want to use http://localhost:3001/api/docs/#/Workspaces/post_v1_workspace__slug__stream_chat for streaming chats to a specific workspace. The documentation will tell you what response you can expect back from the API and your code will just need to handle the stream chunks of data.
yindo changed title from Integration with Microsoft Word by selecting both workspace and thread to [GH-ISSUE #3428] Integration with Microsoft Word by selecting both workspace and thread 2026-06-05 14:45:12 -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
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#2210
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?