Put recurring work on the calendar.
Tell Sharper what should happen and when. Create the schedule in conversation or manage it in the Scheduled Tasks UI, then inspect every run and the task it produced.
Manage scheduled tasks in conversation.
Create, update, pause, resume, or review scheduled tasks in plain language. Sharper keeps the schedule, timezone, run mode, and safeguards visible before it makes a change.
FAQ
Practical details about creating schedules, recurrence, timezones, run modes, confirmations, and run history.
Can I create a scheduled task from chat?
Yes. Load the sharper-api skill and explicitly describe the work, start time, recurrence, timezone, and run mode. Sharper can create the persistent schedule after you review the request.
Which recurrence options are supported?
Scheduled Tasks support one-time, every-N-hours, daily, weekly, and monthly schedules. Weekly and monthly schedules use the weekday or month day from the start time.
What is the difference between the two run modes?
Same task reuses one conversation across runs, which preserves continuity. Independent task starts a fresh conversation for every run, which keeps each result isolated.
Can a scheduled task use knowledge bases or integrations?
Yes. You can attach organization knowledge bases and enabled integrations so that context is available whenever the schedule runs.
Can I pause or edit a recurring task?
Yes. Recurring tasks can be paused or resumed. You can edit their title, prompt, future dates, context, integrations, and confirmation policy; immutable schedule fields require creating a replacement.
What can I see in run history?
Run history shows queued, running, completed, failed, and skipped runs. When a run created a task conversation, you can open it to inspect the result and execution context.
Schedule the work that should not wait for a reminder.
Describe a recurring task in conversation, review its exact schedule, and keep every future run visible in the workspace.