Tasks and conversations

A task is a conversation centered on one goal. It keeps your request, Aru’s responses, tool activity, and results together. Start a new task when you move to a different goal.

Start a task

Choose a project.
Select New task.
Check the model, permission mode, and workspace in the composer.
Describe the work and desired result, then send the request.

Include the purpose, source material, output format, and save location. Mention files that must not change or steps you want to review first.

In a Git project, open the gear menu before sending the first message to choose a branch or turn on New worktree. The worktree is created when you send that message. See Isolate work with worktrees for details.

Compare the monthly results in data/ and summarize the main changes. Keep the source files unchanged and save the result to results/performance-summary.md.

Attach files and images

Use the attachment menu to add files or images. To reference a project file, type @ and choose it. Confirm the file and path before sending.

Attaching a file does not automatically authorize editing it. Say whether the file is reference material or should be modified.

Pasting 5,000 or more characters automatically attaches the content as a text file. Hold Shift while pasting to keep a long paste in the message body. Side Chat uses the same behavior.

Aru composer with the Files and folders menu and an @ file mention

Follow progress

The conversation shows responses and tool activity. Expand a tool result to review file reads and edits, commands, or service requests.

Status	What to do
Running	Review the current step and tool results.
Input needed	Answer the question or provide missing information.
Permission needed	Review the target and action, then approve or deny it.
Error or retry	Review the failed step and supply the missing information or connection.
Complete	Review the final explanation and result files.

If Aru delegates work, a delegated-task or subtask list may appear. Open a subtask to inspect it. Parallel execution depends on the work and available tools.

Project analysis with progress notes, Called tools and ran commands, a to-do list, and Shell Command activity

Add direction or stop work

You can send more instructions while a task is running—for example, to add material or change direction.

Include follow-up actions by owner in the presentation. Add a table of owners and due dates to the final slide.

Select Stop to stop the current run. File or service changes completed before the stop remain in place. Review the state before continuing in the same task.

Working status, a queued message with edit and send controls, and the composer stop button

Review and revise results

Open result links and compare edited files in Review changes. For revisions, name the item and change in the same conversation.

Add percentage change to the second table in the summary. State the calculation basis below the table.

Find and organize tasks

Use Search tasks to find a task by title or path.
Use Rename to give it a goal-oriented title.
Use Pin task for tasks you revisit often.
Drag tasks to reorder them.

Deleting a task may permanently delete its conversation and subtasks. This does not undo file changes in the project.

Branch a conversation

To continue in another direction, select Branch in new chat below a completed answer. The new chat includes the conversation through that answer and keeps the current model, reasoning, speed, and approval settings. Enter the next request in its empty composer.

Branch in new chat below a completed answer and numbered branched tasks in the project list

The branched chat shares the original working folder and files; it does not create a worktree automatically. For independent file changes, choose a worktree before sending its first request. Use Side Chat for a quick question alongside the current task.