v1.3.5 (October 2026)

• Schedule a Dev task: A developer makes a deliverable on a timer, reviewers check it, and you integrate it from the Autopilot tab. A schedule waits while its last run is unhandled, and pauses itself after three failed runs. Like an Ops task, a scheduled Dev task can run the commands you allow, such as a render script.
• Integrate can bring a run's generated files along: Files that git ignores, such as rendered images, land in your checkout without being staged.
• Each scheduled Ops run keeps its report and its files in one folder: The folder is named with the run's date and task ID.
• The Scheduled tab can be sorted and filtered: Sort by next run, last run, created, name, repo or last result, and filter by kind, state, last result and repo. Your choice is remembered.
• Monitor has a "Show shells" switch: Shells stay out of the way until you turn it on, and the choice is remembered. When no agent runs anywhere, Monitor shows your sessions and shells instead of an empty page.
• Settings warns you before you leave with unsaved changes: It also reminds you to press Save after any edit.
• A Herdr that is too old for ACTower is now said out loud: Settings → Integrations turns red with the version you need and the command to run, and Monitor shows a notice until Herdr is updated.
• Start workspace offers "Open in terminal" beside "View in Monitor": It is the same door as Monitor's >_; the tmux attach command stays as an optional hint, not a step.
• The planner no longer waits for you on read-only commands: When the overseer can judge a read-only command, planning carries on without stopping for you.
• Reviewers now see the task text: The checks you write for them in a task file reach them.
• "Match Monitor sessions" in the Responder is on by default: New installs start with it turned on.
• On the Free plan the five monitored panes are the most active agents: They are picked across tmux and Herdr, instead of the first five tmux panes; on a tie, two tmux and three Herdr.
• The new version shows right away after a Homebrew upgrade: actower doctor and Settings → Installation report the version you just installed.
• An autopilot review session's card reads "on dev": It used to read "dev from dev".
• Smaller fixes: Rebuild's button says "Apply 1 change" for a single change, and the Start workspace plan says "launched" once the launch ran.

v1.3.4 (October 2026)

• Scheduled Ops runs can run the commands you list: Name a script with its fixed arguments in the Launch form's Allowed commands field, or with --allow-command, and a scheduled or one-off Ops run may run it, as long as the script is committed and unchanged; everything else stays read-only. Turn on cloud reads (--allow-cloud-read) to let AWS describe, list and get commands through. Each run's report lists the allowed commands that ran. A listed command may also run a script from another repository you name, by starting with cd /full/path/to/that/repo &&, and the report names that repository next to the command.
• A new autopilot task shows up the moment it starts: It appears in the Autopilot tab as "Starting…" while its agents start, with Open in terminal as soon as its session exists, and becomes the normal card when it is ready; a task that fails to start says "Start failed" with the reason. Its terminal window opens right away, and its agents start working sooner.
• One Plus plan: Plus and Pro are one plan now, and the app calls the plan that unlocks Custom Safe Rules Plus, matching the website.
• A scheduled Ops run saves a long report even in fullscreen mode: When Claude Code runs in fullscreen mode, a report taller than the window used to be refused, and the run then waited out its time limit; it is now saved to the schedule's folder.
• Run now always starts a run: Pressing Run now on a schedule starts the run every time, instead of sometimes recording it as skipped.
• `actower autopilot stop` stops a scheduled run: It used to say a scheduled run could not be reached; it now stops it cleanly, and the run is marked as needing a look.
• A scheduled run that keeps being refused says so, and a run that expects refusals finishes: A run stops after it asks three times for the same command it may not run, or after 20 refusals in total, and the Autopilot tab says which of the two stopped it instead of showing a timeout; a task with several expected refusals runs to the end.
• Smaller autopilot fixes: More reliable prompt handling in autopilot sessions.

v1.3.3 (October 2026)

