Schedule recurring agent work

On this page

Create a scheduled task for repository checks, issue triage or a recurring summary.

Before you start

Open the workspace and ensure the selected agent can access the required files and integrations. A scheduled task is called a Ritual. Its prompt is the Decree and its notification policy is Omens.

Create the schedule

  1. In Command/Action mode, find Rituals in the left sidebar.
  2. Click + to open New Ritual.
  3. Fill the title and choose the Grunt that should execute the task.
  4. Choose a Cadence: every N minutes/hours, daily, weekdays or weekly.
  5. Set notifications to Always, On failure or Never.
  6. Write the task prompt. Use Foresee to preview variables such as {workspace_name}, {repos}, {branch} and {datetime}.
  7. Click Inscribe Ritual to save.
  8. Run it manually once from its controls, then inspect its terminal and run history.

The current desktop editor exposes periodic cadence choices. A general cron-expression editor is not documented here; use the controls actually shown in your build.

Example prompt

Review open issues relevant to {workspace_name}. Identify new blockers since the previous report and write a short summary with issue links. Keep the task read-only and report any unavailable integration instead of assuming there are no issues.

For this example, configure the tracker integration before enabling the recurring run.

Keep the schedule available

Keep the owning workspace open and signed in on the machine responsible for the schedule. If the work should continue away from the laptop, configure the Skyforge route and verify which machine owns the scheduled work. A saved schedule cannot execute on a stopped or unreachable host.

Check the result

Open the Ritual's detail panel and check its run history, outcome and output. Confirm a manual run succeeds and that the next-run time matches your intended cadence. Use disable/enable controls when changing the schedule.

More detail

Scheduled Tasks · Cloud ownership and sync