mirror of
https://github.com/danny-avila/LibreChat.git
synced 2026-11-19 22:43:38 +00:00
* 🙋 feat: Let a Schedule's Owner Approve a Tool Before Each Use * 🧪 test: Drive a Real Run Through a Schedule's Approval Pause and Resume * 🙋 fix: Keep a Stored Ask-First Choice When a Run Can No Longer Pause Where pausing became unavailable, the dialog hid the ask-first boxes and renewed the grant without them, so a tool the owner approved each time started running unattended. The dialog now starts from the stored choice either way and always sends it. Where a run cannot pause it shows only the stored questions, with a note that those tools are refused for now, and the owner can keep or drop them but add none. The server keeps the stored questions for tools still allowed when a confirmation says nothing about asking, and refuses only a new question where a run cannot pause. * 🙋 fix: Say Why a Schedule Asks for Approval in the Reader's Language The approval card showed an English sentence sent by the server as the request's description. The server now sends a code, and the card maps it to a localized string. Any other description is shown as sent. * 🙋 fix: Never Offer Always Allow for a Tool a Schedule Asks About Each Use Where the endpoint enables Always allow, a schedule's approval card offered it for a tool the owner approves on each use. Choosing it stored a conversation allow the schedule still overrode at the next use. The offer and the recheck at resume now take a predicate for anything beyond the policy that asks on every use, and the schedule's grant supplies it, so such a tool is neither offered nor stored. * 🙋 fix: Let the Owner Ask First About as Many Tools as They Can Allow The confirmation accepted up to 25,600 allowed tools per server but only 256 to ask about, so a large grant could not be confirmed with every tool set to ask first. * 🙋 fix: Keep a Tool Asking First When the Owner Allows Its Changed Definition The dialog derived the ask-first boxes from the ticked tools. A tool whose definition changed starts unticked, so its stored question was dropped, and ticking the tool again confirmed it as unattended. The ask-first selection is now kept apart from the ticks, starts from the stored grant, and is narrowed to the ticked tools only when the confirmation is sent. The owner's edits to it hold only for the grant they were made against, so a question added to a grant confirmed elsewhere is not dropped unseen. |
||
|---|---|---|
| .. | ||
| __tests__ | ||
| agents | ||
| assistants | ||
| auth | ||
| AuthController.js | ||
| AuthController.spec.js | ||
| avatar.contentFilter.spec.js | ||
| Balance.js | ||
| Balance.spec.js | ||
| EndpointController.js | ||
| FavoritesController.js | ||
| FavoritesController.spec.js | ||
| mcp.js | ||
| mcpApps.js | ||
| mcpApps.test.js | ||
| ModelController.js | ||
| ModelController.spec.js | ||
| PermissionsController.js | ||
| PluginController.js | ||
| PluginController.spec.js | ||
| ReasoningCapabilitiesController.js | ||
| SkillStatesController.js | ||
| TokenConfigController.js | ||
| tools.js | ||
| TwoFactorController.js | ||
| UserController.js | ||
| UserController.spec.js | ||