Changelog

DevThrottle ships continuously. The authoritative, always-current changelog is the GitHub releases feed, where every version lists its merged changes. Highlights of the recent line:

v2.0.2 - August 8, 2026

A small release that finishes the mission lifecycle. Missions could be started but never ended, and the fleet was found in exactly that state - eleven missions, several of them finished days earlier, with no way out of the list. You can now end one - from the command line, which is the whole surface for this until the Cockpit gets an archive view.

• A mission can be ended, renamed, or brought back. A mission is the body of work a session belongs to. Until now nothing anywhere could end one, so the list only ever grew, and finished work sat beside live work with no way to tell them apart. Five commands now do the whole lifecycle: cc-devthrottle mission rename, mission complete, mission remove, mission reopen, and mission list filtered by state - --all or --state active|complete|removed. All of them are in the agent-discoverable actions list, not just the help text, so an agent that finishes a body of work can find the verb that ends it.
• The wording is most of the work here, because these commands are the only surface for it. A rename names the old name too, so it is visible which mission moved, and says the identifier is unchanged - because "will this detach my sessions" is the first thing anyone wonders. Ending a mission says where the record went and how to get it back, naming both the list command and reopen: there is no other way to see an ended mission yet, so a bare "done" would leave you unable to find it. An empty filtered list says which list is empty, because a bare "no missions" under a filter reads as "you have none at all" - a different and much more alarming thing. And a mission with no stated reason for existing is flagged rather than shown as an empty cell, the same rule the Cockpit card follows.
• Your agents can actually use those commands. The commands above reached a service that refused them: every mission verb answered 403 for an agent session, on a service that had just been given the routes - a session key could create a mission and read one, but not change one. An agent may now change a mission it can already create and read. This is no wider than what it already held - the mission is resolved inside the caller's own account, and another account's mission answers "not found" exactly as a read does.
• Also in this release. mission create --parent is gone: missions are flat now, and the flag was still sending a parent identifier to a service that no longer has the field. Resolving a mission by name or short identifier now looks at every mission rather than only the active ones - without that, reopen was impossible, and rename failed on exactly the missions most likely to need correcting.

v2.0.1 - August 7, 2026

A hardening release. Every item here is a defect found during or just after v2.0.0, several of them by walking the product on a clean machine as a new user would, and several more by an independent review that sent the work back before it shipped.

• Your dictionary now reaches your own dictation. If you use DevThrottle in the cloud, the words you added to your dictionary were not affecting your dictation at all: the correction pass read a shared dictionary rather than yours, so adding a term you say all day changed nothing, and the promise that your dictionary follows you everywhere quietly failed. Your dictation now reads your glossary. Two details worth stating plainly, because either could have been got wrong and both were checked: if you have written no dictionary you get no correction, never somebody else's terms; and running DevThrottle on your own machine is unchanged.
• A broken dictionary no longer costs you the transcription. A malformed or unreadable dictionary file could fail the whole transcription instead of stepping aside - backwards, since the dictionary exists to improve a transcript. One that cannot be read is now skipped and you get your raw text. It does not fall back to anyone else's terms either: failing open means your own words, not a stranger's spelling.
• The dictionary never did bias speech recognition, and now says so. The product told you, in the app and on the phone, that your terms were "biased into speech-to-text". They were not, and the code path that would have done it had no caller - your audio goes to speech recognition untouched, and your terms are applied afterwards to the finished transcript. The wording is now what actually happens everywhere it appeared, and the dead path is gone. This changes no behaviour; it stops the product describing a design it does not have.
• A request we cannot place is refused rather than guessed at. On the hosted service, one voice route would accept a request whose account could not be resolved and quietly treat it as a local, single-machine request - reading the shared dictionary and filing the transcript in the wrong place. Every comparable route already refused; this one now refuses too.
• Also in this release. The Missions board groups sessions by the mission they belong to, hides missions with nothing in them, and always tells you how many there are. Dictation no longer carries a finished recording into a session you have since moved on from - the guard now arms from both ways of starting to speak. The root folders caption says what actually happens: discovery is the local scan. And workflow run accepts the short run id it prints to you, while a web page answer is never mistaken for data.

