1.5.0 (2026-11-14)

Demo

• The first demo start adds a fictional Mars-gadget startup (team, agents, a small git project with a backlog), so every page has something to show.
• npm run demo:reset stops a leftover demo server and clears the demo data (on Windows the old server could keep the database locked).
• Browser tests (npm run e2e) run the app in a real browser against the demo data, and CI runs them. A test walks the full flow: a task merges, a retried task asks for approval, the sprint is released.

Documents

• Two new General guides: Engineering standards and UI guidelines. They are written for any project, so agents can follow them everywhere. Your own edits to the other guides are left alone.

Accessibility

• An automated scan checks every page in both themes, plus dialogs, a form with an error, an open dropdown and the approval banner. It found and fixed: the sidebar project list, links told apart only by colour, amber text and the green badge too dim on the dark theme, unnamed controls (logo upload, model picker), the usage chart, scrolling pages that keyboard users could not reach, and the Deny button.
• Keyboard and screen-reader fixes: Scrum backlog items open from their title, the "Sprint" back link is a real button, a task's check rows open with Enter or Space, the Usage chart days can be reached with Tab, and the Chat message box is labelled.

Changes

• Faster first load: pages are fetched when first opened (about half the download).
• The server sends a Content-Security-Policy and related security headers. Markdown images from other sites are not shown.
• Enter no longer sends a chat message or note while you are composing text with an input method (Japanese, Chinese, Korean).
• With "reduce motion" on, the office is a still picture and UI animations are off.

Maintenance

• Lint has zero warnings and CI fails on any new one; GitHub Actions runs lint, tests, build and the browser tests.
• ESLint 10; shadcn moved to development dependencies, so the production audit reports no issues.
• Engineering standards, stage gates, decisions and pitfalls added under docs/.

Release notes, 1.4.0 (2026-11-12)

Changes

• The web UI now uses shadcn/ui and Tailwind. The theme is preset b1a09SuFE: stone surfaces, amber primary, blue charts, Roboto. Dark mode is the default. A theme control in the sidebar (and on the sign-in screen) switches to the light stone theme. The isometric office is unchanged.
• Long forms (agent, project, team, and the other app dialogs) are about 100px wider. Confirmations stay compact.
• The Checks box on a task no longer clips the command and its result.
• Documents replaces Guides. Pages are stored in the local database.
• Documents is a wiki. General holds Coding guidelines, Choosing AI models, and Development cycle. Each project has Overview, Architecture, Decisions, Road map, Release notes, Setup, and a page per task. A task page stays in step with the task’s spec, summary, and review. Pages can link to each other. The planner and a developer read that project’s pages and can update them. General pages stay free of project names. Upload is not in this version.
• Opening another page in Documents no longer jumps the list back to the top. A refresh of the page you are reading keeps your place.
• Vite is 8.3.8 and @vitejs/plugin-react is 6.3.0. React stays on 19.3.1.

Release notes, 1.3.2 (2026-11-11)

Changes

• Planner picker in the chat. The chat header has a Planner selector next to Team, and your choice applies to the next message. A project can also have its own planner in the Projects form. The order is chat, then project, then the team’s planner. Before, changing the planner in a team or in Settings could leave a chat on the old one.
• Release notes now collect under Unreleased until a release is made, so the version number no longer goes up with every small fix.

AgentDesk 1.3.1

• A check that was cut off because you pressed Stop is now shown as stopped instead of "failed (exit 1)". It is not counted as a failure, and nothing is sent back to the developer.

Next versions will be more grouped, so its more clear what was done in each version.

AgentDesk 1.3.0

Tasks

• Export: an Export button on every task downloads it as one Markdown file: the task, its problem, summary, review and spec, and every round with each tool call and its result. For bug reports and for handing a task to a reviewer. It can contain output from your project: read it before you share it.

Fixes

• A task that is stopped and restarted after its work was already committed no longer fails with "The worker made no changes". Finding nothing left to do is fine when the work is on the branch, and the summary of what was done is kept.

AgentDesk 1.2.3

• A restarted task no longer starts beside a task that is already working on the same files: it waits for it. Before, only tasks higher in the backlog were waited for, so stopping one task and restarting it while the other had started could run both at once.

AgentDesk 1.2.1

• A queued task that waits for another one (same files) now says so in the task view: "Waiting for () to finish", and warns when that task has stopped and needs a retry.

AgentDesk 1.2.0

Scrum

• Tasks that change the same files now run one after the other. Before, two items of a sprint that both touched the README started at the same time: the second could not see the first one's work and either did nothing or conflicted. Now the later task waits (and says so in the sprint chat), then starts from the sprint branch with the earlier work in it. Tasks on different files still run in parallel.

AgentDesk 1.1.2

Fixes

• Task summary: the summary of a task (shown on the task, in the merge commit and in the release notes) now keeps what the earlier rounds did. Before, a last round that changed no files replaced it with "no file changed in this round".
• Scrum: a task that is retried after its sprint closed now marks its backlog item done and rewrites the sprint's release notes, instead of leaving "Nothing was merged" and the item back in the backlog.
• A task of a sprint that is already released can no longer be retried, because its branch is gone. Plan the item again from the backlog.

Includes everything from 1.1.0 (Checks section, loop guard, verify and setup suggestions, env file for checks, Version page).

AgentDesk 1.1

Checks

• New Checks section in the task view, by Merge and as a chip at the top of the task: every verify command with its result. Open a failed one to see its output.
• A check that cannot run (missing npm script, no package.json, command not found) says so, instead of looking like a code failure.
• The Checks section shows "waiting" until the build is done.

Safer, less wasteful agents

• Loop guard: an agent that keeps repeating a failing edit or the same failing call is warned and then stopped, even when it reads files in between.
• A check that fails because of the project setup (missing environment variable, missing script, command not found) stops the task at once with the reason, instead of starting new fix rounds.

Project setup

• Verify suggestions: buttons for commands that fit the folder (npm scripts that exist, pytest, go, cargo, dotnet, git diff --check), plus warnings for commands that cannot work there.
• Setup suggestions: install buttons (npm ci, pnpm, yarn, pip) and a warning when nothing installs the packages.
• Env file for checks: copy a file such as .env.demo into the worktree as .env (setting Copy as) only while the verify commands run, then remove it. Agents never see it.

Other

• This Version page and the version in the sidebar.