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 #3629] [FEAT]: Accessing Full Feature Set via UI-Exposed API — Request for Guidance #2342

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

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

Hi @timothycarambat ,

I noticed that AnythingLLM currently provides two sets of APIs:

The Developer API

The API used internally for the UI

We’re looking to build a custom tool or UI that integrates deeply with AnythingLLM. However, it seems the UI-facing API may not offer access to all the features available in the full Developer API.

Request:

Is it possible to leverage the existing UI-facing API to implement a tool that can access all of AnythingLLM’s core features? If not directly, are there any recommended workarounds or best practices you could suggest to help achieve this?

Use Case:

We’re aiming to create a tool or UI that mirrors the full functionality of AnythingLLM as closely as possible, ideally without relying solely on the Developer API.

Reference:

We’ve discussed this briefly on Discord and reviewed the feedback shared here:
🔗 https://discord.com/channels/1114740394715004990/1341092411165773864/1360105808012247102
We understand the technical limitations and would appreciate any further suggestions or alternatives you might recommend.

Request for Guidance:

@timothycarambat , would love your input on whether this approach is feasible and how best to go about it with the current architecture.

We're also open to continuing the discussion on Discord if that’s easier for more in-depth guidance.

Thanks!

Originally created by @avinashkurup on GitHub (Apr 11, 2025). Original GitHub issue: https://github.com/Mintplex-Labs/anything-llm/issues/3629 Hi @timothycarambat , I noticed that AnythingLLM currently provides two sets of APIs: The Developer API The API used internally for the UI We’re looking to build a custom tool or UI that integrates deeply with AnythingLLM. However, it seems the UI-facing API may not offer access to all the features available in the full Developer API. Request: Is it possible to leverage the existing UI-facing API to implement a tool that can access all of AnythingLLM’s core features? If not directly, are there any recommended workarounds or best practices you could suggest to help achieve this? Use Case: We’re aiming to create a tool or UI that mirrors the full functionality of AnythingLLM as closely as possible, ideally without relying solely on the Developer API. Reference: We’ve discussed this briefly on Discord and reviewed the feedback shared here: 🔗 https://discord.com/channels/1114740394715004990/1341092411165773864/1360105808012247102 We understand the technical limitations and would appreciate any further suggestions or alternatives you might recommend. Request for Guidance: @timothycarambat , would love your input on whether this approach is feasible and how best to go about it with the current architecture. We're also open to continuing the discussion on Discord if that’s easier for more in-depth guidance. Thanks!
yindo added the enhancementfeature request labels 2026-02-22 18:29:16 -05:00
yindo closed this issue 2026-02-22 18:29:16 -05:00
yindo commented 2026-02-22 18:29:16 -05:00
Author
Owner
Copy Link
Copy Source

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

For something like this, you are far better off using a fork with a custom frontend replaced with what you like. All of the internal endpoints are for exactly that, internal!

There is no best practice to enable this in any way that would be rationally maintainable since overloading of the UI endpoints via a 3rd party is simple not something we are going to long term support since we should be able to change that at all without blowing up 3rd party integrations.

The safest way for this is to simply create a fork you maintain, then you can use whatever styling or frontend you like and not have to worry about the frontend changing and breaking your custom application.

@timothycarambat commented on GitHub (Apr 11, 2025): For something like this, you are far better off using a fork with a custom `frontend` replaced with what you like. All of the internal endpoints are for exactly that, internal! There is no best practice to enable this in any way that would be rationally maintainable since overloading of the UI endpoints via a 3rd party is simple not something we are going to long term support since we should be able to change that at all without blowing up 3rd party integrations. The safest way for this is to simply create a fork you maintain, then you can use whatever styling or frontend you like and not have to worry about the frontend changing and breaking your custom application.
yindo changed title from [FEAT]: Accessing Full Feature Set via UI-Exposed API — Request for Guidance to [GH-ISSUE #3629] [FEAT]: Accessing Full Feature Set via UI-Exposed API — Request for Guidance 2026-06-05 14:45:59 -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#2342
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?