• ACTower works with Herdr: Agents running in Herdr workspaces show up in Monitor beside your tmux sessions, and their questions reach the Responder, so you answer tmux and Herdr agents from one queue, with auto approvals for safe questions. The Layout view draws the Herdr windows. Go to pane brings the Herdr window forward on the right pane, Enlarge shows its pane cards, and Snapshot asks the agent for a handoff just as it does in tmux. Shells are listed too, under the Shell chip, and Herdr panes are named the way tmux panes are: workspace, tab and pane. Herdr workspaces are watched as soon as Herdr is on; untick one in Settings to leave it out. Works with Herdr 0.9.3 or newer. Agents you start from ACTower still open in tmux; starting them in Herdr comes next.
• Autopilot waits for its agents: A phase now ends only when its agent has really finished. An agent that showed its own task text no longer ends its phase early, and the session report has a Done signals line saying how each phase's end was decided. An agent waiting on its own background work, or on a long test run, is no longer ended as stuck: autopilot waits for that work, and an agent that sits idle without saying it is done gets one reminder to finish or to say it is still working. A resumed session whose plan never finished goes back to planning instead of starting development without a plan.
• Answer faster in the Responder: The answer buttons now sit right under the question, with the pane's recent output in a scrollable box below them, so a long preview never pushes Yes and No off the screen.
• A reminder before a waiting question ends the session: When a question has been waiting for your answer and the session's limit is 15 minutes away, you get one more notification, so a session you forgot about doesn't time out unseen.
• Autopilot windows open at a readable size: The terminal window ACTower opens for a new autopilot session, and every window inside it, now come up at the same laptop-sized terminal that Go to pane uses, instead of a small default window you had to enlarge.
• An autopilot session shows the branch it started from: The session card and its detail name the source branch beside the session's own, the button that stages the result says where it goes ("Stage into dev"), the message afterwards says where it went, and actower autopilot status <id> prints the source branch too.

v1.3.2 (October 2026)

• Your workspace: see who works where, and start an agent from the repo card: Every tmux pane is now tied to the repo whose folder it works in, whatever AI CLI runs in it, a plain shell or an autopilot worktree included. A repo card says who is there and how many questions wait on you, and lists those panes, each one a click away in Monitor. Start an agent here opens a terminal window in the repo's folder with the CLI you pick, and a second click goes to the agent already working there. The proposal review screen gets Review with your agent, and an autopilot session gets Open worktree. Windows and editors ACTower opens for you now start with your own login environment. From the command line: actower ecosystem repo open <repo>.
• Monitor has three views: Session view as before; Repo view, which groups panes by ecosystem, then repo, from any session, with "Not in an ecosystem" after them and a pane in no repo under its own folder; and Layout view, which draws every window the way tmux lays it out, with each pane's agent, its state and the questions waiting. Enlarge a window to see each of its panes as a full card. Filters hide windows with nothing that matches and dim the panes that don't, so a window keeps its shape. The toolbar is tidier: Status and Agent on the left, the view switcher on the right, and each view remembers its own choices. When you have an ecosystem, Monitor opens on Repo view the first time.
• Your tmux, tidy and themed: ACTower's look goes into its own block in ~/.tmux.conf, between markers. Your own lines never change, and settings you already have are kept and named. You get a right-click pane menu, pane borders labelled with repo, agent and state, a status bar with the questions waiting, and three keys after your own prefix: zoom, the next pane waiting on you, and the key list. Pick a theme in Settings with a live preview, or run actower tmux theme. actower tmux theme --off gives the file back byte for byte.
• Add repo takes a repo you already have, or one from GitHub: Besides creating a new repo, Add repo now takes a folder already on this computer, with its history, or a repo from GitHub, and the next invite shares it. Put it on GitHub first shows a dry run of what will happen, then creates the repo and sends your work only into an empty one. A copy that pushes to another repo is never copied silently: ACTower says what it found and lets you choose. From the command line: actower ecosystem repo add and actower ecosystem repo github, both with --dry-run.
• Autopilot sessions finish what they start: A session keeps running when the shell that started it closes, and actower autopilot stop stops one cleanly from any terminal. A session stopped at the review limit by a finding only you can decide can now be finished from its card by the ecosystem's owner: tick the findings you accept, give your reason, and choose Accept as exception and commit. The session ends complete with an Exception badge, and the reason stays on the card and in the report. Open worktree now offers VS Code and Cursor beside Terminal.
• The autopilot session list opens instantly: Even with hundreds of sessions, the list opens in milliseconds. It shows one "ended" number that stays put, and each card shows the session's pipeline phase. A new session appears at the top on the next refresh, and one that just ended changes state instead of disappearing. Autopilot agents also do their own work now, without handing parts to helper agents, so a session never looks finished while a helper is still running, and you are not asked to approve a helper's commands one by one.
• Your repo keeps its branch name on GitHub: If your copy works on master, Put on GitHub and the first invite publish it as master and make that the team's branch, so Share, Send for review and Start a change work from the first day. Before, such a repo went to GitHub as main while your copy stayed on master, and its card showed every button greyed out with no reason. Whenever every send button on a card is off, the card now says why.
• Other team fixes: Revoking a member removes every key of theirs on GitHub and reports any it can't remove. A push from a View only copy is refused in ACTower's words before anything reaches GitHub. A member whose profile has no specialists can still start a workspace. Smaller fixes: the proposal screen shows the proposal's id with Copy, Open diff opens a new editor window, the banner after your proposal is merged says it once, and /team-sync always offers "Keep both lines" when both sides changed the same line.
• Settings shows the desktop app's version next to the CLI's: The version chip shows both, and Installation in Settings has a Desktop app row. When the app is behind the CLI, Settings says so and gives you actower desktop to update it.
• Doctor, setup and the installer: actower doctor and actower setup find a Python 3.11 or tmux that is installed but not on your PATH, and say how to add it. The curl installer uses a temporary file of its own and always removes it, and asks you to reload your shell only when this terminal needs it. Refresh license on the Free plan says "No license key on this computer yet" instead of calling the file corrupted. The desktop app carries its own notarization ticket, so its first launch doesn't depend on reaching Apple.

