What shipped, release by release.

v1.18.3 — TUI live-board and release rehearsal fixes

• Release rehearsal commits the workspace files tracker init creates before it dispatches, so the smoke no longer stops with dirty_repo. When VERSION is unset, it uses the latest vMAJOR.MINOR.PATCH git tag.
• The TUI watch loop follows SQLite data_version. A commit that lands before the next tick is still loaded when a WAL spill moves the file stamp first, and a failed generation read still reloads on the next tick.
• Docs, site and plugin pins moved to v1.18.3.

Download v1.18.3 and read its verification results. The installer selects this stable release.

v1.18.2 — Quarantine, checksum and installer fixes

• Repair copies under .tracker/quarantine/ are git-ignored. On an existing workspace, run tracker doctor --repair once to refresh the ignore rules.
• Release checksums.txt lists bare asset names, so sha256sum -c checksums.txt works in the download folder. The installer and tracker update still accept the older dist/ lines.
• The installer accepts VERSION=1.18.2 or VERSION=v1.18.2 and names a missing release with its URL.
• Docs: building from source needs Go 1.26.10 or newer, and the tracker version --json samples match a real release binary.

Download v1.18.2 and read its verification results.

v1.18.1 — Install, update and MCP approval fixes

• The installer and tracker update need GitHub CLI (gh) 2.102.0 or newer and stop before downloading with an upgrade message. The no-script install block starts with a real gh check and stops cleanly when gh is missing or too old.
• When /usr/local/bin isn't writable and BIN_DIR isn't set, the installer uses ~/.local/bin instead of failing.
• tracker update verifies the release attestation with the installer's exact policy and the local bundle, so updates work without a GitHub token.
• MCP: approvals for machine-scoped tools are stored where the global MCP server looks for them, and tracker mcp approvals revoke --json reports scope and found.
• tracker backup remote restore-apply accepts the plan ID that remote restore-plan printed, and restores no longer get stuck on an event id the restored log already uses or reuse ids of discarded events. tracker doctor --repair clears a workspace already stuck this way.
• A truncated or unparseable ticket file is named by doctor and reindex (exit 7), and tracker doctor --repair backs it up and restores it from the event log.
• tracker web open signs the browser in instead of getting HTTP 401, and Ctrl-C stops tracker web serve and Atlas Home, including during startup.
• tracker init no longer shows another Atlas instance's Home port (such as 127.0.0.1:7432) as this workspace's Home; it names the owner and points to service.port.
• Upgrading from v1.18.0 or older: the old updater can't verify without a token, so reinstall with the installer or the no-script steps.

Download v1.18.1 and read its verification results.

v1.18.0 — Grok plugin and install without curl | sh

• Grok plugin: .grok-plugin/plugin.json and a root .mcp.json let Atlas Tasker be listed in the Grok plugin marketplace as a local plugin. It launches the installed tracker mcp serve over stdio.
• Install without curl | sh via a checksum- and attestation-verified release binary or a pinned go install.
• The README lists every network endpoint Atlas Tasker can call and every credential or environment variable it reads. Reviewer steps and an MCP stdio smoke test support marketplace review.
• No changes to tracker behavior, the CLI or the MCP tools.

Download v1.18.0 and read its verification results.

v1.17.1 — Home and live-board stability

• Home sessions recover across restarts, and schedule and project forms retain typed drafts when validation fails.
• Live boards recover after index replacement, retain saved-view filters and active drags, and refresh ticket details and activity.
• MCP pagination and structured search remain bounded and predictable. First-ticket validation leaves invalid empty directories untouched.

Download v1.17.1 and read its verification results.

v1.17.0 — Chat-native boards and security hardening