v2.0.0 - August 6, 2026

On 5 August every session on every machine was locked out at once. The cloud Gateway was older than the app talking to it, so it refused each session's credential, and every command an agent ran answered "missing or invalid token". The outage lasted hours rather than minutes because nothing said so - the Home page showed no problem, and the error the command line printed blamed the credential, which was fine all along. That is what this release fixes.

• The Home page shows a red Sessions row when the Gateway will not accept this Director's session keys, and says that it affects every session rather than one. Previously that state produced no row at all, so the one screen built to surface it was blank while the whole fleet was locked out.
• The command line no longer blames your credential. A refused session key now explains that the Gateway may simply be older than the app - and says which line in the log tells the two apart - instead of asserting that your token is wrong. It deliberately does not guess which cause applies, because it cannot tell from where it stands.
• The app asks the Gateway what it can do the moment it connects, and says plainly in its log when the Gateway is missing something it needs. Before, it discovered this one failed call at a time, from an error carrying no version and no detail.
• Sessions no longer go permanently silent. A session could stop speaking forever with nothing reporting a fault - its rail sat on "Preparing voice" indefinitely, it was never played, and no error was raised anywhere. The cause was a corrupted internal pointer: something could overwrite a session's record of its own transcript with a value that was not a transcript at all, after which the session could never be narrated again. Running DevThrottle's own test suite from inside a live session did exactly that, which is how it was found. Both halves are fixed, and a session already damaged this way is repaired by restarting it.

If you run your own Gateway, update it as well as the app. This release changes what the app asks the Gateway for. An older Gateway will still work - that is tested in both directions, and the app now says clearly when it happens - but the fleet features are only fully available once both sides are current.

v1.9.11 - August 5, 2026

Your plan now includes the AI features, the phone recorder lasts all day, and the Windows application finally carries the current mark.

• The AI features are included in your plan - no credits needed. Dictation, spoken replies, session naming and the Wingman come with DevThrottle Pro and with the 14-day Pro trial, and the app no longer asks you to add credits for any of them. Dictation and voice work on a brand-new account from the first minute, with no balance to top up. The Wingman, session naming and dictation cleanup run on DevThrottle's included models, and the model settings offer exactly those models, so a saved setting can never route your included features onto paid API models. If your trial has ended and you have no subscription, the app says so plainly and points you to the pricing page rather than asking you to buy credits for features credits do not buy. Prepaid credits remain what they always were: optional, and only for calling the DevThrottle model APIs directly with your own API key.
• The phone recorder lasts all day. Recording no longer stops at a default time cap, keeps capturing while you navigate between screens, and shows a recording indicator on every screen. It holds a wake lock and asks Android to exempt it from battery Doze, so long recordings are not silently killed in your pocket. If a recording ever has to be cut short, it is cut short loudly - you are told, instead of discovering a truncated file later.
• The Windows Director shows the current mark, not the old name. Every surface had moved to the new mark except the Windows executable, which still carried the old two-C icon in the taskbar, Alt+Tab, the title bar and the installer's file properties. Windows and macOS now match, and the icon carries nine drawn sizes instead of four, so it no longer looks soft at taskbar scale. Windows caches application icons aggressively: if a pinned shortcut still shows the old mark after updating, unpin and re-pin it, or sign out and back in.

v1.9.10 - August 5, 2026

A single fix: the Handovers list in the New Session dialog now shows your newest handover first.

The tab ordered documents by their filename rather than by their date. Handovers written by the product itself are named for what they are - a session move, a rebuild manifest - while the ones you write are named for the day and minute they were written, and sorting those names as text floated every name beginning with a letter above every name beginning with a date. The result was a list that looked sorted but was not: a handover written minutes ago sat thirteenth of a hundred and forty-three, below a dozen machine-written files, and the date shown against each row ran out of order the whole way down - so the one column you would use to find your document was the one column you could not trust. The list is now ordered by that same visible date, newest first, which is how the Cockpit has always shown it. Reading the list is also no longer done on the interface thread, so opening the tab with a few hundred handovers no longer briefly holds up the window.

