Users with VIEWER role unable to see respective agents under 'My Agents'

[dareima]

What happened?

After migrating our existing agents to the new access model in LibreChat using the migration script, I assigned the VIEWER role for everyone on most of them, so regular users would only see them and be able to use them but not do anything else with them.

I noticed that it didn't work and no one saw the agents any longer under My Agents.
Only when I updated the role to at least EDITOR, the agents appear again.

I also checked with newly created agents that were only created after the update to 0.8.0-rc3, but that didn't change the fact that no one sees these agents when only VIEWER is assigned.

I also doesn't make a difference whether VIEWER is assigned for EVERYONE or for a single user.

See the Steps to Reproduce section for more details.

I wanted to report this before 0.8.0 gets released, in case this is not yet known.

Version Information

0.8.0-rc3 (Docker, pulled on September 1st, 2025)

Steps to Reproduce

1. Make sure to log in to LibreChat with an ADMIN account
2. Create a new agent in the Agent Builder (no specific configurations required)
3. Share the agent with either everyone or with a test user and assign the role VIEWER
4. Log in with the test user and check your available agents under My Agents (top left)
5. You won't see the new agent in the agent selection
6. However, try typing @ in the prompt box and you will see the agent there (selectable & usable)
7. Once selected via @, the agent now also appears under My Agents, but only as long as the website isn't refreshed

Note: This is unrelated to running the migration script for agents. I ran the migration script before and after doing this kind of test. It makes no difference.

What browsers are you seeing the problem on?

Chrome

Relevant log output

There aren't really logs that can be correlated to this issue. When I set permissions on agents for the first time after restarting LibreChat, I am seeing this message though:

debug: MongoDB transactions not supported (transaction error): Transaction numbers are only allowed on a replica set member or mongos

When the user selects the "invisible" agent via '@', the debug console reads this:

[canAccessResource] Resolving agent custom ID agent_0ueZ2xZU_uTj7g0B_xS1t to ObjectId
[canAccessResource] Resolved agent agent_0ueZ2xZU_uTj7g0B_xS1t to ObjectId 688a3b940120878103b9c460
[canAccessResource] User 68b581d934a92e885a304510 has permission 1 on agent agent_0ueZ2xZU_uTj7g0B_xS1t (688a3b940120878103b9c460)

which I read as correct, as VIEWER == 1, EDITOR ==2 and so on.

Screenshots

RBAC Test Agent is shared with everyone using the VIEWER role

The RBAC Test Agent isn't visible for anyone under My Agents

Using @ in the prompt box however does in fact show the RBAC Test Agent (selectable & usable)

Code of Conduct

• I agree to follow this project's Code of Conduct

[danny-avila]

Hi @dareima this is actually expected behavior if you have the marketplace enabled. This is to possibly account for many shared agents, and to allow the user easy visibility of their own agents still.

If only viewer permission is granted then it's delegated to marketplace for access.

[dareima]

@danny-avila thanks so much for clearing this up for me.

I now see that "My Agents" is meant literally as in "only my own agents or the ones I can edit".

I like the idea of seeing VIEWER role agents on the marketplace. The only thing that strikes me as rather non-intuitive is the way users need to go to create a new conversation with such agents (which might a thing they do quite often).

From observing how most of our users are using LibreChat (when ModelSpecs are not enabled), they would go over the selection of endpoints and agents in the top left menu.

In this new version they'd have to go through the marketplace or select an existing chat with the respective agent and create a new conversation.

Also, I'd need to test which methods remain when the marketplace would be disabled for users.

I understand the overall idea of this and don't have a proper answer other than to educate users how the new version works.
I suppose an additional new menu in the top left selection wouldn't cut it either, as you'd have to list all agents to which viewer access exists, which kind of eliminiates the purpose of looking at an overflowing list of agents.

[danny-avila]

I think it's a good discussion because we can certainly improve UX here.

If having the full list of agents in the LLM Select is preferred, then we could add an easy option for that.

Model specs can also already be leveraged to highlight specific agents along with "My Agents".

A "Favorites" agent list would also help, which can include any agent the user has access to.

[dareima]

These are good ideas. Configurable options are always great.

Like in such a case where an implementation of LibreChat doesn't have a lot of agents and all viewer role agents in LLM Select wouldn't spoil the list.

The ModelSpec option is already very handy and well used in our scenarios as well.

Favorites sound just perfect!

Thanks so much for taking that into account.