v1.3.1 (October 2026)

• Join a team by pasting the invite as you received it: Paste the whole message you were sent, or the link, into Join: ACTower finds the invite in it by itself. The message the owner sends now says so, and says where the link goes if your chat app shows it as plain text.
• Proposals, where the work is and in your editor: A repo with a proposal waiting for your review says so on its card. On the review screen, Open diff in VS Code or Cursor opens the change in your editor's compare view, so a large proposal is readable, and your own copy stays on main. The same is available from the command line with actower ecosystem proposal diff. Review wording now speaks to you ("You asked for changes") and tells you when a newer version is waiting.
• Members see what happened to their work: After Get updates, the card says when your proposal was merged. If your access was removed, the card says so and names who to ask, instead of showing an old "Up to date". A push from the terminal to a repo you can only view is refused with a plain sentence.
• The installer sets up a fresh Mac by itself: Where it used to list missing tools and stop, the curl installer now shows exactly what it will install, asks once, and carries on. It never installs Homebrew, never installs anything without a yes, and finds a Python 3.11 or tmux that is on the machine but not on your PATH. The dependency step says what it is doing instead of going quiet. --yes for scripts.
• The desktop app tells you when it is behind: After a CLI upgrade, the first actower command says once that the desktop app is on an older version and how to update it. actower doctor shows the app's version next to the CLI's. Settings no longer promises an install record on a machine with two installs; it says which copy is used and how to pick one.
• Clearer team wording: Revoking someone with an open proposal says the proposal stays for you to merge or decline. The invite screen says "Invite created on this computer" instead of "Signed as". Profile help says the repo's reviewers approve proposed changes. A repo that is not on GitHub yet explains that instead of offering a button that fails. /team-sync offers only the sending option your access allows.
• Scheduled Ops runs file their reports reliably: A tall or parallel report write no longer loses the run's report path, and any file in the run's report folder is the run's to write. Autopilot sessions and attach windows open at laptop size.

v1.3.0 (October 2026)

