Automation & scheduled tasks

Automation (scheduled tasks) lets Aureink run tasks automatically on a schedule. It’s like setting an alarm clock for a task — it runs on time, automatically, with no need to trigger it by hand each time. It suits “repetitive and regular” work like daily briefings, periodic tidy-ups, and recurring checks.

1 · Overview

A lot of work isn’t done once and finished — it “comes around every day/every week.” Hand this kind of task to automation: set it up once, and Aureink runs it automatically on the set frequency and keeps a record, so you can just check the results later.

Automation accumulates quota consumption by frequency — the more often it runs and the heavier the task, the more it consumes. So thinking through the frequency and run time before setting it up is the key to using it well.

2 · Creating a scheduled task

The main way to create a scheduled task is simply to tell the AI directly in a conversation what you want done on a schedule:

• Example: “Generate an AI news briefing for me every morning at 8.”
• Example: “Every Monday at 9 a.m., compile last week’s customer feedback into a summary.”

State clearly “what to do + how often,” and Aureink will set up a scheduled task accordingly. The task then appears on the Scheduled Tasks page, where you can view and manage it.

〔Figure: creating a scheduled task with one sentence in a conversation, and the resulting entry appearing on the Scheduled Tasks page〕

3 · The Scheduled Tasks page

Open the Scheduled Tasks page from the activity bar to view and manage all recurring tasks in one place:

〔Figure: the Scheduled Tasks page, highlighting the task list, last run time, failure status, and the run history entry〕

• Task list — an overview of all scheduled tasks, including last run time and run status; a failure status is flagged when a run fails.
• Run history — the past run records of each task; open one to view the details (what it did this time and how it turned out).

For a single task, you can:

• Run Now — run once immediately without waiting for the next scheduled time, often used to verify the task is configured correctly.
• Delete task — remove a scheduled task you no longer need.
• Clear history — clear that task’s run history.

When adjustments are needed, you can edit the following fields of a task:

4 · Usage tips

• Run it manually once before scheduling — use Run Now or a regular task to confirm the prompt produces the expected result, then hand it off to run on a schedule.
• Estimate the run time well — match a single run’s duration to its frequency, so the next run doesn’t start before the previous one finishes.
• Frequent enough is enough — higher frequency isn’t always better; set it to your actual needs to save quota and reduce interruptions.

5 · Important notes

Important notes

• Set high-risk prompts with care: prompts involving writing/deleting files, financial operations, or sending messages externally will run automatically and unattended — confirm again and again before scheduling them.
• Still bound by permissions and the sandbox: automatic execution does not bypass security boundaries and remains bound by the permission mode and the sandbox; but since no one confirms in real time, keep the scope as minimal as possible.
• Accumulates quota by frequency: a scheduled task consumes usage quota on every run; the higher the frequency and the heavier the task, the more it accumulates.
• Watch the failure status: review the run history regularly and promptly handle tasks flagged as failed.

Disclaimer: a scheduled task runs automatically and unattended, and its behavior is determined by the prompt, frequency, and bound Agent you set. Enable automatic execution only for tasks you fully understand and trust, and stay cautious with prompts that touch data or external actions.

Last updated · July 2026 ｜ Next: Channels overview →