# The task panel, changes, and worktrees

> See a task’s agent, session, changed files, and memory beside the chat; review diffs; and run repository tasks in separate worktrees.

Section: Chat and tasks · Updated: 2026-11-19 · Canonical: https://nested.me/docs/task-panel

Chat tells you what the agent says it did. The task panel shows what it actually did: the files it changed, the machine it works on, and the memory it uses. Files, diffs, Desktop, Terminal, and runbooks open as view tabs beside **Chat**, so you never lose the thread.

## Before you start

- The task panel is a desktop feature (windows at least 1024px wide). On a phone, open **Task details** for the same information as a sheet.
- **Changes** and **Files** need a workspace on the agent. Some views are “Not available for this workspace”.

## Steps

1. Open a task and select **Show task panel**. **Use full width** hides it again; you can resize it.
2. Read the sections, described in the table below.
3. Select a changed file to open the review view as a tab beside **Chat**.
4. For a repository workspace, select **Manage worktrees** to see every worktree for that checkout.

## Panel sections

| Section | What it shows |
| --- | --- |
| **Agent** | The agent on this task, with **Agent settings** |
| **Session** | Desktop and Terminal for the agent’s machine — “Available when the agent is running” |
| **Changes** | Uncommitted changes, or the branch’s changes, with lines added and removed |
| **Files** | The workspace’s files |
| **Memory** | The memories this task uses; **Forget what this task saved** undoes what it wrote |
| **Resources** | The agent’s resource usage, when available |

## Reviewing changes

The review view lists **Changed files** with a filter. Switch the **Diff layout** between **Unified** and **Split**, and use **Diff settings** to **Wrap lines** or **Hide whitespace changes**. Mark each file **Viewed** to track progress; a file that changes afterwards shows **Changed since viewed**. **Keyboard shortcuts** lists keys for the next or previous file and change.

## Worktrees

A worktree lets a repository task work on its own copy of the code, so parallel tasks do not edit the same files. When you start a task in a **One repository** workspace, **Run this task** offers:

- **Local** — the main checkout.
- An existing **Worktree**.
- **New worktree**, with an optional **Worktree name**.

**Manage worktrees** opens the workspace view with **Files**, **Changes**, and **Worktrees** tabs. For each worktree you can **Sync** (update files), **Reset** (back to its base; local commits and changes are discarded), or **Delete**. Select several to act in bulk; worktrees **In use** are skipped. **Refresh** updates status only.

> [!WARNING]
> **Reset** discards local commits and changes in that worktree. Check **Changes** first.

## Example

Two tasks fix two bugs in the same repository. Start each with **New worktree**, so they never touch each other’s files. When the first finishes, open **Changes**, review the diff in **Split** layout, mark each file **Viewed**, then **Complete** the task and **Delete** its worktree from **Manage worktrees**.

## Questions

### How do I see which files an agent changed?

Open the task panel with **Show task panel** and read **Changes**. Select a file to open the diff beside the chat.

### Why use a worktree for a Nested task?

A worktree gives the task its own copy of the repository, so parallel tasks on the same repo do not overwrite each other.

[Open in Nested](https://app.nested.me/)

## Related

- [Chat, workspaces, and tasks](https://nested.me/docs/chat)
- [Desktop and Terminal](https://nested.me/docs/desktop-terminal)
- [Memories](https://nested.me/docs/memory)