• Invite your team into your ecosystem: Open an ecosystem and choose Invite. Pick a profile, and ACTower creates the GitHub repos if needed and gives that person their own access key for each repo they should see. You get a short message to send them: the install line and a join command, or an actower://join link if they already have ACTower. They join in the app, confirm an eight-word phrase you tell them by voice, and their copies and hub are set up for them. Members shows who is in and who has joined, and lets you re-invite or revoke anyone.
• Profiles decide who can do what, per repo: A profile lists repos and, for each one, View only, Propose changes or Can edit. Several people can share a profile (for example Sales), and one person can have a profile of their own. When you change a profile, the people on it are shown as needing a re-invite, and their access does not change behind their back.
• Proposals and reviews, without leaving the app: People with Propose changes send their work for review instead of pushing it. Start a change puts them on their own branch, Send for review saves it and sends it, and once the required approvals are in the change can be merged and the author's copy returns to main on its own. Each repo can have its own reviewers, a number of approvals needed, and repo admins who manage that repo's reviews. A new version of a proposal resets earlier approvals, and every review is signed so it traces back to the person who gave it. The Proposals tab shows what is waiting for you.
• Get updates, Share and Sync all on every repo card: Each ecosystem has a Repos tab with every role and code repo: which branch it is on, what changed and when it was last checked. Get updates brings in what others shared and never merges over your work: if a file changed on both sides, you keep yours and the team's version is saved next to it. Share my changes shows exactly what will be sent before anything leaves your machine, flags files that look like secrets, and sends only the files you staged or tick in the confirm. Sync all gets updates everywhere and refreshes your hub, and never sends anything.
• Help from your AI agent when files need a look: When a file changed on both sides, the card explains what happened and suggests running /team-sync in your AI agent, which combines the two versions and asks you only where they genuinely disagree. /team-sync now comes with every ecosystem hub. Copy instructions gives the same steps as text for any AI tool.
• Scheduled Ops tasks: Autopilot can now run a task on a schedule, on macOS and Linux. Set it up once in the app, and it runs on its own cadence, on an ecosystem hub too, with each run's report filed in the agent's folder and listed under Sessions. The /autopilot-manager skill helps any agent form one from a plain description.
• Autopilot keeps going when it needs you: A question left waiting for you, or a busy pane, no longer ends the session: it waits, keeps the other agents working, and stops only after a time limit you can set, with a separate deadline for the validation step so a working developer is never cut off. When ACTower refuses a command, the agent is told why and carries on another way. Reviewers finish their checks before giving a verdict, and each verdict is recorded reliably. Sessions that ended with good work can be integrated from the Web UI, a review that ran out of rounds can be given one more, and a resumed task shows its real status and who resumed it.
• Autopilot starts on your sessions: The Autopilot tab opens on Sessions; starting something new is under New task, with ready-made templates.
• Safer auto-approvals, fewer needless prompts: Commands that write to a file, run another program or expose your environment always wait for you, and more of the everyday commands your agents run are recognised as safe on the first try. Fewer safe actions wait for you; nothing risky slips through.
• Monitor shows how long a question has waited: A waiting pane turns yellow, then orange after thirty seconds, then red after five minutes, and waiting panes sort to the top. The thresholds are in Settings.
• Tidier Monitor and Responder toolbars: Filters fit on one row, and the agent filter only appears when you use more than one AI CLI.
• Clearer Rebuild preview: Rebuild shows what will actually change, section by section ("1 change", "no changes"), and matches what Apply does. The ecosystem window can be maximised.
• Your GitHub connection, handled carefully: You connect GitHub once in Settings; the token is used only for setup work and is never sent to members. Each copy of a repo, yours included, uses its own access key, and ACTower checks GitHub's published identity when it connects, so a first connection from a new machine needs no manual trust step.
• A second install stays out of your way: Installing ACTower into a custom location no longer edits your shell configuration or restarts your main ACTower; --no-path skips the shell edit for any install.
• Bundled skills: The general-purpose pr-review and validate-review skills are no longer bundled; Autopilot's built-in review runs that method for you, and copies you edited are left in place. autopilot-manager, team-sync and commit-message remain, and every install, Homebrew included, now keeps them current after an upgrade.
• General fixes and reliability improvements.

v1.2.16 (September 2026)

• A Homebrew-only install can now open the desktop app: Homebrew cannot create ACTower's Python environment when it installs the CLI (its install step runs in a sandbox that cannot write to your home directory), and actower setup never created it either — so on a machine where ACTower came from brew install alone, actower desktop ended in a "CLI Not Found" dialog about a CLI you had just installed. Now actower web, actower desktop and actower setup create the environment themselves the first time they need it, showing progress while the packages download so a long first launch never looks like a hang. The only thing that still needs you is Python 3.11 itself; if it is missing you get one clear message with the install command. Curl installs are unchanged.
• The desktop app always runs the copy of ACTower you upgraded: The app used to start from the curl install's location unconditionally, so on a Homebrew-only machine it failed to start, and on a machine with both installs it silently ran the curl copy — which is why brew upgrade actower never reached the app and Settings kept showing the older version. The app now finds every install on the machine, runs the newest one, and never picks an older copy over a newer one. If it cannot find a usable install at all, it tells you so and names the install commands.
• Autopilot files its hub documents without interrupting you — for real this time: The v1.2.15 rule that lets a hub-bound session write its reports into your hub's docs/ never fired on a real hub, because those folders are links into your role repositories and the agent reports the write by where the file actually lives. ACTower now recognises a document by its real location as well as by its hub path. Nothing new is granted — the same files, the same guards on agent, skill and command definitions, CLAUDE.md, non-document files, deletes and moves. A hub write the rule does not cover now waits for you on the Queue page with the reason, instead of being refused outright.
• General fixes and reliability improvements.

