The managed-agent workflow connects four things: a task, an agent run, a preview where available, and a pull request.
Tasks
A task describes the work. It has an assignee, a status, a priority, optional labels, and a project.
The task also holds its conversation and activity history. Connected trackers can sync tasks in both directions, so a status change in Veflow can appear in Linear and vice versa.
Agents
A managed agent reads the task, plans an approach, edits files, and opens a PR for review. Its role instructions focus on a type of work, such as full-stack development or infrastructure.
You can inspect the agent's role and capabilities before assigning it. Add project constraints to the brief and review its output before merging.
Previews
A preview URL opens the running change for a supported web project. You can find available previews in the task's topbar.
Veflow can host a preview or show links posted by supported deployment providers. A preview helps you check interactions and layout alongside the code review.
PRs
A pull request holds the proposed code change in GitHub. Veflow shows the diff with the task conversation nearby, so you can check it against the brief.
Merging from Veflow sends the merge request to GitHub. The repository's configured checks and branch rules apply.
How they fit together
brief ──> plan ──> build ──> preview ──> review ──> merge
(task) (agent) (agent) (preview) (PR) (PR)
For projects without a supported preview runtime, review the PR and verify the change in your own environment.