> ## Documentation Index
> Fetch the complete documentation index at: https://docs.resolve.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Tasks

Tell Resolve what to do, when to run, and where to report. Tasks can run on a schedule or in response to an event to monitor deployments, triage alerts, generate reports, and more, using the same investigation abilities Resolve brings to a live incident, but on autopilot.

You create tasks in plain language ("every Monday morning, summarize last week's alerts and DM me") in a chat with your agent, from a Slack or MS Teams thread, or in the Resolve UI. Everything a task can do, your agent can also do when you ask in chat.

## When tasks run

**On a schedule.** Run at an interval or a cron expression, in your time zone: hourly deploy checks, daily alert digests, weekly report generation.

**On events.** Ask your agent to watch a Slack or MS Teams channel for topics you care about ("watch #deploys for rollbacks, check the SLO dashboard, and DM me if things are trending poorly"). When a matching message appears, the agent wakes up and follows your instructions: summarize, check dashboards, notify you, or kick off deeper work.

**On demand.** One-off tasks run immediately or at a due time ("tomorrow at noon, check whether checkout error rates recovered"). Running tasks can also file their own follow-up tasks when they discover new work.

## Where tasks report

Each task has a reporting destination: a Slack channel or thread, a direct message, an MS Teams conversation, or its task page in Resolve. Reports, files, and links the task produces are attached to the task's run history so you can review any run later.

## What tasks can read

* **Your integrations:** anything your configured integrations expose (metrics, logs, traces, dashboards, code, deploys, tickets), scoped to the teams the agent belongs to.
* **Your MCP integrations:** any tools exposed by MCP servers you've connected.
* **Investigations:** search and read past and in-flight investigations, their findings, and their evidence.
* **Your knowledge base and the agent's memory:** team runbooks and docs, plus learnings the agent has accumulated.

## What tasks can do

### Actions from your integrations

Any action included in your configured integrations: query a dashboard, fetch logs, look up a deploy, comment on a ticket. All actions are subject to the permissions of that integration.

### Send messages

Post Slack or MS Teams messages, reply in threads, send DMs, add reactions. Personal agents deliver privately (DM) by default and only post publicly in a channel when you've explicitly allowed it.

### Actions from MCP integrations

Any action exposed by the MCP servers you've connected, alongside native integrations.

### Internal actions: things Resolve can change inside Resolve

These are the built-in actions your agent can take on Resolve itself. Each one is a named tool call, visible in the agent's activity feed, and scoped to the agent's own team (or, for personal agents, to you).

**Create and update tasks**

The agent manages its own work queue. Ask it to create a task, change an existing task's instructions or schedule, pause one, or wind one down.

* Tasks are **one-shot** (run once, now or at a due time), **recurring** (interval or cron, time-zone aware), or **projects** (groupings of related tasks).
* Lifecycle you can steer in plain language: active, paused (waiting on you), done, or canceled. Only an explicit status change stops a recurring task; a single run finishing never silently kills the schedule.
* Running tasks can file follow-up tasks for newly discovered work, including scheduled or recurring follow-ups.

**Watch channels (event-driven triggers)**

Ask the agent to watch a Slack channel for keywords and act when they appear. Each ask creates an independent watch rule (a channel can have several) with your interest recorded in your own words plus an instruction for what to do when it fires. Rules can be grouped under a project.

**Recommend knowledge updates**

The agent can propose new runbooks and edits to existing team docs, either from a conversation ("update my knowledge with what we’ve discussed here") or automatically by reviewing completed investigations for lessons.

**Create reports and files**

Tasks and chats can produce durable outputs in the agent's workspace:

* **Markdown reports:** digests, summaries, audit write-ups.
* **Rich HTML:** interactive reports with charts, visualizations, and buttons.
* **Images:** generated diagrams and visuals, rendered inline.

Files the agent writes into its workspace are attached to the task's outputs and viewable (and shareable) from the task page and run history in Resolve.

**Run your skills**

Skills are reusable instruction packages you define at the org, team, or personal level: your encoded procedures. The agent matches tasks and requests against its skill listing and loads the right skill's instructions before acting, so your procedures drive recurring workflows.