v1.2.15 (September 2026)

• Homebrew installs are recognised correctly: If you installed with Homebrew and nothing else, Settings reported Installed via: Unknown and the updates bell offered you every upgrade command rather than the brew one. Homebrew runs its post-install step in a sandbox that cannot write to your home directory, so the record ACTower keeps was never actually written. ACTower now writes it itself the first time you run any command — in your own shell, where there is no sandbox — after which each run costs a single file check. It never overwrites a record that already exists, and it declines to guess: a copy it cannot attribute to an install method records nothing rather than something wrong.
• Autopilot can file its own session reports into your ecosystem hub: When — and only when — an Autopilot session is bound to a hub, it now auto-approves reads anywhere in that hub and document writes under docs/ (.md, .txt, .yaml, .yml, .json). Previously every session report and findings draft an agent tried to file there was rejected as out of scope, so either you clicked approve or the agent gave up and you filed it by hand. Agent, skill and command definitions, CLAUDE.md, non-document files, deletes and moves all still come to you. Sessions with no hub are completely unaffected. Every auto-approval is still recorded in the audit log.
• General fixes and reliability improvements.

v1.2.14 (September 2026)

• Bare `actower` transparently routes to your newest install: If you have both a curl install and a Homebrew install, running actower from your shell now automatically hands off to whichever one is newer — no more PATH-shadowing surprises where a stale copy answers instead of the one you just upgraded. Both installs stay first-class; the software adapts.
• `actower doctor` shows install method, path, and version at a glance: A new Installation section reports how ACTower was installed (brew or curl), where it lives, and which version, so you can tell dual-install state apart from single-install without hunting.
• Every install prints "Previous → Now installed": The installer now names the previous highest version (from any install method) and the newly installed one, in method + path + version form — so you can see exactly what changed after a curl or brew upgrade.
• Desktop app is auto-checked after install: If the CLI was upgraded past your installed ACTower.app, the installer offers to update the desktop app in the same step — no separate actower desktop follow-up required.
• Settings page has a new Installation section: The desktop and web UIs now include an Installation panel showing the active install's method, location, and version, plus a compact info line when a second install is also detected. Purely informational — never a nudge to remove either one.
• Method-specific "How to update" in the updates bell: The bell now renders the right upgrade command for your install method (brew update && brew upgrade actower for brew, curl installer for curl) instead of both grouped as pick-one.
• General fixes and reliability improvements.

v1.2.13 (September 2026)

• License refresh reaches the server reliably: Even on Python installs without a bundled root CA store (common on Python.org macOS), Settings "Refresh license" now actually calls the server rather than silently falling back to your cached copy. v1.2.12 correctly surfaced the fallback state as "using cached license"; this release fixes the underlying call so the fallback is no longer needed on those installs.
• Autopilot sessions survive Homebrew Python upgrades: When brew upgrade rolls Python to a new major version, Autopilot used to silently break — the session would run blind. Now Autopilot uses an explicit interpreter version internally so Homebrew Python upgrades don't strand your sessions.
• Autopilot sessions complete more consistently: long-running sessions now self-heal from occasional internal state drift instead of stalling partway through.

v1.2.12 (September 2026)

• Homebrew Web UI works out of the box: actower web on a Homebrew install now launches cleanly — the browser-based UI is fully supported on both curl and Homebrew paths.
• Homebrew upgrades pick up new code immediately: brew upgrade actower now auto-restarts the background Web UI service — no more "upgraded, but Settings still shows the old version" until you manually restart. Matches what the curl installer has done since v1.2.10.
• License refresh shows honest status: Settings "Refresh license" now clearly indicates whether the license was just re-validated with the server or fell back to your cached copy because the server couldn't be reached. Previously the two outcomes looked identical, so a fallback silently rendered as if it were fresh.
• Desktop app upgrade shows the new version instantly: actower desktop --update now paints the new version on the very first frame — no more manual Cmd+R after upgrade to see the fresh UI.