• Download v1.17.0 and read its verification results.
• Inline HTML boards for Meta Muse and other compatible chats show status lanes, priority, blockers, and expandable ticket details. The MCP board widget opens with side-scroll lanes and can switch to wrapping columns.
• Markdown boards work in text-based chats such as Grok Bot. Discord and Grokbot can opt into a colored ansi code block; the default Markdown remains plain. Chat hosts control their own message fonts.
• Security hardening confines MCP paths, validates sync and bundle inputs, rejects protected bundle paths and symlink escapes, and keeps scheduled wakeups alive after request cancellation.

Meta Muse has not yet been tested live with the Atlas HTML renderer. Agents use the installed guide to select a format the chat host actually displays.

v1.16.0 — First-use and browser management

• Download v1.16.0 and read its verification results.
• Install needs curl, tar, and gh. Local attestation-bundle verify does not need a GitHub login.
• Ordinary path: install → tracker init → restart the client → ask for status. Init configures detected agents without a picker. The picker is tracker init --integrations.
• Native skill roots: Grok .grok/skills (project trust first), Codex .agents/skills (legacy .codex/skills still lists on 0.144.5), Cursor detects cursor-agent, OpenClaw shares .agents/skills.
• Home can create or attach a board and Kanban covers everyday tickets including Delete ticket, which retains files and history. Home init does not write client MCP files. A written config is not a live connection.
• tracker update still replaces only the binary. Re-run tracker init in each workspace to refresh managed skills.

See the v1.16 upgrade guide for refreshing existing workspaces.

v1.15.0 — Atlas Home and agent setup

• tracker init then tracker is ordinary onboarding: workspace, default project, local checkpoints, Atlas-managed MCP for detected agents, and Atlas Home on 127.0.0.1:7432. The one-line installer is the normal path. Unstamped source builds report version: "dev".
• Terminal and TUI boards default to polished tables, with optional Kanban cards. Browser and MCP App boards keep their Kanban presentation; chat uses native Markdown.
• Global tracker mcp serve --global --tool-profile workflow lists workspaces; cross-workspace writes need workspace_id. Restart the client after init. Pinned --workspace remains.
• Local checkpoints start at init. A named remote is never inferred from Git origin. A push is not verified until Atlas fetches the snapshot. Restore is plan-then-apply.
• tracker uninstall and /uninstall remove Atlas software only. Boards, history, backups, and registry pointers stay. Verified source and Go installs can record a receipt during init or setup.
• Grok Build loads compatible underscore tool names. Init finds agent CLIs on PATH, and Home shows the scope and actual command for each registration. MCP defaults to the workflow profile; explicit read-only operation remains available.
• Assigned backlog appears in personal queues without being promoted. Opt-in MCP bootstrap creates a first project and registers with Home. Long project names and nested command help are handled.
• README and website use current dark screenshots, including a real Grok Build status-and-ticket session recorded on a v1.15 source build. The favicon is the A from the Atlas wordmark.

See verification results on the v1.15.0 release page.

v1.14.0 — implementation candidate

• tracker setup is one pass for skills, MCP, managed mode, and an optional already-added backup target. --yes is not backup consent, and setup never installs a user scheduler or selects Git origin.
• Six coding-agent adapters stay transactional. Custom instruction text and unmanaged atlas-* MCP entries are left alone. tracker update still replaces only the binary.
• Automatic Atlas checkpoints write an isolated Git repository. Off-device publication is fast-forward only; a push is not verified until Atlas fetches the remote commit into an empty temporary repo. Verification is per target and is not claimed while the replica is blocked. Ticket writes stay available when backup is offline.

This is source on the development branch, not a published GitHub release. The latest tagged installer remains the latest stable release. Hosted verification is recorded only on a release page.

v1.13.0 — Workflow Consistency

