Reviewing Tasks
Pro Only
The Review tab of the Tasks tool lists the finished tasks that are waiting for your review, grouped by the queue they ran in. The group whose queue finished a task last is listed first. While you stay on the tab, the groups keep their order and a new group is added at the top.
Each group's header names the queue and counts the files its tasks changed. From the header you can list the changed files, start a review of them, or commit them. A review always covers the whole queue, since several tasks may have changed the same file. Wing keeps track of the files the queue's tasks touched, so other uncommitted changes in the working copy are left out.
When the Tasks Manager is set to commit, it commits each queue's work once its tests pass, and the tasks arrive here marked Committed. They stay until you mark them complete, so you can still read their reports and ask for changes. See Tasks Manager Settings.
Task Reports
A task that ran autonomously shows its report: a summary of what it did and the judgement calls it made on your behalf, each with its reasoning and the alternatives it considered. Read these before you commit; to object to one, use Revise... as described below, either before or after committing. When an agent commits a queue, a task in it that changed no files stays here while it has questions or a report for you.
The triangle at the left of a task's row collapses the row to its heading and report summary, and expands it again. Show New Review Tasks Expanded in the tool's options menu sets how new tasks arrive. When the agent's response is available, Transcript at the bottom of the row shows or hides it.
Each task's row offers:
- View Changes -- Shows only this task's changes in the diff viewer. When the task's work is already committed and Wing can open a review of those commits, this is Review Changes, where you can revert, edit, or comment on the changes and submit them as a revision request.
- Revise... -- Asks for changes, described below.
- Show Session or Resume Session -- Shows the agent session that ran the task, or resumes it in a new instance of the agent if nothing is using it. Typing a follow-up there moves the task back to the Execute tab. Shown only when the session can be resumed.
- Mark Complete -- Moves the task to the History tab without reviewing or committing it. Without version control, this is Done.
- Reset -- Returns the task to the Plan tab, to edit and run again.
Asking for Changes
Revise... asks for a change to the whole task, or to one of the decisions it reported. The Tasks Manager decides whether the task's own session, a follow-up task, or no change addresses what you wrote, and runs that work in one of its queues, whichever queue the task first ran in. If the task's session is still the current one of a queue you started yourself, Wing waits until that queue is idle and then moves the session to the Manager's queue. Your queue starts its next task in a new session. While the Manager is off, an agent addresses your request in the task's queue.
The task's status shows what is happening with your request: with the Tasks Manager, sent to the task's session, being done in the tasks named, or that no change was needed. Until the request is taken up, the status reads Revision pending and says what it is waiting for, such as a writing slot, and Mark Complete asks before dropping it. Meanwhile the link reads Revise Again. The row lists your review comments, each with its state and what was done about it, and Withdraw closes one that no longer needs to be addressed.
Plans
A task that ran in plan mode, or researched a found problem, may report a plan of work instead of changes. It waits here marked Plan to act on, and Make Tasks in its header opens a dialog for choosing which steps become tasks. Save Draft files them as Draft tasks in the task's goal, and Run Now runs them. With the Tasks Manager on, the Manager makes the tasks and schedules them. With it off, you also choose one task for the whole plan or one per step, and Run Now starts them one after another in the default queue.
Once tasks are made from its plan, the task stays here naming them, and moves to History when they have all finished. Mark Complete moves it sooner. A plan-mode task that is still planning waits on the Questions tab instead; see The Questions Tab.
When a task revises its plan after tasks were made from it, the tasks from the earlier plan that have not started move to History, even ones you edited. The link reads Plan Revised: Make Tasks, and the dialog leaves unchecked the steps that the remaining tasks already do. The task does not move to History until the revised plan is made into tasks.
Reviewing and Committing a Queue
Once a queue has a task awaiting review, its header offers:
- Start Review -- Asks the queue's agent to open Wing's diff viewer on the queue's changed files. Disabled when there are no uncommitted changes. While another review is in progress, the request waits and runs when that review finishes.
- Commit -- Asks the agent to commit the queue's changes without reviewing them first.
The REVIEW icon at the top right of the AI Agent tool does the same as Start Review for the session's queue, and the drop-down beside it lists the queue's changed files. You can also ask an agent to commit only some files, for example "commit the source files but not the documentation", and it starts a review of just those files.
The Diff Viewer
However a review is started, Wing opens its diff viewer on the changes. In it you can move between changed files and their hunks, revert hunks you do not want to keep, and click the pencil icon between hunks to comment on one for the agent.
To finish, click the green check mark in the toolbar. This commits the changes, unless you left comments on hunks, which send the task back to the Execute tab for the agent to act on. The toolbar's pencil icon always sends the task back, with an overall comment.