Tasks Manager Settings

Pro Only

The first time you press Turn On, Wing asks for the Manager's settings; a project set up with the Manager on starts with their defaults. To change them later, select Tasks Manager Settings... in the Tasks tool's options menu, click the settings icon on the Manager's bar, or press the Settings... button next to Task Scheduling in Project Properties. This works while the Manager is off too. The settings are on three tabs: Scheduling, Permissions, and Commits.

While the Manager is on, its Permissions and Commits settings are used for all of the project's agent work, in place of the Preapprove settings, Commit Mode, and Show Summaries on the AI Agent tab of Project Properties. This covers its workers, the sessions and tasks you start yourself, the Fix features, and every commit. They start from the values on the AI Agent tab, so turning the Manager on without changing them keeps the same permissions and commit behavior, except as noted for Edits for below. See Configuration for details.

The Scheduling tab holds these settings:

Agent -- Which agent runs the Manager's own session. This defaults to the agent the project is set up for; the worker queues use their own agents as usual. Some agents (Codex, Cursor, goose and other agents run over ACP, and OpenCode) cannot be prevented from editing files, so for them the Manager's read-only role is only an instruction. Wing warns about this but lets you use them anyway. Wing also warns when an agent, such as Antigravity or Cursor in their own terminal interfaces, does not tell Wing that it has stopped to ask for approval. A Manager or worker waiting on such a prompt shows as running, with nothing on the Questions tab, so answer it in its session if it stops making progress.
Decisions -- How autonomous tasks handle decisions they would otherwise ask you about:
- Decide and Report makes the judgement call, records it, and carries on, asking only when the work truly cannot go on. Every decision is listed with the task on the Review tab so you can object to any you disagree with.
- Ask Me First does everything that doesn't depend on your answer, then asks before any significant decision and waits for you.
This is only an instruction to the Manager and the workers, and you can refine it by talking to the Manager -- for example, "ask me about anything that changes a file format".
Maximum writing workers -- A ceiling, not a target, on how many worker queues may be changing files at once. All queues share one working copy, so the Manager raises concurrency up to this limit (five by default) only when it judges that the tasks touch different files. Read-only research tasks don't count against the limit. With more than one writing worker, which task changed which file can occasionally be unclear on Review. With one, the next writing task waits until the last one's changes are committed, so each commit holds one task's work.
Concurrent agent test runs -- How many agents' test runs may go at once (four by default). A run beyond this waits for one to finish, as does a run of the same files as another agent's or your own live run. Time spent waiting counts toward the run's time limit, and its result tells the agent how long it waited. This limits only agents' runs: your own runs in the Testing tool never wait for it. See Running Tests.
Resume previous Manager session -- When checked, turning the Manager on again continues its earlier session and context. Uncheck it to start each time with a fresh session.
Start found tasks -- Which of the tasks the Manager proposes and the bugs agents find it may mark Ready, so that they run right away instead of waiting for you:
- Never leaves them all as a Draft for you to decide on.
- Related Tasks Only starts only those closely related to the task they came from, for example a test that the task's change broke, a bug found in the code the task worked on, or the plan of research you ran. This is the default.
- Always starts any the Manager judges you would want run, leaving bugs in unrelated code for you.
- As Described: lets you write your own policy in the box below it, such as "Start fixes for failing tests and bugs in code my tasks changed, but leave new features and refactoring for me". The Manager applies it to each task, and leaves a task for you when it is unsure.
Each task the Manager starts is listed under Decisions, where you can undo it.
Maximum found tasks started per hour -- A last-resort limit on how many found or proposed tasks the Manager marks Ready in any hour. Past it, they stay a Draft for you.
Split mixed or broad tasks -- Whether the Manager splits a Ready task into separate tasks, so that each is reviewed and committed on its own and work on different files can run at the same time. It splits a task that holds independent pieces of work, such as a fix with an unrelated request added at the end. A request too broad to carry out as written is researched first, and once its plan is accepted the Manager carries it out as one task or files its steps as separate tasks. The original task goes to History, marked as split.

The Manager decides whether the new tasks are Ready or Draft. Parts of a task you wrote out in detail are usually Ready, as are the steps of an accepted plan, except optional ones, which are a Draft for you to decide on. The new tasks go in the original task's goal, another of your goals, or a new goal the Manager makes for large new work. The Manager removes a goal it made once its tasks are done, and never removes your goals.
- Always splits without asking. This is the default.
- Ask Me proposes each split on the Questions tab first.
- Never runs each task as written.
Each split is listed under Decisions, where you can undo it until one of its tasks starts.
Research notes directory -- Where Research This writes its notes on found problems (see Found Problems). Blank uses the private .TASKS/notes directory, which version control already ignores.

The Permissions tab has two sections. See Configuration for how these reach each agent.

Preapprove sets what agents may do without asking, in sessions that ask for approval:

Edits for -- All Project Directories lets agents edit files in the project's directories that are under version control. Nothing (Prompt Each Time) makes them ask before every edit. There is no list of chosen directories here, so a project whose AI Agent tab uses Only These Directories starts with Nothing (Prompt Each Time).
Running commands -- Whether agents may run any shell command without asking.
Revision control commands -- Whether agents may run hg, git, and other revision control commands, such as status, diff, and log, without asking, even when running other commands is not preapproved. This only affects whether agents ask first. Whether the Manager's workers commit is set on the Commits tab.

Allow Tools lists capabilities that agents in the project may use while the Manager is on. Unchecking one keeps every agent from it: Wing launches every session without it, and the Manager can't give it to a task. A change takes effect as each session next starts. The capabilities are web search and fetching web pages, driving a web browser, outside services linked to the agent's account, publishing shareable pages and designs, timers, cron jobs, cloud routines, and push notifications, and pushing to remotes with git or hg.

Pushing, when unchecked, is refused whenever an agent runs a push command, in any session, starting at once. A script or alias that pushes is not detected, so this does not replace the access controls on your remote repositories.

Only the capabilities the Manager's agent can be kept from are listed: for Codex, web search, timers, and pushing; for Copilot, Cursor, and Antigravity, only pushing. OpenCode can't be kept from any of them, so the section is hidden.

The Commits tab holds these settings:

Commits -- Review/Commit Manually leaves finished work on the Review tab for you to review and commit. Commit Automatically lets the Manager commit each queue's work once its tests pass; the committed tasks still go to Review, marked Committed, so you can look them over and mark them complete. Describe Policy: lets you write your own rule in the box below it, such as "Commit code automatically, but leave documentation changes for me to review". The Manager applies the rule to each commit: it commits the files the rule allows and leaves the rest uncommitted, with the tasks that changed them still on Review. When it is unsure whether the rule allows a file, it leaves it for you.
This setting decides when the tasks the Manager runs are committed; its workers don't commit on their own. Until you commit or discard work left for you, a queue whose tasks changed the same files starts no task that may write files. Plan-mode tasks, and queues working on other files, go on. See The Tasks Manager Agent for how the Manager commits.
Commits in sessions you start -- How work in sessions and queues you start yourself is committed, and who writes the message for every commit you start, including commits of the Manager's tasks. It has the same choices as Commit Mode. In the two choices where Wing writes the message, agents end each task with the summary Wing builds it from.