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

# Assign work and automate it

> Choose between chat, Computer Tasks, repeating work, heartbeats, and delegation.

Vida provides several ways to give a Computer Agent work. Choose the narrowest option that matches the job.

| Work type              | Best for                                                                                    |
| ---------------------- | ------------------------------------------------------------------------------------------- |
| Direct chat            | Interactive requests, clarification, and one-time collaboration                             |
| Computer Task          | One defined piece of work to run now or at a future time                                    |
| Repeating Task         | Work that should run on a predictable recurring schedule                                    |
| One-off scheduled Task | Work that should run once at a specific time                                                |
| Heartbeat              | Periodic awareness checks where the Agent decides whether anything material needs attention |
| Delegation             | Work requested by another Vida Agent during a conversation                                  |

## Write outcome-focused instructions

For every Task, describe:

* the result you need
* the systems and information the Agent may use
* the time period or records in scope
* how the Agent should verify success
* actions that require confirmation
* what should be reported if work is blocked

Avoid vague recurring instructions such as “check everything and report problems.” Define what qualifies as a legitimate issue or measurable improvement so routine checks do not become noisy.

## Review the work conversation

Computer Tasks and repeating runs create linked Vida conversations. Open the conversation to review the instructions, progress, tool calls, results, and final response.

An accepted or started Task is not proof of completion. Check its final status and verify important changes in the destination system.

## Start recurring work safely

Create repeating work in a paused state when possible. Review the schedule and instructions, run a controlled test, inspect the result, and enable it only when it behaves correctly.

Pause repeating work when its source system, permissions, or business rules change. Delete completed one-off Tasks when their Task record is no longer needed; their linked conversation can remain as work history.