Where scheduling actually lives: an optional Web overlay, not a plugin

When to use

Looking for the scheduling entry, not finding it in the plugin list, and wondering if the wrong version is installed. It is neither a plugin nor a CLI feature.

Preparation

Host version

To fill (record the exact rc version when testing)

Model

To fill

Mode / permissions

Standard mode + modify-within-workspace is enough to start

Plugins required

None (add name & version after testing if used)

Input materials

Keep in a separate workspace; back up originals first

Full instruction

I want to confirm where the scheduling or reminder feature lives in this environment, and what it can and cannot do.

Answer in this order, and for each say where the basis comes from (docs, config file, or your inference):

1. Is it a built-in subsystem, an optional capability (overlay), or a plugin? Which package?
2. Where is the entry point: CLI, web UI, or config? If it is UI-only, which UI and what must be enabled first?
3. Which scheduling rules does it support? List each with its parameter limits (minimum interval, time format, how the zone is given).
4. What does it explicitly not support? For example calendar rules, cron expressions, cross-session delivery.
5. How is a due reminder delivered, and what happens if the session is closed?

Do not give me generalities like 'schedulers usually support cron'. If this version's schedule protocol has no cron, say so and tell me what to use instead.

End with one command or action that verifies the entry point exists right now.

Copy full instruction

Run log

Output

After a successful run, list files and screenshots here, and note whether originals changed.

Acceptance checklist

Tap to tick each item off as you verify.

• Picks one of built-in, overlay, or plugin, and names the package
• States which layer the entry lives in and what must be enabled first
• Lists supported rules with parameter limits, especially the minimum interval
• Explicitly states what is unsupported instead of hedging
• Gives a command or action that verifies the entry exists

Failures & boundaries

• Measured: schedule is an optional capability. The official doc is titled 'Session-scoped Schedule' and the packages are @deepseek-ai/dsh-schedule and @deepseek-ai/dsh-client-ui-schedule — one server side, one UI side. It is not in the profile's bundles list (which holds only dsh-base and dsh-web-app), so an overlay must be loaded to enable it.
• Only three rules exist: after (a positive safe-integer second delay), at (an explicit absolute instant), and every (a fixed interval, minimum 300 seconds). The docs state plainly that the protocol contains no calendar rules, no cron expressions, and no zone for repeating schedules.
• Delivery is in-session only: a live idle agent delivers immediately, while closed or cold sessions leave reminders overdue until resumed. No email, SMS, or push.
• So searching the plugin list will never find it — it is not a plugin. The point of this recipe is to settle the 'what is it' question first and stop wasting time in the wrong place.
• Blocked on: Runnable, but end-to-end verification needs the Schedule overlay enabled first: create a reminder, wait for it, confirm it returns to the original session. Not loaded here yet.

Claim this recipe Back to recipes