• Workflow consistency fixes keep Canceled separate from Done across every board, show assignees on cards and terminal views, reject claims that would take another assignee's work, require new schedules to be strictly in the future, and apply one actor-resolution order across CLI mutations.
• Review team presets now install their actual required reviewer, make new projects inherit workspace policy, migrate project open overrides to inheritance, and enforce the request-review → required-reviewer approval lifecycle. Approval completes review_gate work.
• The workflow MCP profile adds explicit workspace bootstrap and project creation plus ticket heartbeat, priority, label, and ordinary-field editing. Strict schemas, the read-only default profile, separate client registration, and externally issued high-impact approvals remain in place.
• Generated agent guidance now uses real configured identities, portable workspace-relative references, distinct integration skill directories, explicit OpenClaw --global wording, same-status no-op guidance, and reasons on mutation examples.

The v1.13.0 release page lists platform downloads, checksums, provenance, and hosted verification. Run tracker update --check to check your installed version.

v1.12.0 — Agent Setup And Documentation

• Optional first-install agent setup, safe cancellation, and unattended installation.
• All six web languages accepted as saved preferences.
• Updated MCP and self-update docs, a complete Connect Your Agent walkthrough, neutral screenshots, and the current UI wordmark.

The v1.12.0 release page preserves its builds and verification. For the current version, use the latest stable release.

v1.11.0 - MCP Loop, Self-Update, And Local Hardening (2026-09-09)

• MCP workflow profile covers the real agent loop (create/assign/link, approve/reject/complete, agents/teams, goal brief, wake-ups), and stdio accepts both newline JSON-RPC and LSP-style framing.
• `tracker update` self-updates from GitHub releases with checksum and attestation verification and atomic binary replace.
• `tracker integrations detect` and interactive install checkboxes (plus init flags) for Claude Code, Codex, Cursor, OpenClaw, and Grok.
• Local security hardening: archive/compact path containment, symlink fail-closed checks, private modes for sensitive paths and config, OpenClaw `--global` destination validation, and soft secret-like warnings on create/comment.
• CLI honesty: same-status move is a no-op, nested init refusal, `ticket show` alias, required `--type` unless a template supplies it, and consistent actor resolution on create/move.

v1.10.0 - Local Web UI And Agent-Ready CLI (2026-09-08)

• Atlas grows a local browser UI: `tracker web serve` starts a loopback-only server with a welcome dashboard, the Kanban board, a schedule workspace, and a read-only settings page — server-rendered through the same services and event log as the CLI. The board wears the atlas.pen restyle: deep-navy surfaces, Geist and Geist Mono, column accent bars, and tinted status and priority pills.
• The board and welcome chrome speak six languages (English, Spanish, Indonesian, Chinese, Japanese, Korean); ticket content is never translated.
• One-time ticket schedules: `tracker schedule set` reminds a human through your notification sinks or wakes (and in command mode, launches) an assigned agent; `schedule tick` is a one-shot trigger built for cron or launchd, and matching MCP tools cover list/history/set/clear.
• Agent-ready CLI: `--json` on every command agents run with a build gate to keep it that way, `tracker init --json` bootstrap reporting, `mcp serve --workspace` pinning, and an OpenClaw skill installer.
• Security: the web board is strictly loopback-only (the `--unsafe-host` escape hatch is gone — breaking), exports and backups fail closed on symlinked inputs, the CI and release workflows pin every action to a reviewed commit, and the toolchain moved to Go 1.26.6.
• Breaking: `tracker board --json` now returns `columns` (lowercase), and forbidden workflow transitions exit 4 in the CLI (previously 1) and 409 on the web.
• CLI first-run polish: running tracker outside an initialized workspace is a clear exit-2 error instead of silently scaffolding a stray `.tracker` (from a subdirectory the error names the workspace root), `invalid status` errors enumerate the legal values, and `tracker --help` walks `init` → `project create` → `ticket create` → `board`.
• Wake-ups point at work you can see: when the last blocker of an agent-assigned ticket completes, Atlas promotes the dependent from `backlog` to `ready` (audited as `agent:atlas`) before waking the agent, and `queue`/`next` gain an `unblocked_for_me` category for backlog tickets whose blockers are all done but that nobody moved, while `agent available` reports a `promote` action for the unassigned (claimable) ones, or for the agent's own ticket when the automatic move failed. A write that dies after its canonical file no longer has its mutation journal overwritten by the next write; that write is refused with `repair_needed` until `tracker doctor --repair` replays it.

