Skip to content

Scheduled tasks

A scheduled task wakes your agent without a new message from you. It suits recurring summaries, periodic checks and reminders.

When a task is running, its page offers Stop the run if the engine allows it. The stop is requested for that run only: actions already taken are kept and upcoming runs stay scheduled. The Stop requested status stays displayed while the run is being interrupted. To suspend upcoming runs, use Pause.

  1. Open the agent, then Tasks.
  2. Choose New task to open its settings page.
  3. Give it a clear name, for example “Morning summary”.
  4. Write a complete instruction.
  5. Choose the frequency and where to deliver the result.
  6. Choose whether you want to be personally notified at the end.
  7. Save.

The instruction must be executable without any further question:

Every morning, compare the prices of our 40 flagship products on the websites of the three competitors listed in Files, and flag any difference of more than 5%.

The interface offers the common cases:

  • once, on a specific date and time;
  • every hour;
  • every day;
  • every week, with a choice of day;
  • an advanced schedule for unusual rhythms.

Dates and times are shown in your workspace’s time zone.

Choose In Diadems to find the result in Conversations: each result opens a new conversation. Choose On Telegram to receive a notification on your phone; Telegram must first be connected in the Channels tab. You can also choose By email and enter the authorised recipient.

Some existing tasks show The agent reanalyses the result: their result starts a new run of the agent, which may take further actions. This setting is kept when you edit the task without choosing a new delivery. Select In Diadems to read the report directly without this reanalysis.

The Notify me in Diadems, Windows and mobile option also adds the result to your bell and sends it to your devices if you are not already viewing the right conversation. It applies only to your account and does not notify other members.

In the schedule, turn on Carry over the previous result so that each run receives the latest report from that task, up to 8,000 characters. This option helps the agent continue the work and avoid repetition. With no previous result, the task follows its usual instruction.

Each launch opens a new conversation: the full history of exchanges and tools is not carried over. To track progress precisely, also ask the agent to keep the steps and the items processed in a file. This setting is independent of automatic saving to memory.

In a task’s form, Save to memory automatically lets you choose whether its runs feed the agent’s memories. On compatible agents, this option is off by default: turn it on for tasks that produce lasting information, rather than for simple repetitive checks. Each task keeps its own choice.

Turning it off does not delete any memory and does not hide the result in the history. The agent can still consult its memories; an explicit request to remember something remains possible. If an engine update is required, the form says so and the existing behaviour is unchanged.

Each run of a task keeps its own history (the agent’s exchanges and actions). It is deleted automatically 30 days after the run ends. For a frequent task, tick Delete each run after 24 h: the history of each run then disappears the next day.

The task’s latest result stays displayed on its page. A run that you took over with Continue the conversation becomes an ordinary conversation and is never deleted by this setting.

Open a task from the list. On its page, you can:

  • run a task immediately to test it;
  • pause and resume it;
  • edit its instruction or schedule;
  • delete it.

An indicator shows the next run and any recent failure.

Each run opens its own conversation, available from the task’s page (Latest runs) or the Conversations tab. Once the run has finished, an administrator or the workspace owner can choose Continue the conversation below the thread. They become the pilot of that run and the agent keeps its full context: instruction, actions taken and report. Then ask a question or request a follow-up as in an ordinary conversation.

  • The first member to continue the run becomes its pilot. Others see “This run has already been taken over by …” and follow the conversation read-only; the pilot can share it.
  • The run stays visible to the workspace’s administrators, as it was before being continued. It joins its pilot’s conversations with its Scheduled task badge and keeps its date on the task’s page, with the note “Continued by …”.
  • Upcoming runs do not change: Carry over the previous result uses only the report from each run, never the exchanges added afterwards.
  • These exchanges follow the memory of an ordinary conversation, whatever the task’s Save to memory automatically setting.
  • A run still in progress cannot be continued: wait for it to finish.

Email, Telegram and other channel conversations remain view-only in Diadems: continue them from their channel.

Ask [agent name] opens a new conversation with “I’d like to know more about Tasks” and the link to this guide. The request is sent once. The agent can explain, create and edit its tasks with the Hermes tools it has. Give a precise instruction, frequency and destination.

Settings and frequency choices open in sub-views. The breadcrumb takes you back to the task or the list. Deleting asks for confirmation. Webhooks stay accessible from Tasks → Webhooks to start work from an external event.

Missions are an option for each agent, off by default. An administrator or the workspace owner turns it on in Settings → Missions: the agent can then create and track your missions from your requests, and the Work → Missions menu appears under Tasks. Turning it off hides this menu and the missions in the Activity panel; mission notices already received stay readable in your conversations. This choice applies to the Main work profile, available from your agent’s Work profiles menu. It is kept after a restart and applies to the next exchanges. The agent must be online for you to change it.

From Work → Missions, view your agent’s main board. A card appears when you or your agent explicitly create a mission on this board. Opening a conversation or launching a scheduled task does not automatically create a card. The board shows the setting under the name Create missions with [agent name].

Turning on missions creates no mission and sends no message. It allows the agent to create and manage the cards. A mission that is ready and assigned to the agent can then start automatically. Turning missions off does not pause the ones that already exist.

The columns separate missions to do, in progress, blocked and to approve. Finished missions are under the board, in a collapsible history shown as a table, most recent first. Each mission forms a row; its arrow expands the sub-tasks on indented rows. Click a title to open its page. Six missions are shown per page; the arrows give access to the next ones. Search includes this history and returns to its first page. Turn on Archives to include archived cards. Steps are grouped under their main mission. On the board, click the number of steps to expand its compact sub-cards, or turn on Show steps to expand them all. Each step shows its status and opens its own page. Search also finds steps, keeping their mission as a reference. A mission appears as in progress as soon as its steps are working. Empty columns fold into thin strips to leave more room for missions. Click a strip to expand it; a column containing a mission always stays open. When no mission to follow is displayed, the four columns appear on one compact line (two lines on mobile).

