Scheduled Chats

Have a saved agent start a new chat with your prompt on a recurring schedule, such as every weekday at 9:00.

A scheduled chat sends a fixed prompt to one of your saved agents on a timer. Each run starts a new conversation, so you come back to a finished answer: a morning news briefing, a weekly report, a reminder that checks something for you.

Scheduled Chats are experimental, and an admin has to turn them on.

Create a schedule

Open Scheduled chats from the side panel and click New schedule.

Give it a name and write the prompt. The prompt is sent as plain text; composer variables are not filled in.

Pick the agent. You need view and use access to it, and it has to be a saved agent.

Choose the Frequency, the Time zone, and, if you use Chat Projects, the project that new chats go into. Save.

Frequency

Hourly: at a chosen minute past the hour.
Daily: at one time of day.
Weekdays: at one time, Monday to Friday.
Weekly: on the days you tick, at one time. Pick at least one day.
Custom: a five-field cron expression (minute, hour, day of month, month, day of week). The dialog shows the next few run times as you type. 0 9,17 * * 1-5 runs at 9:00 and 17:00 on weekdays; 0 9 1 * * runs at 9:00 on the first of each month. Seconds and year fields are not supported.

Runs must be at least an hour apart unless your admin allows a shorter gap, and that applies to custom cron too: */15 * * * * is rejected at the default setting.

Time zone

New schedules start in your browser's time zone; your browser zone and UTC are pinned at the top of the list. Times follow the schedule's zone, not wherever you happen to be, and daylight saving is handled: a time that does not exist on the change day runs at the first valid moment, and a time that occurs twice runs once.

Times are displayed in your 12- or 24-hour clock format and weeks start on the day set in Settings. That only changes how they look, not when they run.

Manage schedules

Each schedule card shows when it runs next, how the last run went, and a link to the latest conversation. From a card you can edit, enable or pause, Run now, or delete it. Run now starts one run even when the schedule is paused, without turning future runs back on. The panel also shows how many of your allowed schedules you have used.

If a run stops to ask you a question or to get approval for a tool call, its status shows Needs approval. Open the conversation to answer, and the run carries on.

When a run does not happen

Only one run of a schedule happens at a time. A run is Skipped if the previous one is still going or if your balance is too low.

Before each run, LibreChat checks the agent's MCP servers, including those used by its subagents. If one is unreachable, needs you to sign in again, or you have lost permission to it, the run does not start. Use Open agent to reconnect MCPs on the schedule to fix it. You can still edit a schedule while it is blocked like this.

A schedule disables itself, with the reason on its card, when:

it fails several runs in a row,
its agent is deleted, invalid, or you lose access to it, or you lose permission to use agents,
your balance runs out,
a required project is missing or was deleted.

Fix the cause and switch the schedule back on.

Authorizing MCP tools for unattended runs

Some deployments require you to authorize MCP access before a schedule can use those tools without you. In that case the schedule editor has a Scheduled MCP authorization section: set the Authorization lifetime (hours) and click Confirm authorization. The card shows Authorized with the exact expiry time. The authorization covers only that agent and the listed resources, expires on its deadline, and is cleared if you change the agent, the schedule, or the resources; you then confirm again. Revoke authorization withdraws it at any time.

Setup

Scheduled Chats are off by default. An admin enables them, sets limits such as schedules per user and the minimum interval, and meets the Redis requirements for multi-replica deployments; see Scheduled Chats configuration.