v1.2.11 (September 2026)

• Auto-relaunch after desktop upgrade: actower desktop --update (or accepting the auto-offered upgrade when versions mismatch) now quits the running app and relaunches it after installing the new bundle — no more "upgraded, but the version and features look unchanged until I manually quit and reopen."
• Clearer install-command grouping in the bell: the "How to update" section in the updates bell now groups the CLI upgrade paths (brew or curl) under a "pick one" label, with actower desktop in its own "then relaunch the app" section — no more ambiguity about whether to run all three commands in sequence (which would trip the dual-install shadow warning we added in v1.2.10).
• Google Antigravity CLI (renamed from Gemini): the multi-CLI dispatcher now correctly labels Google's CLI as "Google Antigravity CLI (beta)" following their product rename. Cursor, Codex, and Claude Code labels are unchanged.

v1.2.10 (September 2026)

• In-app updates bell: a new bell icon in the top nav surfaces new releases, announcements, and incidents — no need to check the website to catch what changed.
• Install + login now refresh instantly: the desktop app picks up new code and license state the moment you upgrade the CLI or run actower login — no more "Settings still shows the old version" delay while the background service holds stale state.
• License refresh actually refreshes: the Settings page's "Refresh license" button and the periodic background poll now update the "Last validated" timestamp immediately, so a click feels responsive instead of doing nothing visible.
• Dual-install safety net: if you've installed ACTower via BOTH the curl installer and Homebrew, the installer will warn you before the wrong copy silently shadows the other. A new actower doctor subcommand shows every install location + version with one-line remediation snippets. Warn-only — you decide which to remove.

v1.2.9 (September 2026)

• Refreshed ecosystem tooling: bundled skills and vendored tooling were updated to their current versions, so new sessions pick up the latest toolset out of the box.
• Smoother repo discovery: auto-discovery surfaces git repos more reliably when scanning a workspace root, so fewer repos go missing from your Repos list.
• Safer approval routing: actions the overseer can't confidently classify are now routed to you for a decision instead of being hard-denied — you stay in control without spurious denials stalling a session.

v1.2.8 (September 2026)

• Reviewer identity everywhere: Session detail now shows each reviewer by name — the full roster appears in the sidebar the moment a session launches (before any verdict lands), and the Verdicts tab labels every row with the specialist that produced it. No more guessing which reviewer is holding up completion.
• Launcher works for any repo — ecosystem or not: reviewers used to quietly go missing if your code repos lived outside your ecosystem's workspace root. The new resolver tries exact-path, then repo-name, then offers a picker, and finally falls back to every specialist ACTower knows about (across all your hubs plus ~/.claude/agents/). Fresh install with no ecosystem set up? You can still pick reviewers.
• "Needs your input" signal: when a reviewer stalls on a human-approval prompt for more than 30 seconds, the session card gets a red pip and the session detail shows a banner deep-linking to the Responder. No more wondering why a session isn't finishing.
• Autopilot sound settings: new Autopilot sound alerts in Settings — set AP session panes to off, escalated_only (fires only when a question really needs you), or all (previous behavior). Non-AP panes unchanged. New global Mute sounds for auto-approved actions applies across every pane if you want it.
• Session Timeline gets filters + coloring: chips for Phase transitions / Reviewer verdicts / Overseer events / Errors, and amber-red left borders on OVERSEER DOWN / TIMEOUT / STUCK / DENIED rows so post-mortems don't need a wall-of-log scan.
• Sessions stay tracked until you clean them up: v1.2.7 was quietly pruning completed AP sessions from your monitored lists. That's gone — sessions now stay in Monitor until you kill their tmux panes and remove their worktrees via the ⋮ menu.
• Fixed the empty "specialist authoring guide" page: the launcher's fallback link now goes to a real docs page.

v1.2.7 (September 2026)