Open a card to read the report first, then download the delivered files (up to 25 MB per file). Find the instructions, steps, dependencies and run history on that same page. Each step can have its own files. Comments added after closure are flagged separately: they may complete or correct the initial summary. Done means the agent closed it or a manager approved the result. This status alone does not guarantee that a person has reviewed the work.

Administrators and the owner have actions on each page, depending on the mission’s current state:

  • Approve the result completes a mission awaiting approval. The missions that depend on it can then start.
  • Ask for a correction records your feedback in the mission and allows the agent to resume its work.
  • Block closes the run as blocked; an action already under way may still finish. Unblock lets work resume once the dependencies are met. Resolve the obstacle before resuming.
  • Reopen allows new work on a finished or archived mission. Be specific in your request: the following missions may need to be redone.
  • Archive puts the card in the archives and frees its dependencies. This action is not offered during a run.
  • Click the title, the objective and instructions or the priority directly to edit them in place, then choose Save or Cancel. Editing is available outside a run, for missions that are not archived. Add a dependency and Remove a dependency adjust the prerequisite missions; a circular dependency is refused.

Hover over an action or select it with the keyboard to read its explanation. Each action also shows its consequences before you confirm. If the mission changed while you were typing, refresh the page and check your request before confirming again. A lost network response is resolved with Check the save, without automatically repeating the action.

In the Add a comment block, a manager can choose Add a file, then Attach the file. The file can be added independently of the comment; each has its own save confirmation. You can also drag a file into this block, then confirm with Attach the file. Dropping keeps your comment and sends nothing automatically. Add one file at a time, with no folder. The limit is 25 MB per file. The file joins the mission, where members with access to tasks and the agent can view it. Adding it does not restart the mission; a run in progress may need to re-read its context.

Notify me is a personal choice: it flags in the Diadems bell when a mission is completed, blocked or has a result to approve. Updates are checked about every minute, even when you have closed the board. It does not resend events from before you turned it on. A notification opens the conversation where the mission was requested, straight to its latest notice, when you can view that conversation; otherwise it opens the mission’s page. Reading the conversation does not mark the notification as read. If you have allowed notifications on your device, an unread notification may also be sent there after a delay.

You automatically follow the new missions you create. When the agent creates a mission in the chat, it is attached to the person who asked for it, as soon as that exchange is identified. You can turn off Notify me without losing this link. For an older mission, the tracking you already chose is kept; identifying its requester later does not turn notifications back on.

In the agent’s menu, a Missions badge shows the number of your blocked missions, including when one of their steps is waiting for action. Hover over the menu or select it with the keyboard to see their names. Each mission is counted only once. The badge is independent of your notification choice.

An organisation owner or administrator can change the Owner directly on the parent mission’s page: click the name, choose a member with access to this agent’s Missions, then Save. Steps show the owner of their parent mission. This choice designates the person responsible for follow-up; it does not change the agent that runs the mission. The badge is attached to that person, and their tracking is on unless they have already turned it off. Other subscriptions are kept.

In Exchanges and follow-ups, Add a comment saves your text directly in the mission, with your name. Members with access to Tasks can view and add comments. They are part of the context the agent can read, particularly when work resumes; adding one does not restart the mission and does not guarantee an immediate reply. A question that needs a conversation can go through Talk about it with [name], which prepares a draft in the chat about the existing mission.

If sending is interrupted, Check the send looks for the comment already saved before offering a new attempt. The text and the pending send are kept while you navigate between cards, as long as the Missions view stays open. Comments are limited to 8,000 characters.

To create a mission directly, choose New mission. Enter a title, add your objective and instructions if needed, then choose a priority: normal, high or urgent. Two options are offered:

  • Organise into steps, selected by default: the agent can break the objective down, run the steps, then prepare the summary.
  • Run directly: the agent can start on the objective as you defined it, as soon as it is available.

In both cases, Create and hand over the mission lets the agent pick it up automatically. It is not a draft awaiting approval.

Direct creation is reserved for administrators and the workspace owner. It does not require turning on creation during conversations. It creates no personal conversation and sends no message to one. After saving, the new card appears on the board. If the response is interrupted, Check the creation lets you find it without sending again. The draft is kept while you stay in the Missions view.

To define your objective with the agent, Prepare with [name] opens a new conversation and fills the input field with a draft. You can edit it before sending. From a card, Talk about it with [name] prepares an exchange about that existing mission. These two actions require creation during conversations to be turned on; they send no message automatically.

The board and the open detail refresh every ten seconds while they are visible. Other boards and profiles are not grouped here. Access to Missions follows the rights of the Tasks section.

A mission requested in the chat stays linked to its original conversation. On the page, Original conversation opens that thread at the mission’s notice, if you can already view that conversation: your own, a conversation shared with you or, for an administrator, a conversation visible to the team. Another member’s private conversation is never revealed. A mission created with New mission has no original conversation.

In the agent’s Activity panel, missions in progress or to organise appear in What I’ve planned, under Ongoing: first those that began in the open conversation (In this conversation), with their owner and the progress of their steps. Blocked missions or those awaiting approval appear in What’s waiting for you, and those finished during the day in Today I finished…. A mission from the open conversation opens its page, like See the mission in the chat; another opens its original conversation when you have access, otherwise its page. These lines do not appear when there is nothing to report and are refreshed about every thirty seconds while the panel is displayed.