Scheduled Tasks in Aikeedo: Let Chat Run on a Schedule

Think about how people use an AI assistant once the novelty wears off. The same morning question about the news in their field. The same Friday request to sum up the week. The same Sunday plan for meals or money. They are not asking anything new — they are repeating themselves, and they forget on the days they are busiest.

v5.2 lets them stop. With scheduled tasks, a user writes the instructions once, picks a schedule, and Aikeedo runs them on time, every time, whether or not anyone has the app open.

This post covers what a scheduled task is, how your users create and manage them, and how you control the feature as an operator.

What a Scheduled Task Is

A scheduled task has four parts:

• Instructions — what to ask, written the way the user would type it in chat.
• A schedule — when to ask it.
• A model — the default chat model, or any model the plan includes.
• A permission — whether the run may stop to ask the user something.

When a task is due, Aikeedo sends the instructions to the assistant as a new chat, exactly as if the user had typed them. The chat is named after the task, saved in the library like any other, and carries a note saying which scheduled task started it and when. If the user wants to follow up on a briefing, they just reply.

Because each run is an ordinary chat, it can use the same tools as any chat on the plan, such as web search, connectors and Canvas documents.

Three Ways to Create One

Your users find scheduled tasks under Scheduled in the sidebar. The New task menu offers three routes.

Ask in chat

Create with chat opens a new conversation with "Set up a scheduled task that…" ready to finish. But users do not need the menu at all. In any chat, they can say "every weekday at 8, give me the top five AI headlines" and the AI creates the task on the spot, using the user's timezone and the model they are chatting with. It asks first only when the request is unclear.

The chat shows a card with what was set up — name, schedule, permission and instructions — with a link to the task. Creating a task this way costs no credits.

Set it up manually

Set up manually opens a form with the name, instructions, schedule, model and permission. Time is entered in 24-hour format and stored with the user's timezone, so 08:00 stays 08:00 wherever the server is.

Start from a template

The Suggested section lists templates, and View all templates opens a gallery with search and category filters. Picking one fills in the instructions and a sensible schedule, which the user can change before saving.

Schedules

The Repeat options cover how people actually plan:

• Once — on a given date
• Daily
• Weekdays — Monday to Friday
• Weekly — on one or more days of the week
• Monthly — from a start date; a day the month does not have runs on its last day, so the 31st becomes the 30th in April
• Yearly — on a month and day

Repeating tasks can end on a date or never. If cron was down and several runs were missed, the task runs once when it comes back and then carries on from now, rather than flooding the user with catch-up chats.

Auto or Ask

Nobody is watching when a task runs, so each task has a permission:

• Auto runs without asking. Tools that would stop and wait for the user — a clarifying question, or a connector tool that needs approval — are left out of the run, so it goes through to the end.
• Ask may pause to ask the user a question or to approve a tool, such as a connector action that needs approval. The run waits, and the user gets a "Chat needs your input" notification.

Auto is the default, and the right choice for briefings and summaries. Ask suits tasks that act on other services.

Running, Pausing and History

Each task has its own page with an Overview and a History tab.

• Run now starts an extra run immediately without moving the schedule.
• Pause and Resume stop and restart the schedule without losing anything.
• History lists every run as Queued, Running, Completed, Needs your input or Failed, marked manual or automatic, with a link to its chat.

When a run finishes or fails, the user gets a notification under the bell, and a browser alert if they allowed them. If a run cannot start — the plan no longer includes the model, the workspace is out of credits or a usage limit is reached — the notification says why.

Deleting a task removes it and its history. The chats it produced stay in the library.

Templates

Aikeedo ships ten starter templates in two categories:

• Productivity — Morning briefing, Weekly work summary, Weekly planning and Daily industry news
• Personal — Workout reminder, Weekly meal plan, Weekly budget check, Daily language practice, Evening reflection and Weekend plans

Import them under Settings → Starter content. Then make them yours: templates are managed on the admin Templates page as the Scheduled task template type, with their own instructions, an optional model and a default schedule. Write templates for your niche — a daily market summary for traders, a weekly content calendar for marketers — and they become a reason to subscribe.

The Operator Perspective

Scheduled tasks are off by default. To offer them:

1. Turn on the feature. Switch on Scheduled tasks under Settings → Features → Chat. Chat must be on too.
2. Set the plan limits. Each subscription plan has a Scheduled tasks cap in its quota: how many tasks a workspace may have, paused and ended ones included. Leave it blank for unlimited, or set it to 0 to leave the feature out of the plan.
3. Keep cron running. Tasks run only while the cron job runs every minute. A background worker makes them start faster but is optional.

Some details worth knowing:

• Credits. Each run is charged to the workspace like a chat reply, at the plan's rates. Before a run starts, Aikeedo checks that the model is still in the plan and that the workspace has credits left.
• Plans with no tasks. On a plan with a cap of 0, the Scheduled page stays in the sidebar and offers View plans — a natural upgrade path. Existing tasks stop running until the workspace moves to a plan that includes them.
• Downgrades. If a workspace has more tasks than the plan it is switching to allows, checkout stops and asks the user to remove some first.
• Workspaces. Every member's tasks count toward the workspace's cap. The workspace owner sees all members' tasks under All members and can delete them. Only the person who created a task can open, change or run it.

What Scheduled Tasks Do Not Do

• No hourly or cron-style schedules. The shortest repeat is daily.
• No assistant selection. A task runs with a model, not with one of your Assistants.
• No time zone picker. A task uses the time zone of the browser it was created in.
• Not in private mode. The AI does not offer to create tasks in private mode or inside a task's own runs.

Getting Started

Update to v5.2, then:

1. Turn on Scheduled tasks under Settings → Features → Chat.
2. Set the Scheduled tasks cap on your plans.
3. Import the starter templates from Settings → Starter content, and add a few of your own.
4. Check that cron runs every minute.

The scheduled tasks documentation has the details, the feature page has the overview, and the v5.2 release post covers everything else that is new.

Try the live demo to see it in action, or head to our pricing page if you are ready to get started.