• Autopilot tab (Premium) — first user-visible surface: launch, monitor, and integrate autonomous coding sessions from a proper UI, right next to Rules.
• Your repos — every git repo ACTower knows about with live state chips (staged, untracked, branch, ahead/behind remote), plus one-click Start task and Review + revise staged changes shortcuts.
• Auto-discovery — point ACTower at a workspace root and every git repo inside it appears; no more adding repos one by one.
• Launch templates for the common cases: add a /health endpoint, review my staged changes, design a caching layer, check test suite health.
• Sessions — filter by integration state (Clean, Staged, Has running AP, Ready to integrate) with per-card Discard. Session detail has Report, Verdicts, and Timeline tabs with Integrate / Resume buttons.
• Local ↔ remote sync on repo cards: see when you're ahead or behind your remote and push, pull, or fetch in one click — without leaving the app.
• Integrated + Abandoned chips on Monitor session cards: completed AP sessions show whether their changes have been integrated into your repo, and sessions whose worktree is gone are marked Abandoned so you know at a glance that nothing's left to integrate.
• Bundled skills: pr-review, commit-message, validate-review, and autopilot-manager install alongside ACTower and become available to any Claude Code session out of the box.

v1.2.6 (September 2026)

• Trust & reliability: License validation, Custom Safe Rules, and monitor internals hardened across a batch of behind-the-scenes fixes — no visible behavior change, but the guardrails you already rely on are stronger.

v1.2.5 (August 2026)

• License changes propagate in seconds: switching plans on the site now flips your desktop app to the new tier the next time you focus it — instead of waiting for your local cache to expire. Adds a Refresh license button in Settings and a gentle background check, so a plan change never leaves your app showing the wrong tier for long.

v1.2.4 (August 2026)

• Autopilot resume smarts: when a session hits its review limit, the auto-resume path from the web UI now extends the cycle budget so you don't have to relaunch from scratch.
• Stability fixes across the monitor and web UI.

v1.2.3 (August 2026)

• Autopilot planning doesn't stall: fixes an edge case where plan-only sessions could get stuck at Validation instead of surfacing the plan for your approval.
• Stability fixes across the web backend and monitor.

v1.2.2 (August 2026)

• Custom Safe Rules — Suggestions column: suggestions now live in a dedicated left-column slot, so a new suggestion doesn't push the rest of the page down.
• File-path rules, precise: file rules carry canonical paths, directory scope, and action scope; rules created from your current pane pick up the right working directory automatically.
• Stability across the monitor and rule-suggestion path.

v1.2.1 (August 2026)

• Don't-ask-again mute + Muted view: "Don't ask again" suggestions now offer a Mute path — the Rules tab has a Muted section where you can review, restore, or delete anything you've hushed.
• Tier-aware safety floor: rule suggestions and default safety behavior adapt to your plan — Pro unlocks Custom Safe Rules; Free and Plus keep the strong default guardrails.
• Select-path suggestions: when a suggestion could apply at multiple scopes (this file / this directory / project-wide), the UI now lets you pick.

v1.2.0 (August 2026)

• Autopilot (Premium): give ACTower a task, walk away, come back to a reviewed, ready-to-merge set of changes. A developer agent works in an isolated git worktree while an overseer keeps it moving and a peer-reviewer reads the diff — findings loop back for revision until reviewers approve. Four modes cover the common cases: full development on a fresh task, cold-eyes review-revise on your own staged changes, plan-only to think through an approach before you commit to building it, and ops mode for read-only inspection tasks (perfect for scheduled runs). CLI-driven today; the desktop UI launcher is on the near-term roadmap.
• Custom Safe Rules (Pro): teach ACTower to auto-approve repeat commands you trust. After approving a benign command a few times, a suggestion appears in the UI — click Yes and a rule is created on the spot. Next time your agent runs the same command, no prompt. Supports command rules (e.g. npm test), file-path rules (e.g. auto-approve edits under docs/), and don't-ask-again mutes for repeat questions. Rules apply across sessions and are managed on the Rules tab.

v1.1.6 (July 2026)

• New Claude Code prompts fully supported: the latest picker prompts (options with a side panel showing a file tree or diff) parse correctly, and the Responder preview now shows the panel content your decision is actually about.
• Filters that stay put: session and agent filters behave the same on Monitor and Responder — always visible, selections stick while you triage, and autopilot sessions collapse into a single pill.
• Agent list, readable at scale: workspace agents sort alphabetically in aligned columns (agent, repo, knowledge home), with grouping and filtering by repo.

