[Question]: Can I disable the agent versioning?

[mansiibm]

Hey , thanks for the new updates ,they are wonderful, but is there a way that the agent versioning can be disabled?

[danny-avila]

Not at the moment, @mawburn do you think it would be easy to implement?

[mansiibm]

Heyy!! just to follow up, will disabling agent versioning be considered for future updates?

[mawburn]

Yeah, I think it would be easy.

Sorry I missed this due to a work trip.

[mawburn]

@mansiibm I wouldn't mind doing this, but can you tell me the use case for it? Like why do you want them disabled?

I know there is a problem with versions potentially filling up the document in Mongo, which I want to fix, but we've only had this happen once at our org and that person had a very long prompt and >200 versions. But other than that, I'm curious what you want this for.

Like, do you need it globally or just per agent? I think per agent would make the most sense but your use case may want a global method.

[mawburn]

This was being triggered when users were updating the models/providers? It should be comparing everything to avoid conflicts.

I could probably just get rid of this error and not check anything.

[mansiibm]

Hi @mawburn thank you so much for replying :). Now post 7.9 we are using this tag- ghcr.io/danny-avila/librechat-dev-api:545a9099537c85ba1bd942b9f99215ecf5e6ee15 , the issue we were facing were -

1. I created an agent now-

2. This has no chain of agents -

3. I added an agent to create chained agent-

4. So now two versions are visible and the topmost is active -

5. Then I ask it to restore to the first version and message pops up, that it is restored

6. If I refresh and check it's still the new version -

For full-proof purpose I have included the time stamp at the bottom of the images :).

So now the version selection is not working.

Then earlier, when I had raised the ticket the issues users were facing were -

1. If the user was removing or adding a tool and saving, he/she was getting the warning for the duplicates detected.
2. If the user tried to restore the version the above-described issue was appearing. No change in version.

Hence, we wished to disable it altogether :).

[mawburn]

I'm not seeing this behavior on main at all. Am I doing something wrong?

Screen.Recording.2025-07-31.at.9.06.54.AM.mov

[mansiibm]

Hi mawburn thanks a lot for sharing this video, you are right, this is working correctly as you explained. The version is working, but still may I please request you if versioning can be kept configurable :) .

[mansiibm]

Hi just checking for a follow up :)