Duplicated shared agents not visible to other users due to version history conflict

[benverhees]

What happened?

When duplicating a shared agent, the operation appears to succeed for the original agent creator, but other users cannot see the duplicated agent in their agent list. The duplication creates an agent document with conflicting version history that affects visibility for other users.

Expected behavior:

• When a shared agent is duplicated, the new agent should be visible to all users

Actual behavior:

• The original agent creator sees no issues with the duplication process
• Other users don't see the duplicated agent in their agent list
• The duplicated agent exists in MongoDB but has malformed version structure

Version Information

Repository	Tag	Digest	Created	Size
ghcr.io/danny-avila/librechat-dev	0587a1c	1f53b52d6476	4 days ago	1.89GB
ghcr.io/danny-avila/librechat-rag-api-dev-lite	33a221a6f5f5ee0af03e0cecca2508d9bc1f649b	e03717fc8fc9	5 days ago	2.01GB
ghcr.io/librechat-ai/codesandbox-client/bundler	latest	569b08251638	7 weeks ago	207MB

Steps to Reproduce

1. User A creates an agent and shares it (makes it collaborative/shared)
2. User A duplicates the agent using the duplicate button
3. User A can see the duplicated agent normally
4. User B cannot see the duplicated agent in their agent list
5. Check MongoDB - the duplicated agent exists but has conflicting version data structure

What browsers are you seeing the problem on?

No response

Relevant log output

No relevant logs

Screenshots

No response

Code of Conduct

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

[danny-avila]

When a shared agent is duplicated, the new agent should be visible to all users

This is not expected behavior. A duplicated agent will be treated as a new agent, so it needs to be shared again manually. So no issue there.

Check MongoDB - the duplicated agent exists but has conflicting version data structure

The conflicting version data structure might be a separate issue, @mawburn can you look into this?

[benverhees]

When a shared agent is duplicated, the new agent should be visible to all users

This is not expected behavior. A duplicated agent will be treated as a new agent, so it needs to be shared again manually. So no issue there.

@danny-avila that seems the most reasonable expected behavior to me as well. My assumption that it would need to be visible to other users stems from the fact that after duplicating a shared agent, the user interface indicates that the duplicated agent is shared as well:

Check MongoDB - the duplicated agent exists but has conflicting version data structure

The conflicting version data structure might be a separate issue, @mawburn can you look into this?

[danny-avila]

I see, thanks for sharing that point, will mess around with duplication of agent.

[mawburn]

@benverhees Can you provide a screenshot or sample data of what you mean here? I want to make sure I can recreate it the same way, so am curious what I should be looking for.

The duplication creates an agent document with conflicting version history that affects visibility for other users.

[benverhees]

@mawburn absolutely! Here is the data of a duplicated agent. It has a versions and __v field nested in the version, which are not present in subsequent versions. This could be unrelated to the original issue and might not even be an issue at all, but I noticed that after disabling and reenabling the sharing of the duplicated agent, the latest version doesn't have those fields which lead me to believe it was related.

{
    _id: ObjectId('685c417423209aacb7466ac4'),
    id: 'agent_rvrz04IQKcUVbzUxsJ3ba',
    name: 'Test (6/25/25, 18:35)',
    description: '',
    instructions: '',
    provider: 'azureOpenAI',
    model: 'o3-mini',
    artifacts: '',
    tools: [],
    tool_kwargs: [],
    actions: [],
    author: ObjectId('68270ea4f4e68b63fe4435a8'),
    agent_ids: [],
    isCollaborative: true,
    conversation_starters: [],
    projectIds: [
        ObjectId('67ff818ccb7949447da365b4')
    ],
    versions: [
        {
            name: 'Test (6/25/25, 18:35)',
            description: '',
            instructions: '',
            provider: 'azureOpenAI',
            model: 'o3-mini',
            artifacts: '',
            tools: [],
            tool_kwargs: [],
            agent_ids: [],
            conversation_starters: [],
            projectIds: [
                ObjectId('67ff818ccb7949447da365b4')
            ],
            versions: [
                {
                    artifacts: '',
                    tools: [],
                    name: 'Test',
                    description: '',
                    instructions: '',
                    provider: 'azureOpenAI',
                    model: 'o3-mini',
                    id: 'agent_MC5iDNEPhNreW5QFVcDkJ',
                    createdAt: ISODate('2025-06-25T15:04:53.862Z'),
                    updatedAt: ISODate('2025-06-25T15:04:53.862Z')
                }
            ],
            __v: 0,
            isCollaborative: true,
            id: 'agent_rvrz04IQKcUVbzUxsJ3ba',
            actions: [],
            createdAt: ISODate('2025-06-25T18:35:32.902Z'),
            updatedAt: ISODate('2025-06-25T18:35:32.902Z')
        }
    ],
    __v: 0,
    createdAt: ISODate('2025-06-25T18:35:32.904Z'),
    updatedAt: ISODate('2025-06-25T18:35:32.904Z')
}

[mawburn]

It has a versions and __v field nested in the version, which are not present in subsequent versions.

Interesting, I'll look into this. Thanks. Neither of these should be any of the versions. The first one would blow up the size exponentially and the second isn't used.

[mawburn]

Fixed here:

• 🤖 fix: Remove versions and __v when Duplicating an Agent #8115