v1.9.9 - August 5, 2026

The portless release. Until now both the Director and the launcher listened on a local network port, and agents could reach the fleet two different ways - through the Gateway, or directly through that port. Neither listens any more: everything an agent does now goes through the Gateway, one door, always.

• Windows will not ask about the network on first launch, and cannot start asking again. The security prompt that appeared on top of the setup wizard, swallowing the clicks meant for it so a new install looked frozen in its first minute, was caused by the Director opening candidate ports to test them. v1.9.8 stopped the prompt by narrowing what that code touched; this release deletes the code outright, so the cause is gone rather than avoided.
• Your agents stop having a wrong door to find. An agent that can reach the fleet two ways will eventually use the wrong one, and documentation does not fix that. There is now one way, so there is nothing to choose - and the product stopped shipping agents instructions that pointed at the old door. A machine that never accepted a connection cannot have one guessed at, scanned, or exhausted.
• A security fix you did not ask for. Skill, workflow, schedule and mission commands used to read your account-wide credential from disk and present it, which meant any agent running one of those commands held authority over your entire account, on every machine - true of every release before this one. Each session now gets its own credential instead: bound to that session, limited in what it may call, expiring, and revoked when the session ends. An agent can still change how the product behaves - settings, handovers, sessions, missions - but it cannot change who is allowed in. Device enrolment and account identity are refused to it.
• What you will notice day to day. Fleet-wide commands are slightly faster, since the local hop is gone. A session reading its own terminal is slower - roughly a third of a second to under a second against a hosted Gateway - because what used to be a local read is now a round trip. With no Gateway reachable, agent tooling does not work: a deliberate trade, not a regression, and the error says so plainly and names the self-hosted gateway as the answer. Starting, stopping and updating the application still work with the Gateway down, because process lifecycle never asks the Gateway anything.

Update the launcher with or before the Gateway. A launcher older than this release registers normally but cannot be commanded by an upgraded Gateway, because commands now travel down the connection the launcher itself opens; if that state occurs, the refusal names the cause rather than failing vaguely. Stated honestly: the Director still opens a local listener during interactive sign-in, to receive the callback from your browser - loopback-only, lasting as long as the sign-in, and carrying nothing an agent can call. The Director runs without a listening socket; it is not that it never opens one.

v1.9.8 - August 3, 2026

Sessions can now move in and out of missions while they run - shipped quietly in v1.9.7 and announced here - and a brand-new Windows machine's first minute no longer looks broken.

• Move any session in and out of any mission. The v1.9.7 release included this and its notes never said so, so it is announced here. A session no longer has to be born into a mission: attach any running session to a mission, move it between missions, or detach it entirely - from the command line, with no restart and no respawn. cc-devthrottle mission attach attaches a session, or moves it if it already belongs to another mission, and tells you which mission it left; --with-children also brings along every session the target controls, all the way down; cc-devthrottle mission detach returns a session to belonging to no mission, the ordinary state. The session's workflow seat moves with it, so a session shown under one mission is never quietly governed by the conduct of the one it left, and a seat you chose yourself at spawn is preserved. Sessions spawned by a controlling session now also inherit that session's mission by default, so a team stays a team without anyone remembering a flag. One honest limit: a running agent keeps the instructions it was handed at birth, so after a move the command tells you exactly how to ask the session to fetch its current conduct.
• The setup wizard no longer appears frozen on a brand-new Windows machine. Windows showed its firewall security prompt directly on top of the wizard's first button, where it silently swallowed every click aimed at it - no error, the product simply looked broken in its first minute of use. DevThrottle no longer does the thing that made Windows ask: it now checks candidate ports on the machine's internal address only, so the firewall prompt does not appear at all.
• Browser profiles is one clickable row again. The entry in the Director's side rail used to unfold into a list of every profile with its own Start link, taking a third of the visible rail. It is now a single row showing the profile count and a green dot when at least one is running; clicking it opens the Browsers settings screen, where all the actions already lived.
• A logging fault can no longer take down the work that was being logged. Stopping and restarting the application's log writer left it in a state where every later log line threw an error into whichever operation happened to be logging - so one defect surfaced as several unrelated, unreproducible failures. The writer is now replaced rather than revived, and a log call that cannot be accepted is dropped and counted instead of thrown. This one fault was behind most of the sporadic test failures seen on the local gate.

