# Scheduling a Prompt

HyperDesk includes a desktop-safe `schedule_prompt` capability for running a prompt later in the current app session.

## What it does

A scheduled prompt waits until the requested time, then injects the prompt back into the active HyperDesk session. It is useful for reminders, delayed checks, and short follow-up loops.

Example prompts:

- “Remind me in 10 minutes to check the release workflow.”
- “In 2 minutes, ask whether the build finished.”
- “At 5pm, prompt me to write the release notes.”

## Important limits

- Scheduled prompts are in-memory for the current HyperDesk desktop session.
- They do **not** survive app restarts.
- Very long delays are rejected; use a normal calendar or durable scheduler for long-term reminders.
- A scheduled prompt still runs through the normal session context and tool approval model.

## Best practices

- Use short, concrete prompts.
- Include the desired success check.
- For release workflows, schedule a prompt that asks the agent to verify a URL or workflow status.

Example:

> “In 5 minutes, check the GitHub release workflow for v0.1.11 and summarize any failures.”