v1.1.5 (July 2026)

• Knowledge homes, managed by the app: agent knowledge folders — the convention where each agent keeps its discussions and reference/ in its own docs/ folder — are now first-class in the product. Rebuild reads the homes your agents already declare in their profiles, proposes the rest, and one confirm wires them in: each agent's Dashboard section lists exactly its folder, new folders are created with a reference/ scaffold, and agent profiles are kept in sync with what you confirm. Works out of the box on adopted workspaces with existing conventions.
• Smarter Add agent: the repo is a pick-list of your workspace's role repos, and the knowledge folder is auto-suggested from the agent's name — created new and guaranteed unique.
• Agents are visible: the workspace view lists each agent with its source repo, its knowledge home, and one-click open in Obsidian.
• Readable rebuild plans: collapsible sections with chips that name what matters (removes, backups, skips) — and honest counts: a healthy workspace reports near-zero changes instead of a wall of churn.
• Vault first-open: the Dashboard opens as a pinned tab with starter bookmarks on a fresh vault — seeded once, then the layout is yours; rebuilds never touch it again.
• Activity, sharper: filter the whole page by coding agent — now accurate for any session naming — and "View moment" opens the pane snapshot from both the detection and the decision, with titles that say which you're looking at.
• Captures self-label: every decision capture records which CLI produced it, in the file and the filename.

(v1.1.4 was a quiet hardening release — deeper Codex and Antigravity prompt coverage validated against real captures, and ecosystem workspace-layout improvements; its user-facing polish ships in v1.1.5.)

v1.1.3 (July 2026)

• Ecosystems: create and manage team AI workspaces — the wizard shows a dry-run preview before anything is written to disk. New workspaces are symlinked team hubs with per-role repos by default; basic single-folder hubs are also available. Existing workspaces can be adopted read-only.
• Start workspace: creates tmux sessions natively, with an optional agent launch that discloses, per window, what it will run. Wizard-created workspaces can pre-approve their own folder trust — disclosed up front in the plan.
• Source map: a live view of what a hub aggregates, broken down by repo and by folder, with broken links and local strays flagged. Read-only by construction.
• Obsidian: open a hub as a vault in one click; agent profiles open directly, and a vault watcher keeps Obsidian in sync with role-repo edits.
• Governed trust prompts: trust prompts are now human-only questions — never auto-approved.
• Match Monitor sessions: now a persisted setting. Newly started team sessions are covered by both monitor and responder automatically.
• Desktop app: native folder pickers and reveal-in-Finder actions.

(v1.1.2 was an internal staging release; its features ship publicly in v1.1.3.)

v1.1.1 (July 2026)

• Cursor CLI (beta): early support — govern Cursor sessions alongside Claude Code, Codex CLI (beta), and Google Antigravity CLI (beta).
• Ecosystem CLI preview: actower ecosystem — init, scaffold, hub, and list from the command line.
• Stability fixes across the monitor and web UI.

v1.1.0 (July 2026)

• Multi-CLI support: govern Codex CLI (beta) and Google Antigravity CLI (beta) sessions alongside Claude Code.
• Web UI train: refreshed dashboard UX, notification deep-links, single shared backend (port 1320).
• Desktop app: first notarized DMG release channel (actower desktop).

v1.0.0 (July 2026)

Initial release.

• Monitor: real-time agent monitoring across tmux panes — status filters (Working, Question, Idle), per-pane activity, Go to Pane, Expand/Collapse All.
• Auto-responder: smart classifier with 42 question types — safe operations auto-approved, risky ones held for a human. Click a question to jump straight to the single-question approval view, with full-color context preview.
• Local Web UI: Monitor, Responder, Activity, Logs, Settings — all on your machine, no cloud.
• Activity summaries: per-agent history with phase detection (Exploring, Editing, Testing, Git), action counts, and timeline.
• Reports: actower report (speed factor, risk distribution, busiest hours) and actower digest (files modified, risky actions, decision timeline).
• Audit trail: JSONL logs of every detection and decision, with JSON export.
• Claude Code Agent Teams: team member badges and role detection.
• Install: Homebrew (brew tap actower/brew && brew trust actower/brew && brew install actower) or the one-line curl installer. Free tier includes 5 monitored agents.