Scheduling runs a task automatically at a time you set. You tell 100xprompt what to do and when; it opens a fresh session, hands your prompt to the agent you chose, and does the work while you’re away. Suppose you want a summary of open pull requests waiting for you every weekday at 9am. Describe the job once, give it a schedule, and it runs on its own - nightly cleanups, weekly reports, and hourly health checks all run better on a clock than on your memory.

​
How a scheduled task works

A scheduled task is a saved prompt plus a when. You give it a title, the instructions to run, and a schedule - a one-time moment, a repeating interval, or a cron expression. From then on, whenever the task is due, 100xprompt starts a new session and runs it. Each run is independent and clean, so a recurring report never gets tangled with last week’s conversation.
Tasks belong to the project you created them in, and every run happens in that project’s context - so a task scheduled in one codebase always runs against that codebase, with the right files, tools, and configuration around it.
Scheduled tasks run while 100xprompt is live - that is, while a session is open in your terminal or the server is running. Keep 100xprompt running for the times your tasks are due, or use it to fire recurring work during your working hours.

​
Pick a schedule type

Every schedule is one of three kinds. Match the type to how often the work should happen.
I want the task to…Use
Run once, at a specific future momentOnce
Repeat on a fixed gap, foreverEvery
Fire on a calendar rule (specific hours, weekdays, dates)Cron
TypeRunsYou provideExampleFires
OnceA single time, then it’s doneAn ISO date-time2026-06-23T09:00June 23, 2026 at 9:00 AM
EveryOn a repeating interval, foreverA duration30s, 5m, 2h, 1dEvery 5 minutes, indefinitely
CronOn a calendar-based scheduleA 5-field cron expression0 9 * * 1-59:00 AM, Monday-Friday
Runs a single time at the date-time you name, then retires itself. Give the time in ISO format, for example 2026-06-23T09:00. Ideal for reminders and one-off jobs you want to happen later - “run the migration check tomorrow at 8 AM.”
Runs over and over on a fixed gap. Express the gap as a number and a unit:
UnitMeaningExample
sseconds30s
mminutes5m
hhours2h
ddays1d
Great for polling and watchdogs - “every 15 minutes, check that the staging build is green.”
Runs whenever the clock matches a standard 5-field cron expression:
┌───────── minute        (0 - 59)
│ ┌─────── hour          (0 - 23)
│ │ ┌───── day of month  (1 - 31)
│ │ │ ┌─── month         (1 - 12)
│ │ │ │ ┌─ day of week   (0 - 6, Sunday = 0)
│ │ │ │ │
* * * * *
Each field accepts a single value, a * wildcard, a range (9-17), a list (0,30), a step (*/15), or a combination (0,30 9-17 * * 1-5). Use cron when timing matters - a specific hour, only on weekdays, or the first of the month.
ExpressionMeaning
0 9 * * *Every day at 9:00 AM
0 9 * * 1-59:00 AM on weekdays
*/15 * * * *Every 15 minutes
0 0 1 * *Midnight on the 1st of each month
30 17 * * 55:30 PM every Friday

​
Set up a scheduled task

Suppose you want a weekday PR review waiting each morning. Create schedules by asking 100xprompt in plain language - describe the work and the timing, and it saves the task for you.
1

Describe the task and the timing

Tell 100xprompt what to run and when. Be specific about both:
Every weekday at 9am, review open pull requests and post a summary
to my notes. Use the review agent.
You can phrase the timing naturally (“every 30 minutes”, “tomorrow at 8am”, “at 9am on weekdays”) or hand over an exact interval or cron expression.
2

Choose which agent runs it

By default the task runs with your standard agent. To point it at a purpose-built agent - a planner, a reviewer, or one of your own - name it when you set the schedule. The task will run every time with that agent’s instructions, model, and allowed tools.
3

Confirm the schedule

100xprompt saves the task and reports its next run time, so you can confirm the timing landed the way you meant. A repeating task shows its next occurrence; a one-time task shows the single moment it will fire.
4

Let it run

From here it’s automatic. Each time the task is due, 100xprompt opens a fresh session, runs your prompt with the chosen agent, and moves on to the next occurrence.
Tips:
  • Write the prompt to stand on its own. A scheduled run starts cold, with no memory of a prior chat, so include the goal, the commands to run, and what to produce.
  • Point a recurring task at a purpose-built agent so every run has the same instructions, model, and allowed tools.
  • Prefer “open a PR” over “push to main” for unattended runs - you review the result on your own time.

​
List and remove schedules

Manage your tasks the same conversational way you create them.
Ask to list scheduled tasks to see everything you have set up. Each entry shows its title, whether it’s on or off, its type, the next run time, and how many times it has run - plus a note if the last run hit an error.
Show me my scheduled tasks.
Every run records its outcome. If a scheduled task fails, the failure is captured on the task and shown when you list your schedules - so a broken nightly job surfaces the next time you check, instead of failing silently.

​
Match the schedule to the job

Nightly maintenance

Format code, prune stale branches, refresh dependencies, or regenerate artifacts overnight - on a cron schedule or 1d interval - so your morning starts clean.

Recurring reports

Summarize open pull requests, changelog activity, or test coverage on a weekly cron (0 9 * * 1) and have the write-up waiting for you.

Periodic checks

Poll a build, watch a health endpoint, or verify a deploy on a short every interval and flag anything that drifts.

​
See a recurring schedule over time

Here’s how a weekday-morning task plays out across a week - it fires each qualifying day and skips the rest.
Scheduled tasks fire while 100xprompt is running. If a task’s scheduled moment passes while 100xprompt is closed, that occurrence is missed rather than replayed - the next run is computed forward from the current time. For work that must not be skipped, favor an every interval or a cron schedule (which will catch the next qualifying time) over a single one-time task, and keep 100xprompt running across the windows when your tasks are due.
  • Background Tasks: kick off long-running work on demand and collect it when it’s done.
  • Workflows: chain steps, agents, and tools into repeatable pipelines.

Background Tasks

Kick off long-running work that continues while you keep going - and check back on it when it’s done.

Workflows

Chain steps, agents, and tools into repeatable pipelines for the work you do again and again.