For people running the source, two test-suite fixes make the local gate more trustworthy: a backoff test now measures the code's behaviour rather than the machine's load at that moment, and a test that takes the machine-wide gateway lock is kept out of the parallel run, where it could stall the whole run indefinitely. Known and not fixed here: the Director's large-object heap still grows on an instance left running for days, a vault catalog scan over a synced folder can run away (diagnosed, not fixed), and four repository views still show a failed git read as an empty result rather than saying the read failed.

v1.9.3 - July 31, 2026

A security release. The Director's local control interface now requires a credential, and terminal session recording is off unless you switch it on.

• The local control interface requires a credential. Anything on your machine that talks to the Director - the command line, hooks, the launcher, the settings tools - now presents a credential it is given automatically, and requests coming from a web page in your browser are refused. The tools that needed credentials were updated in the same change, so there is nothing for you to do.
• Terminal session recording starts off. It used to record by default and keep everything indefinitely. It is now a visible setting that starts off, recordings are deleted when their session is removed, and recordings left behind by earlier versions are cleaned up the first time this version starts. If you have old session recordings you want to keep, copy them out before you upgrade.
• The download comes from DevThrottle's own storage. The download link on this site used to point into GitHub's release storage; the release pipeline now publishes it directly.

v1.9.2 - July 31, 2026

The main window fits the screen it opens on, a first install stops reporting its own success as a failure, and sessions stay in the Director when a machine's connection wobbles.

• The window fits the screen. The main window could open larger than the display it was on, putting the Settings button off the right edge - which quietly broke every "you can change this later in Settings" the setup wizard says. The window is now measured against the screen's usable area and centred before it is shown, down to a 1280x720 display.
• A first install stops calling a healthy launcher dead. On a clean machine the launcher unpacks itself on first run, which took longer than the installer's fixed twenty-second allowance - so the install ended on an error while the launcher was answering perfectly well. Waiting is no longer treated as a verdict.
• Sessions survive a wobbly connection instead of vanishing from the Director, and renaming a Director now carries everywhere.

v1.9.1 - July 30, 2026

The app stops getting slower as sessions pile up, and one number was removed on purpose.

• The context percentage is gone where it was guessed. The gauge divided real usage by a context window inferred from the model's name, which was wrong for the model DevThrottle is most often run with - a session with roughly 800,000 tokens of room left could read 92 percent in red. DevThrottle now shows a context window only when the agent itself reports one; where it does not, you get the raw token count with no percentage. A missing number is an annoyance, a confident wrong one gets acted on.
• The app stops feeling slow as sessions accumulate - three costs that grew with every open session were measured and cut - and buttons answer the moment you click them.
• Auto-update says which situation you are in rather than leaving you to guess.

v1.9.0 - July 30, 2026

DevThrottle speaks French and Spanish, and several things that used to fail quietly now say so.

• Pick a language and everything spoken follows it. DevThrottle speaks from four places - the narration of what a session just did, the direct reply when you ask it something, the in-product help, and the assistant. The speaking rules now live in one place, so a language reaches every spoken path. What is translated is what DevThrottle says: the on-screen text stays English, deliberately, for now.
• The voice choice is not evenly matched, and the screen says so. English has twenty-eight voices, Spanish three, French exactly one. English is unchanged unless you choose otherwise.
• Car Mode is out of the product for now. The assistant that shared its underlying brain stays - it is the same thing that answers you in the app.
• A prompt that was never delivered is surfaced instead of being recorded where nobody would look.

v1.8.1 to v1.8.8 - July 27 to 30, 2026

A fast line of releases between the work-history release and 1.9. The ones worth knowing about:

