Scheduled tasks

Give an agent a standing instruction and a schedule. Naumu opens a fresh thread when it fires - Monday digests, nightly briefs, weekly reviews.

Updated August 29, 20267 min read

A scheduled task is a standing instruction you give to an agent (the AI assistant in your space). It has two parts: a prompt - the instruction itself - and a schedule for when to run it.

When the schedule fires, Naumu opens a fresh chat thread in your space, hands the agent your instruction, and the agent does the work and replies - all without anyone having to ask. Scheduled tasks are made for the recurring jobs you'd otherwise have to remember: a Monday status digest, a nightly news brief, a weekly project review.

Each agent keeps its scheduled tasks under a section called Responsibilities. An agent's responsibilities are simply the scheduled tasks assigned to it.

Creating a scheduled task

There are two ways in: fill the form in an agent's details panel, or just ask the agent for one in chat. From the panel:

Open the agent you want to do the work.
Find the Responsibilities section and click Responsibility.
Give the task a short title - this is the label it shows up as in the list, e.g. "Weekly Q3 review."
Under What should the assignee do?, write the instruction the agent will receive when the task runs. Phrase it as a request - for example, "Summarise this week's changes and post the three things that need attention."
Pick When: Once for a single run at a set date and time, or Recurring for a repeating schedule.
Set the responsibility's Home - who can see it, using the same sharing controls as a note or a thread:
- Private - just you, plus anyone you add as a participant.
- Everyone in [space] - every member of the space.
- Topics - file it into one or more topics, so it sits where that work already lives.
The Home you pick governs both the responsibility itself and the threads it fires, so a run lands in front of the same people who can see the standing instruction.
Click Create.

The instruction is a prompt for the agent, not a message from you. So when the task runs, the thread shows the agent's reply - not you appearing to talk to yourself.

Any member can create a scheduled task. Editing or deleting one is reserved for its creator and space admins, but pausing stays open to every member - a standing autonomous run should always have a kill switch anyone can pull.

Recurring schedules

For a recurring task, choose a recurrence and a timezone. Behind the scenes, the schedule is stored as a standard cron expression - a compact way to describe repeating times by minute, hour, day of month, month, and day of week. The timezone is the local clock that expression is read against, so "every Monday at 8am" fires at 8am where you are, not in UTC (Coordinated Universal Time, the global reference clock). As you set the schedule up, the form shows a plain-language preview of when the task will next fire.

Asking an agent in chat

You don't have to open the panel at all. Ask an agent in a thread - "every Monday at 8am, post a summary of what changed last week" - and it creates the responsibility itself, assigned to itself, working out the schedule and timezone from what you asked for. The row appears in the Responsibilities panel like any other, and you can edit, pause, or delete it there.

By default a run posts back into the conversation you asked in. Ask for a separate thread instead, or name people or topics for the run to reach, and each fire opens a fresh thread with that audience. You can also make the responsibility itself visible to the whole space rather than just its participants.

In chat the agent can also list the responsibilities it runs, run one now, pause or resume one, and cancel one.

Asking is not a way around a permission. The agent is held to the same rules the panel enforces: it only lists rows you can already see, deleting one still takes its creator or a space admin, and naming other people on a responsibility takes the standing to open a thread with them.

What a task can do

When a task fires, the assigned agent runs in a new thread with full access to its normal tools. So a scheduled task can do anything that agent could do on request - read and search your memory, traverse (follow) the connections between nodes, draft notes, add or update nodes, and report back in the thread. A task is only as capable as the agent you assign it to, so pick the agent whose persona and permissions fit the job.

Scheduled tasks are distinct from reminders. A scheduled task is a standing job an agent runs in its own thread; a reminder is a lightweight personal nudge - no agent, no thread, no AI run behind it. Set one with the Remind me action on any message, or just ask an agent in chat to remind you about something: it anchors the reminder to your message and surfaces it in your sidebar (and as a push notification) when it's due. The agent manages them too - ask it in chat to list your upcoming reminders or cancel one.

Viewing history and runs

Each scheduled task row shows its key state at a glance:

The schedule (e.g. "Daily" or "Once at Jun 8, 9:00 am").
Last run - how long ago it last fired, or "Never."
Run count - how many times it has run.
A spinner while a run is in progress.

There is no separate log viewer, and you don't need one: the record of a run is the thread it produced. Every time a task fires, it creates a thread in your space with the agent's reply, so you can open that thread to see exactly what the agent did and read its output. If the task was set up to remind other people, the resulting thread also reaches their sidebar.

Seeing every responsibility in one place

An agent's details panel shows only that agent's responsibilities. To see all the standing work across the space at once, open Settings -> Space -> Responsibilities.

The page groups responsibilities by who can see them rather than by which agent runs them - a Private group, a group for everything shared with the whole space, and one group per topic. A responsibility filed into several topics appears under each of them, so scanning a topic shows every standing duty that lands there.

You only ever see responsibilities you have access to. Within each group, active recurring tasks come first and paused ones stay in the grid dimmed - a paused task is still a standing duty someone can resume. One-off tasks that have already fired collapse behind a finished disclosure at the bottom of their group.

A topic's pane links straight here: the header row reading N scheduled items opens this page scrolled to that topic's group.

Running a task manually

To run a task on demand without waiting for its schedule, hover over the responsibility - on the agent's panel or on the Settings -> Space -> Responsibilities page - and click the Run now (play) button that appears. This fires the task immediately, exactly like a scheduled run, producing a fresh thread with the agent's reply. You can also just ask the agent in chat to run one of its responsibilities now.

If a run is already in progress, Run now is unavailable and Naumu tells you the task is already running. This keeps the same task from running twice at once.

Pausing and removing tasks

Pause a task with the toggle on its row. A paused task keeps its schedule but won't fire until you re-enable it. You can still Run now while paused.
Edit a task with the pencil icon to change its title, instruction, schedule, or Home. The assigned agent can't be changed after creation - create a new task on a different agent instead.
Delete a task with the trash icon. One-off tasks are removed automatically after they fire.

Agents - the AI participants that run scheduled tasks.
Sidebar - where fired reminders appear.
Spaces - where agents and their responsibilities live.
Quickstart - set up your first space.