Scheduled Tasks

Run saved instructions automatically on a daily, weekly, or monthly schedule – each result appears as a chat in your inbox.

Scheduled Tasks (listed as Scheduled in the sidebar) let you save an instruction once and have it run automatically on a recurring schedule – daily, weekly, or monthly at a fixed time. On every run, Kasimir turns your instruction into a new chat and drops a notification into your inbox that links straight to the result. This way you can get, for example, a market overview every morning or a recurring report at the start of each month, without retyping the prompt each time.

What a scheduled task is

A scheduled task consists of a saved instruction (the prompt), a schedule, and a few optional settings. At the scheduled time, the following happens automatically:

Kasimir creates a new chat (titled with the task name).
Your instruction is sent as the user message.
The AI model answers once, and the answer is saved in the chat.
You receive an inbox notification linking to the finished chat ("<name> is ready.").

ℹ️

A scheduled task is a single recurring prompt – not a multi-step process. For form-based, multi-step processes, use Workflows instead.

Overview and management

Under Scheduled you see all your tasks in a table with these columns:

Column	Meaning
`Name`	The task's label (links to the editor)
`Frequency`	A summary of the schedule, e.g. "Daily 08:00" or "Weekly Mon 09:00"
`Next run`	When the task runs next (or `Never` if inactive)
`Last run`	When it last ran
`Active`	Toggle to enable/disable

Each row offers the actions Run now, Edit, and Delete.

Overview of all scheduled tasks with frequency, next run, and actions.

Active toggle: Turns the task on or off. When off, no next run is scheduled (Next run shows Never).
Run now: Immediately queues a run regardless of the schedule. You'll see the message "Running shortly – the result will appear in your inbox." The result becomes available in the inbox a short time later.
Delete: Permanently removes the task and its history after a confirmation prompt.

Creating a task

Click New task at the top right. The form has the following fields:

Name and instructions

Name (required, 1–120 characters): A short label, e.g. "Daily market overview".
Instructions (required, up to 8000 characters): The actual prompt sent on every run. Write it as a complete, standalone request – there is no prior conversation context; each run starts from scratch.

Assistant and model

Assistant (optional): Pick one of your assistants so the task runs with its persona (system prompt). The default is No assistant. If the assistant has a default model and you leave the model below unset, the assistant's model is used.
Model (optional): Chooses the AI model. With Default model, Kasimir uses your organization's default chat model.

Schedule

Task creation form: instruction, assistant/model, schedule, and visibility.

Frequency: Daily, Weekly, or Monthly.
Time (required): Time of day to run, in HH:MM format.
Weekday (weekly only): A weekday from Sun to Sat.
Day of month (monthly only): A day from 1 to 28.
Timezone: The timezone the time refers to. Your browser's timezone is preselected; common zones such as Europe/Berlin, Europe/Vienna, Europe/Zurich, UTC, and others are also offered.

⚠️

For monthly tasks, only days 1 to 28 can be chosen. This guarantees the task actually runs on a day that exists in every month (the 29th–31st are intentionally not offered).

Visibility and Active

Visibility: Defaults to Private – the task and its result chat belong only to you. Choosing a project instead makes the task visible to all project members, and the generated chat is attached to that project.
Active: Determines whether the task is scheduled immediately after saving. Inactive tasks can still be started manually at any time via Run now.

Click Save to create the task; you then land on its detail page, where the run history also appears.

Run history

On an existing task's detail page, the History section shows the most recent runs (up to 30). Each entry includes:

a status: Queued, Running, Completed, or Failed,
the trigger: Scheduled (automatic) or Manual (via Run now),
the time of the run,
a short error message on failure,
an Open chat link to the generated chat on success.

How execution works behind the scenes

An always-on service checks regularly (roughly once a minute) which active tasks are due, queues a run, and processes the queue. Each run produces exactly one AI answer, delivered as a chat plus an inbox notification. You don't need to have Kasimir or your browser open for this to happen.

Permissions

Manage (edit, delete, Run now, Active toggle): only the person who created the task.
View: for project-scoped tasks, additionally all members of that project (including the history).
A task's result chat always belongs to the creator; for project-scoped tasks it is attached to the project.

Limitations in this version

⚠️

Scheduled tasks run a single prompt without tools. Automatic runs have no tools, no web search, and no document knowledge (RAG) – even when an assistant is selected. Use them for plain text/knowledge tasks the model can answer on its own; for tool-assisted processes, Workflows are the right choice.

Other intentional limits:

Frequencies are limited to Daily / Weekly / Monthly (no free-form cron expressions in the UI).
Monthly only up to day 28.
Exactly one answer per run, no multi-step process.

Tips

💡

Write the instruction so it works with no history – e.g. "Create a bullet-point summary of the most important industry news from the last 24 hours." Since each run starts from scratch, everything needed should be in the prompt itself.

💡

If you want a consistent tone or fixed framing, create an assistant and select it in the task – its system prompt is applied on every run.

💡

Test a new task before its first scheduled run with Run now and review the result in your inbox.

BackLibrary NextSkills