• Updating became something you can check (v1.8.8). DevThrottle has updated itself for a long time; from this version something is left behind to verify that the update worked, and to put the previous version back when it did not.
• Agents launch ready to work (v1.8.6) instead of asking for approval on every call, and a whole skill directory can be held and placed where each agent looks for it.
• The installer offers Git (v1.8.3), which the app needs to read repositories at all, and the macOS file-search guidance now names the path to grant access to.
• Every session records who started it (v1.8.2), and History shows the shape the work had rather than a flat list. The screenshots folder you set is the one you see.
• Cockpit dictation matches the phone (v1.8.1) - live level bars and a Speak button that sends without making you wait on it.

v1.8.0 - July 27, 2026

Every session now tells you its story: when it started, how long it has been open, how long it has been waiting on you, and what it did - live on the session cards, and kept in a durable work history you can read back across all your repositories.

• Session cards answer the supervision questions. Every card in the Cockpit and on the phone now shows when the session started, how long it has been open, how long it has spent waiting on you, and how many turns the agent has completed - ticking live. Waiting time turns amber after an hour and red after four, so a neglected session looks neglected.
• Work history. DevThrottle keeps a durable record of every session as it runs - what it was asked to do, how it ended, and a summary of what it built. The new History page shows your work across all repositories, grouped by repository and day, and survives crashes and power cuts because the record is written while the session runs, never at the end.
• First-run wizard. Setting up a new machine is now one guided journey instead of a chain of dialogs - it finds your coding agents, offers to install what is missing, locates your repositories and screenshots, and explains each step as an offer, never a demand.
• Fleet Assistant. Ask questions about your whole fleet in plain language - by chat or voice, from the Cockpit or the phone - without being tied to any one session.
• Trustworthy voice input. Test your microphone and test transcription from Settings on both surfaces, and DevThrottle now measures every dictation's microphone quality in the background and shows the detail in a Transcription Health view, so a bad microphone gets caught before it ruins a day of dictation.
• One Settings page. The phone and the Cockpit now show the same Settings - same tabs, same names, same cards - so a setting you find on one surface is where you expect it on the other.
• A 14-day Pro trial for every new account.

Also in this release: voice mode is a real switch with the way out on every screen, and the voice queue plays the waiting sessions first-in-first-out with big buttons on top; the phone's voice recorder is back, with durable segments that survive interruptions and transcripts on both surfaces; the mobile Snooze button lets you pick a length, and a session returning from an expired snooze is labeled so you know to go see why it went quiet; repositories are a first-class subsystem - an always-current monitor, safe worktree and branch cleanup with an orphaned-worktree reaper, and a worktree that an open session is using is never touched; the shared workflow library lets you browse the built-in workflows, switch them on or off per account, and clone one to customize it; each session's uncommitted file count shows in the roster, so you can see who is sitting on unpushed work; the session roster puts Sessions first in the rail, and the Needs-you group is a waiting line with the longest-waiting session on top; the phone says nothing about the network unless something is actually wrong; no user is ever shown a bare status code - errors arrive as plain sentences, and browser errors also land in the Gateway log so they can be diagnosed after the fact; the About page reports the Gateway, Cockpit, and mobile app versions; one Director executable can run several named profiles, and a staged update applies itself automatically when no sessions are running; scheduled runs name their sessions after the schedule and fire time, and asking an agent to clear a session's context now asks you first; and many reliability improvements to the hosted service, including safer deploys with a warmed standby, honest network verdicts, and per-account serving of settings, statistics, and transcripts.

v1.7.4 - July 23, 2026

The macOS setup wizard now mirrors the Windows one, the hosted gateway now scopes every surface by account, and dictation is more reliable and more honest when something goes wrong.

• The Mac setup wizard, rebuilt to match Windows. A cleaner Welcome screen, the obsolete Standard/Developer choice and the separate Gateway step are gone, and uninstall is fully ported - so setting up on a Mac is the same simple flow as on Windows.
• Strict account isolation on the hosted gateway. A large hardening pass makes every hosted surface account-aware - directors, sessions, voice, devices, stats, and keys all now enforce account-scoped authorization - and per-device keys are stored hashed at rest.
• More reliable, more honest dictation. Dictation keeps your last word instead of clipping it, pads trailing silence, and warns you when a send drops audio instead of shipping silence - across the desktop, the Cockpit, and your phone.
• macOS tools fix. The command-line Python tools now find their config on macOS, shipped through the tools bundle.