v1.9.1 - Agent Loop README And Table Polish (2026-06-16)

• README now shows how to hand tickets to Claude Code, Codex, or OpenClaw-style agents through an Atlas-tracked agentic loop.
• List output across the CLI and TUI moved to real terminal tables: rounded muted borders (ASCII under `NO_COLOR`), bold accent headers, and content-hugged columns that only clamp when the terminal is narrower than the data. Cells keep their semantic badge colors, the board groups each workflow column once and omits empty ones, and the TUI highlights the selected row.
• No storage, schema, or command behavior changes.

v1.9.0 - First Stable Release (2026-06-10)

Everything from both release candidates, finalized. The hosted proof for `v1.9.0-rc2` (checksum + attestation verification, clean-directory install from published assets, version metadata match, packaged smoke) is recorded in `docs/release/v1.9.0-release-evidence.md` along with the owner ship decision.

• The TUI opens with a branded splash (chrome-blue ATLAS TASKER art, any key skips, degrades cleanly on narrow and NO_COLOR terminals).
• All terminal colors now come from one brand palette (`internal/theme`): electric-blue primary, adaptive light/dark pairs, semantic status hues, and a real priority scale (critical/high/low) instead of uniform gray badges.
• Brand assets are committed under `assets/brand/` and the README wordmark is served from the repo.
• New `tracker gh` command family wraps the GitHub CLI: `status`, `prs`, `view`, `checks`, `create-pr`, `request-review`, and `import-url`. `create-pr` opens the pull request and links it as a ticket change in one audited mutation; everything degrades to a clear "install GitHub CLI" repair message when `gh` is missing.
• CLI color output now reaches the terminal intact: the display sanitizer preserves the SGR styling Atlas emits itself while still stripping every other escape sequence, so `tracker board` no longer prints `[90m` residue in color-capable terminals. Truncation drops styling cleanly instead of slicing escapes in half.
• README rewritten around the published release candidate: one-line verified install, terminal screenshots, demo GIF, and the agent workflow story.

v1.9.0-rc1 - First Public Release Candidate (2026-06-10)

• Published GitHub prerelease with archives for darwin/linux on amd64/arm64, `checksums.txt`, a CycloneDX SBOM, build attestations, and the installer script.
• Hosted release proof is green: checksum + attestation verification, clean-directory install from published assets, version metadata match, and packaged smoke.
• Go toolchain moved to 1.26.4 to clear stdlib govulncheck findings (GO-2026-5037, GO-2026-5039).
• Agent wake-ups now fire for `backlog` and `blocked` tickets when their last dependency completes; failed wake-up recording leaves a visible `failed` record instead of disappearing.
• A corrupted projection index now exits `repair_needed` with `tracker doctor --repair` guidance instead of leaking the raw sqlite error, and read-only `doctor` diagnoses it.
• Local planning docs and variant scratch trees are gitignored so they cannot ride along in a public push.

v1.8.0-rc1 - Local RC Proof Complete

• Rewrote the public README and OSS metadata for first-time GitHub readers.
• Added public docs for installation, quickstart, tutorials, concepts, command references, troubleshooting, doctor/repair, release verification, and agent workflows.
• Polished terminal, Markdown, and TUI output with width-aware layouts, render tokens, `NO_COLOR`, plain output, ASCII fallback, and better empty states.
• Added Codex, Codex `/goal`, Claude Code, generic agent, and MCP workflow guides.
• Added demo workspace scripts, prompt packs, terminal transcripts, and screenshot-friendly examples.
• Added release preflight, `tracker version`, packaged rehearsal, SBOM/vulnerability proof hooks, and offline RC validation.