Tasks

Tasks are the main execution surface in OpenVibely. The Tasks page is a project board where users create AI coding work, run it, monitor progress, review output, and decide what happens to generated changes.

The Task Board

Open Tasks from the Workspace section of the sidebar. The board shows project work in user-facing categories.

Scheduled tasks are managed from the Schedule page. Chat tasks are internal to chat flows and are not normal board cards.

Creating A Task

Click + Add Task and fill out the modal.

The UI keeps the modal open and shows an inline error if the title conflicts with an existing task in the project.

Swarm Tasks

Enable Swarm mode when one request should be delegated across multiple task roles. A planner creates independent worker scopes, an optional reviewer checks the combined result, and an optional merger integrates approved work. Each child is a real task with its own thread, model assignment, worktree, diff, retry, and follow-up history.

Set the maximum planned worker count and default isolation in the task dialog, then create the parent in Active or Backlog. Active starts planning; Backlog defers the planner until you run the task or move it to Active. The board groups child status under the parent while still linking to every child task.

Max workers limits planned slices, not actual concurrency. Global, project, and per-model limits on the Workers page still determine how many children execute at once. See Swarm Orchestration for roles, isolation, reruns, review, and merge behavior.

Running And Monitoring

Tasks move through statuses such as pending, queued, running, completed, failed, cancelled, and blocked. The page listens for live task events so board state can refresh while work is happening.

While a thread response is active, the send control becomes Stop response. This stops the active model run and records cancellation in the thread. It is different from cancelling a queued follow-up before it starts or cancelling the entire task from the board/detail controls.

Around normal execution, lifecycle hooks can recall memory, prepare useful skills, and learn from completed work. Follow-up messages continue from the existing task thread and respect worker capacity, so they may queue when project or model execution slots are full.

Use task detail views to inspect execution output, thread messages, attachments, changed files, review comments, lifecycle activity, and worktree state.

When a task has an active goal, a Goal panel appears above the tab row showing the objective, status badge, agent reason, and last-checked timestamp. Goal settings live in the task edit dialog.

Reviewing Work

When a project has a repository attached, task execution can produce worktree-backed changes. Review those changes before merging or creating a pull request.

Diff Review

Open a task detail page and select Changes to inspect generated code. Worktree-backed tasks can show live branch and uncommitted diffs while work is still active, then fall back to preserved execution diffs after merge or cleanup. The diff viewer groups changes by file, supports large-file lazy loading, and lets reviewers attach comments before sending feedback back to the agent.

Related Pages