Also in this release: the desktop status box shows which gateway you are on and its connection state; Send-direct from the Cockpit Speak box sends the transcribed text; scrollbar thumbs draw at full thickness instead of a hover-only sliver; and many correctness and test fixes across the fleet.

v1.7.1 - July 21, 2026

You can now change which gateway a Director connects to right from the app - disconnect and reconnect to a gateway on your own machine or the hosted one, without editing any files.

• Change gateway from the app. Settings → Gateway has a new "Change gateway" button: it disconnects this Director and takes you back to the connect screen to pick another - your own machine or the DevThrottle hosted gateway. No config files, no command line.
• One-click hosted connect. The "Use hosted" choice is live - sign in with your DevThrottle account in the browser and the machine joins the hosted gateway under your account, with no address to type.

Also in this release: if a new connection does not take effect immediately, the app now tells you clearly instead of sitting on "Connecting".

v1.7.0 - July 21, 2026

Sign in with your DevThrottle account and control a hosted cc-director from the Cockpit and your phone - on the shared hosted gateway, with each account seeing only its own work.

• Sign in on the hosted gateway. Open the Cockpit or the phone app, sign in with your DevThrottle account, approve the device once, and land in your own hosted Cockpit - no tokens to paste. Everything you see is scoped to your account.
• The Cockpit opens from the gateway address. Clicking Cockpit on a hosted director now opens the real hosted Cockpit in your browser. The Cockpit and the phone app are both reached from the one gateway address - its cockpit and mobile paths - the same way whether the gateway is hosted or running on your own machine.
• Strict separation between accounts. The gateway works out which account a request belongs to from the signed-in identity alone, never from anything the browser or app claims, and refuses by default anything it cannot place. One account's directors, sessions, voice, and usage stay entirely separate from another's.
• A hosted gateway is a paid gateway. Signing a device in to the hosted gateway now requires an active subscription. A gateway you run yourself is unchanged and needs no subscription.

Also in this release: the phone app now lives at the gateway's mobile path, with the old address redirecting so nothing you have bookmarked breaks; the in-window Fleet Map was removed from the desktop app; voice recordings still uploading are cleaned up on an activity-aware schedule; and a plain-English guide to trying the hosted gateway is in the documentation.

v1.5.0 - July 16, 2026

The Gateway becomes the single source of truth for what each session is doing, you can install from the command line with no wizard, and the Gateway core gains the groundwork to run beyond Windows.

• One honest picture of every session. The Gateway now decides each session's state and pushes it out, so the desktop rail, the Cockpit, and the mobile roster all show the same thing - including how long a session has been on hold and when it is winding down - instead of each surface guessing on its own.
• Install from the terminal, no wizard. A command-line installer sets DevThrottle up end to end from the terminal on Windows and macOS, and macOS gets a curl-based install that Gatekeeper cannot block. Command-line sign-in is Windows-only today; on macOS a machine joins your gateway with enroll instead.
• Groundwork to run the Gateway anywhere. The Gateway now runs headless on Linux and macOS, proven in a Linux container, and ships with a Dockerfile you can build yourself. This is foundation work - the Gateway downloads are still Windows-only.
• See what you have spent. New governance screens show your usage by day, week, and month, and each session's token spend is stored and sliced by hour and model.

Also in this release: the text injected into every new session is now a Gateway-owned setting you can view and replace; a self-imposed hold now goes through the Gateway and actually takes effect; Your Throttle stats recognize Azure DevOps remotes alongside GitHub; remote session spawn works over a tunnel-only connection; the move-session skill ships; and the Speak box opens instantly without ever opening a second copy.

v1.4.0 - July 16, 2026

A big reliability-and-visibility release: the fleet's voice is steadier, your stats now show which AI model did the work, and the desktop app gains a live fleet map.

