> For the complete documentation index, see [llms.txt](https://alludium.gitbook.io/alludium-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://alludium.gitbook.io/alludium-docs/inbox-and-tasks/working-with-tasks.md).

# Working with Tasks

Tasks give repeatable work a durable place to live. A task can be created from the Inbox, from a project, from onboarding or setup, or from an automation or agent workflow.

## Task State

A task usually moves through visible states such as:

* To do
* In progress
* Done

Some workflows may expose additional state, assignment, approval, or output requirements depending on the task type and workspace configuration.

## Task Detail

Task detail is where you continue the work. It can include:

* Task title and description
* Current status
* Conversation history
* Required inputs
* Child tasks
* Linked files
* Output or completion fields
* Activity or execution history

The exact layout depends on the task type and the kind of work being performed.

In the current task detail view, the conversation remains visible beside task controls. Common controls include **Output**, **Details**, and **Files** tabs, plus actions such as **Reassign** and **Mark Complete** when your role and the task state allow them.

## Output, Details, And Files

Use the task tabs to inspect different parts of the task:

| Tab         | Use It For                                                                                                                                          |
| ----------- | --------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Output**  | Review guided actions, completion output, or task-specific results. Some tasks may show that there are no pending guided actions.                   |
| **Details** | Review workflow state, status, update time, schedule context, timeline, chat context, configuration, and execution log information where available. |
| **Files**   | Search, upload, and review files linked to the task. Files uploaded here are available to the task context.                                         |

## Child Tasks

Some tasks create or coordinate child tasks. Child tasks let larger workflows split work into smaller pieces while keeping the parent task as the coordination point.

Use child tasks when:

* A workflow has clear substeps
* Different outputs need separate review
* A setup task needs to coordinate several systems
* A project task needs supporting research or follow-up

## Completing Work

Some tasks can be completed once the conversation or manual work is done. Others require structured completion output before the task can move to a terminal state.

When a task type requires structured output, complete the required fields before marking the task done. If required output is missing or invalid, the task detail should prompt you to fix the missing fields before completion.

Use **Mark Complete** only when the task output is ready for review or the task no longer needs follow-up. If the task is owned by the wrong person or agent, use **Reassign** before continuing.

## Task Conversations

Task conversations are scoped to the task. This keeps the context close to the work item and avoids mixing unrelated conversations.

Good task prompts include:

* The outcome you want
* Any relevant project or file context
* What should be checked before completion
* The expected output format when it matters


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://alludium.gitbook.io/alludium-docs/inbox-and-tasks/working-with-tasks.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.