---
sidebar_position: 5
---
# Task Power Features

The task page includes tools for branching, recovering, sharing, and reshaping work after a task has already run. Use these features when you need to compare another approach, recover from a bad turn, or turn useful task context into future work.

## Sharing Tasks

Task links are normal CoderFlow links. They do not bypass authentication, and copying a link does not change who can see the task.

Use the **Share** button in the task header to copy:

- **Copy Task Link** - a direct link to the current task
- **Copy Task Group Link** - a link that opens all loaded variants in the group
- **Copy Task ID** - the task identifier for chat, tickets, or support notes

![Task share menu](/docs-images/task-power-share-dropdown.png)

By default, tasks are shared with users who have `tasks:view` permission on the task's environment. The task owner, or an environment admin with the matching `_any` permission, can open **More actions** and choose **Make Private** to lock the task.

When a task is private:

- The owner can still view and change it.
- Environment admins with `tasks:view_any`, `tasks:change_any`, or related `_any` permissions can still operate on it.
- Other environment members no longer see it in task lists or task stats, and direct links return a permission error.

Choose **Make Shared** from the same menu to restore the environment-level sharing behavior.

## Fork a Task

Forking creates an independent task from a finished task's current state. Use it when you want to continue from the same context without changing the original task.

1. Open a task that is **completed**, **failed**, or **interrupted**.
2. Open **More actions**.
3. Choose **Fork Task**.
4. Confirm the fork.

![Fork task confirmation](/docs-images/task-power-fork-dialog.png)

The fork gets its own task ID, container, task history, branch selections, attachments, and copied workspace state. If the original task container is still running, CoderFlow captures the live workspace state; otherwise it falls back to saved task state when available.

Forks are useful when:

- The first approach is close, but you want to explore a different direction.
- A task failed after producing useful local changes.
- You want to keep the original result untouched while trying follow-up work.

A fork starts as a separate task that can be continued with a normal follow-up. It is not a replacement for resubmitting the same task to multiple agents.

## Rewind a Task

Rewind lets you move the conversation context back to an earlier follow-up point. Use it when the agent took a wrong path and later follow-ups are making the task worse.

1. Open the task page.
2. Click the **Follow-Ups** count in **Task Details**.
3. Choose **Rewind to initial** or **Rewind to #N**.
4. Optionally explain why you are rewinding.
5. If available, check **Also rewind files to this point**.
6. Submit a normal follow-up to continue from the rewind point.

![Rewind picker in follow-up history](/docs-images/task-power-rewind-picker.png)

Rewind points are based on the initial task instructions and each follow-up instruction. Rewinding to follow-up `#2`, for example, keeps the initial task and the first two follow-ups as the active conversation branch, then excludes later follow-ups from the replay context.

### Conversation vs. File State

Every rewind prepares conversation context. File rewind is separate and appears only when CoderFlow has enough turn-patch metadata to restore files safely.

If you do not rewind files, the agent keeps the current filesystem. CoderFlow warns the agent when the current files may contain changes from after the rewind point, but you should still check the changed files before relying on old context.

If you do rewind files, CoderFlow tries to restore repository contents to the selected point and then refreshes the changed-files view.

Rewind requires the task container to be available and not actively running. If the container has stopped, start it before rewinding.

## Resubmit a Task

Resubmit starts new task runs from the same task setup. It is best when you want a fresh attempt with the same environment, branches, and base instructions.

1. Open **More actions**.
2. Choose **Resubmit Task**.
3. Select one or more agents.
4. Edit the instructions if the next attempt should differ.
5. Attach any new files or screenshots.
6. Decide whether to add the new run as a variant.
7. Click **Launch**.

![Resubmit task modal](/docs-images/task-power-resubmit-modal.png)

Resubmit preserves the original branch selections, environment variables, Jira link, source objective link, and task files. New attachments are added to the copied task files and replace files with matching names.

You can launch more than one agent from the resubmit dialog. If you select multiple agents, CoderFlow creates a task group for the new runs. If you check **Add as variant to existing group**, CoderFlow adds the new tasks to the current group instead.

Resubmit is different from a follow-up:

- A follow-up continues the same task and container.
- A resubmit creates new task IDs and new containers.
- A fork creates one independent continuation from the current task state.

## Save as Objective

Use **Save as Objective** when a task has useful instructions that should become reusable planning context.

1. Open **More actions**.
2. Choose **Save as Objective**.
3. Review the pre-filled name, environment, agents, and instructions.
4. Edit the instructions into objective-quality requirements.
5. Click **Save Objective**.

![Save as Objective modal](/docs-images/task-power-save-objective-modal.png)

The new objective keeps the task's environment, branch selections, Jira link, and supported agent settings such as Claude effort level or Codex reasoning level. It does not automatically summarize the task result for you, so revise the instructions before saving if the task outcome changed what the next agent should do.

## Activity Snapshots

When a task page opens, CoderFlow loads a small activity snapshot before replaying the full activity stream. This snapshot scans the tail of the task's debug stream and shows the latest agent response in the **Latest Update** area quickly.

The snapshot is not a separate artifact you manage. It is a fast first view while the full activity feed loads. If the task has no activity stream yet, the task page simply waits for the normal feed.

## Customize the Task Page

The task page layout is local to your browser. These controls help keep busy tasks readable:

- Drag a section by its handle to reorder the page.
- Collapse a section by clicking its header.
- Hide a section with the `x` control in the section header.
- Use **Show** to restore one hidden section, or **Show All** from the dropdown when multiple sections are hidden.
- Use **Hide all sections** to clear the page quickly.
- Use **Reset Layout** to restore the default order and clear hidden or collapsed section state.
- Use the expand control on a section to view it full screen.

Dragging is disabled while a section is expanded. Resetting the layout also clears saved hidden and collapsed state for the task-page sections.

## Reorder Variant Tabs

When a task group is open, variant tabs can be reordered by dragging them. The order is saved to the task group, so it follows the group view instead of being only a local browser preference.

Use tab ordering to put the most important variants first before comparing, judging, or approving a winner.
