Desktop Agents projects: a project manager and a board
WidgetStore desktop Agents projects: a manager reads your repo and suggests issues; agents work on the ones you pick in parallel, and results wait for your approval.
A project is a resident project manager plus a board. You set the goal, pick suggestions and approve results; the manager and worker agents plan, dispatch, follow up and review.
Create a project
- Open Agents in the desktop sidebar and click Projects (or the target icon at the top).
- Describe a goal, e.g. "Add dark mode to the settings page and verify light and dark screenshots".
- Choose a repository (it must be a git repository; recent ones are listed).
- Choose how to start:
- Suggest first, I'll pick (default): the plan lands in Suggested and you tick what to start.
- Start right away: the first batch is dispatched as soon as it's planned.
- You can also tick Autopilot (see below).
- Click Create project (⌘↵). For other agents, concurrency or a check command, use More options….
Defaults: Claude Code manages; workers may edit files, but commands still ask you in the terminal; each issue gets its own worktree and branch; up to 3 issues at a time; small changes that pass the check command (≤ 20 files / 600 lines, no sensitive files) merge into the local base branch automatically, while larger ones or failed checks wait in For review for your approval (from 1.23.7; project settings can make everything wait for you).
Left: talk to the manager
- The manager reads the repo's rules, docs, past issues and each worker's live state, reports progress and answers questions like "why is this taking so long".
- Its next-batch suggestions appear as a checklist: click Start selected, or Dismiss the rest.
- When it needs a decision it asks clearly (a yellow card), and the question also appears in Needs you.
- Issue ids (like WF-3), PRs, branches and document names in messages are clickable.
- Under the input, This Mac / This computer is where work runs; Cloud is coming soon.
Right: the issue board
Each issue has the project prefix and a number (like WF-12). States: Suggested · Queued · Working · Needs you · For review · Done · Dismissed.
- List: ordered Needs you → For review → Working → Queued → Suggested. Working rows show the latest terminal line and a step bar live.
- Board: drag cards to change state, e.g. drop on Queued to start, drag from For review to Done to approve and merge, drop on Dismissed to cancel. Moves that aren't allowed (a suggestion straight to Done) explain why.
- Library: the manager's memory (brief, decisions, lessons), daily progress briefs, changed Markdown documents, PRs, branches, review evidence and test results.
- Every issue shows its artifacts: PR, branch, commits, lines changed, changed documents, checks passed or failed, and cost.
- Search covers titles, files and branches.
Issue panel
Click an issue to open its panel: the current step, what's blocking (and how to unblock), the manager's review, the worker's report, acceptance criteria, time and cost, changed files, screenshot and recording evidence, the latest terminal output, and related messages. Actions:
- Approve & merge: merges into the base branch (the main folder must be on the base branch with no uncommitted changes).
- Send back: write what to fix; it's sent to the worker as is.
- Continue / Message the worker: delivered when the worker is free.
- Open terminal: jump straight to a worker waiting for your approval.
- Send to chat: opens Messages so you can send the issue as a card to a friend or group.
Needs you
Needs you at the top of the sidebar gathers everything waiting for you across projects: the manager's questions, issues ready for review, blocked issues, standalone tasks waiting, and suggestions to pick. The sidebar badge shows the same count, and new items send a system notification.
The manager's memory
Each project has three documents: Project brief, Decisions, and Lessons and rules. They go with every plan and every worker. Edit them in the Library. When you dismiss something and say why, the reason is added to the lessons so similar work isn't proposed again.
Autopilot
Turn on Autopilot at the top of a project and, whenever a batch is finished, the manager plans the next one toward the goal and starts it right away (Loops are now this switch):
- Proposals are filtered first: anything unrelated to the goal, open decisions, work your lessons rule out, and things already judged not worth doing are skipped.
- If workers find nothing to change twice in a row, it re-plans once, then stops and tells you why.
- Daily limits on issues and estimated cost (default 6 issues and $5, editable in project settings); it uses your own agent plans.
- Small changes that pass review (≤ 20 files / 600 lines, check passed, no CI, deploy or secret files) merge into the local base branch automatically; the rest wait for your approval. It never pushes. Project settings can make everything wait for you.
Pre-approved commands
Project settings hold a list of pre-approved commands (one prefix per line). Matching commands run without asking you in the terminal; everything else still asks.
- New projects start with read-only and build commands:
git status,git diff,git log, plus the repository's test, lint, typecheck and build commands. - Push, delete, install, history-changing commands and ones with
;|&&can't be added. - When workers keep stopping on a safe command, the manager suggests adding it. The suggestion appears in Needs you and only takes effect when you click Allow.
- Works with Claude Code for now; Codex and others still ask in the terminal.
Signals
Signals check the repository on a schedule and open issues automatically when something breaks, with evidence links (such as the CI run):
- CI failures (GitHub Actions; needs
ghsigned in on this computer) - Check command fails (the project's check command by default)
- Lighthouse drops (enter "URL minimum", e.g.
https://example.com 90) - New Sentry issues (needs
sentry-clisigned in) - Unchecked list items (enter list files in the repository)
Turn each signal on or off in project settings. The same problem isn't opened twice, things you dismissed aren't raised again, and problems that come back after a fix are reopened. With Autopilot on they start right away; otherwise they land in Suggested. The "N signals" button at the top checks right away.
Fast and steady: how workers run
Requires desktop 1.23.7 or later. When the worker is Claude Code, it runs natively headless: before it starts, the manager writes one complete set of instructions and the worker carries it through in one go. While it works, nothing is injected into its session: no messages from the manager, no background events, and workers can't message each other (they used to wait on each other and needed your approval). Anything you send with "Tell the worker" is handed over when the current run ends.
- Automatic wrap-up: if the project's check command passes and there are changes, the issue passes review and is committed to its branch. Small changes (≤ 20 files / 600 lines, no sensitive files) are merged into the base branch by default (switch to "wait for me" in project settings). Only issues without a check command, or whose check fails, go to the manager for a closer look.
- No stopping to wait for you: if a run stops clearly unfinished (asking "shall I continue?", or only a plan), another run starts automatically in the same session, up to 3 times. If the worker's report starts with BLOCKED, the issue goes straight to "Needs you".
- Per-issue limits: by default 2 million tokens (cache reads excluded) or 30 minutes of run time. At the limit the run stops and wraps up (keeps its changes and reports); past that it's reviewed as is. Research issues are limited to 10 minutes and deliver a findings document. Above 160k tokens of context, the next run starts a fresh session with a summary of the previous one. You can change all of this in project settings, and pick the worker's model and reasoning effort.
- See where the time went: the issue panel's time breakdown separates queued time, model thinking, tests, builds, waiting for your approval or answer, and review, plus interruptions, tokens and context size. The project header shows how many issues were delivered and merged today, tokens spent, average time per issue, time to the first result and the share of time spent waiting for you. Issues that used over 500k tokens without any change are flagged in red.
- The manager now splits work into issues of 15–30 minutes, each with a clear acceptance command and a real deliverable, instead of broad "research / verify / coordinate" tasks. Independent issues start in parallel (3 at a time for new projects).
Daily progress brief
Each morning (after 8 a.m. local time) projects with activity get a progress brief: what's done, what's waiting for review, what's blocked, what's next, and today's cost. It's saved in the Library and linked in the chat. You can also click Write a brief now in the Library.
Keyboard
j / k to move, Enter to open, Esc to close the panel, / to search, c to chat with the manager, 1–3 for List / Board / Library, and ⌘K (Ctrl K on Windows and Linux) to jump to any project, issue or action.
Safety
- The manager only reads the repo: no file edits, no commands. Each worker edits in its own worktree and never pushes.
- Merges only go into your local base branch; pushing and releasing are always up to you.
- Project records, chat and documents stay on this computer.
Last updated: Nov 18, 2026