📘 docs: Add Agents Config

[danny-avila]

Summary

I added documentation for configuring agents in LibreChat, including a feature toggle and capabilities settings, and clarified permissions for accessing agent instructions and tools.

• Added documentation for the agents configuration in librechat.yaml, introducing the agents feature toggle to enable or disable agents for all users.
• Documented the agents endpoint object structure, detailing the disableBuilder and capabilities options for customizing agent functionalities.
• Updated the configuration index and meta files to include the agents configuration.
• Clarified in the agents feature documentation that instructions, model parameters, attached files, and tools are only exposed to users with editing permissions.
• Added a warning about potential data leakage through conversations if agents are not properly configured.

Change Type

• New feature (non-breaking change which adds functionality)
• Documentation update

Testing

I verified that the documentation builds correctly and that the agents feature toggle works as expected when configured in librechat.yaml. I tested the agents' capabilities settings to ensure they properly enable or disable the specified functionalities.

Test Configuration:

• Verified the documentation pages render correctly without errors.
• Tested disabling agents globally via the agents toggle in librechat.yaml.
• Tested customizing agent capabilities by modifying the capabilities list in the agents endpoint configuration.

Checklist

• My code adheres to this project's style guidelines
• I have performed a self-review of my own code
• I have commented in any complex areas of my code
• I have made pertinent documentation changes
• My changes do not introduce new warnings
• Local unit tests pass with my changes

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Comments	Updated (UTC)
librechat-ai	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Dec 11, 2024 10:18pm

[github-actions]

📦 Next.js Bundle Analysis for librechat.ai

This analysis was generated by the Next.js Bundle Analysis action. 🤖

New Pages Added

The following pages were added to the bundle from the code in this PR:

Page	Size (compressed)	First Load	% of Budget (350 KB)
/changelog/config_v1.1.9	64.5 KB	358.39 KB	102.40%
/docs/configuration/librechat_yaml/object_structure/agents	12.88 KB	306.77 KB	87.65%

Three Pages Changed Size

The following pages changed size from the code in this PR compared to its base branch:

Page	Size (compressed)	First Load	% of Budget (350 KB)
/docs/configuration/librechat_yaml	12.52 KB	306.41 KB	87.55% (🟡 +0.02%)
/docs/configuration/librechat_yaml/object_structure/config	14.41 KB	308.3 KB	88.09% (🟡 +0.01%)
/docs/features/agents	15.13 KB	309.02 KB	88.29% (🟡 +0.08%)

Details

Only the gzipped size is provided here based on an expert tip.

First Load is the size of the global bundle plus the bundle for the individual page. If a user were to show up to your website and land on a given page, the first load size represents the amount of javascript that user would need to download. If next/link is used, subsequent page loads would only need to download that page's bundle (the number in the "Size" column), since the global bundle has already been downloaded.

Any third party scripts you have added directly to your app using the <script> tag are not accounted for in this analysis

The "Budget %" column shows what percentage of your performance budget the First Load total takes up. For example, if your budget was 100kb, and a given page's first load size was 10kb, it would be 10% of your budget. You can also see how much this has increased or decreased compared to the base branch of your PR. If this percentage has increased by 20% or more, there will be a red status indicator applied, indicating that special attention should be given to this. If you see "+/- <0.01%" it means that there was a change in bundle size, but it is a trivial enough amount that it can be ignored.