• See which model did the work. Your usage stats now break down by the AI model and the agent tool behind each turn, and each session's token spend is carried up to the Gateway, so you can see what you actually ran.
• Live fleet map in the desktop app. Watch every session across your machines at a glance, click to select, with the controller spawn tree laid out.
• Know who is speaking. The wingman says which session is talking before it reads a summary, so when you are listening without looking you always know who is speaking.
• Steadier voice. A single slow moment on one session no longer silences narration for the whole fleet, and when speech genuinely fails you are told the truth instead of getting silence.
• Pick a snooze length. The desktop and Cockpit menus now offer a list of snooze durations, not just one default.

Also in this release: the Gateway now runs as a background service with a simple Start and Stop tray, and first run no longer asks for a pairing code or a consent window; the mobile app's layout was reworked to sit correctly in the visible screen area, with play controls that mean the same thing everywhere; the Cockpit's settings are organized by topic, the session rail scans by icon, and workflows are served straight from the Gateway; many session-state corrections, so a session's colour and status always tell the truth; and more resilient dictation - a dropped dictation is now loud and gives your words back rather than failing quietly.

v1.3.0 - July 14, 2026

A reliability-and-honesty release: when something goes wrong you are told, and a session's state always tells the truth.

• Honest failures. A dropped command now explains itself instead of hanging or returning a bare error, and writing into an agent's terminal tells you when it fails.
• Session state you can trust. A working session is always blue, matching the spec, so a session's colour and status tell the truth.
• Full prompt-and-reply logging. Every prompt and reply, for all agents, is recorded with where it came from.

Also in this release: the inbound network port was closed and Director Settings restored, removing a connection check that could only mislead; and a cleanup pass deleted dead code, corrected the public API reference, and removed documentation describing features that never shipped.

v1.2.0 - July 14, 2026

This release brings session rename and close back, fixes glitches on large replies, and adds full macOS support.

• Session rename and close work again across the fleet.
• No more glitches on large replies. Voice, Wingman, History, and the mobile session roster stop blinking when a reply is large.
• macOS support. Mac builds, app-bundle placement, launcher start, and the command-line tools.
• Clear All screenshots deletes the files on disk after a warning.
• New Session picks the agent, not the model.

Also in this release: Tailscale is no longer required to install; a per-repository default for Open in Browser; Repos becomes a fourth tab of Your Throttle; the terminal verifies every prompt actually submits, not just large ones; snooze honors a requested duration; and fleet-wide "message all" is back.

v1.1.0 - July 10, 2026

This release gives your sessions real roles and missions, lets your other machines connect without opening a port, and makes voice dictation and long recordings far more reliable.

• Session roles and missions. Every session now shows a role at a glance - Architect, Manager, or Worker - and related sessions group into a named mission. Roles are worked out automatically from how you start and connect sessions; you set the Architect yourself for the session that plans and oversees the work.
• Connect other machines without opening a port (preview). Let your other computers connect to your main machine without opening or forwarding a network port - the other machine reaches out instead of waiting to be contacted, which is simpler to set up and safer. Opt-in and off by default for now.
• More reliable voice dictation on your phone. Dictation holds your audio in a durable queue and keeps trying to deliver it, so a brief network problem or an app restart no longer loses what you said - with clear status instead of silent failure.
• Long recordings and clearer transcription. Long voice clips are split at natural pauses and transcribed in parallel, and a failure now shows a plain-language message instead of a raw error.

Also in this release: a clearer signed-in version and self-repair in the phone app; fewer duplicate and stale notifications; Wingman voice fixes; a security fix that stops the Gateway leaking extra service keys; in-app image generation available again; and a simpler, more focused interface with several in-progress panels removed while they are finished.

v1.0.6 - July 6, 2026

• Cockpit: major port of the Director experience to the new React Cockpit - session roster and rail, reply and action bar, fleet views, schedule, dictionary, and account pages.
• Mobile: voice-mode audio player (resume, restart, seek), durable server-owned dictation upload (a refresh never loses recorded audio), and screens that stay awake.
• Reliability: crash-safe Python tools install and Director self-repair of a broken shared runtime.

v1.0.0 - July 4, 2026

• First stable release: the signed Windows installer line (Azure Trusted Signing) that ships from devthrottle.com today.

Before 1.0

The 0.9.x line was the pre-release run-up during quiet launch week. Its history is preserved in full on the releases feed.