Agent Upstart

Cool things people are building with agents — and practical help getting the most out of them.

Playbooks · Coding tasks

Factory Droid 1.12.0: the November build

Written November 15, 2026

Factory Droid 1.12.0 is the November build. What Factory's own changelog lists, and what changes for a Droid user updating.

What shipped

Factory's own changelog lists Droid 1.12.0 — CLI and Desktop together — dated November 14, 2026, one day after 1.11.0. Its headline is namespaced tool names, fewer terminal redraws, and fixes across sessions, settings, and connectors. There are four improvements and twelve fixes, and the fixes carry most of the weight: two of them repair ways an account switch could leak one account's state into another's session, and several remove terminal-clearing behaviour that made sessions hard to follow. This is a polish release rather than a feature release, and for most Droid users the right response is simply to take it.

Namespaced tool names, and three smaller improvements

The lead improvement changes how tool calls read in the transcript: tool rows now show the namespace and capability for Droid command, connector, and MCP calls. In a long session that mixes built-in commands with connector and MCP tools, the row itself now says which family a call belongs to, instead of leaving you to infer it from the tool's name. The other improvements are narrower. A plain push or pull request now counts as medium risk, while force pushes stay high — a recalibration of the risk prompts a user sees before Droid acts. Revoking a service account key now records an audit entry for your organization, which matters to admins who need a trail for key lifecycle events. And the session sidebar now hides automation sessions until you turn that filter on, so the list a person scans shows their own sessions first.

The account-switch fixes

Two fixes address the same seam from different sides. Switching accounts no longer saves one account's organization settings under the other — a settings bug with real consequences, since organization settings applied to the wrong account can change what a session is allowed to do. And starting a session right after switching accounts now runs as the account you are signed in to. Together they close a class of confusion where the interface said one account while state from another was still in play. Anyone who works across two Factory accounts — a personal one and a work one, or two organizations — is the user these two lines are for, and they are reason enough to update promptly rather than at the next convenient moment.

Sessions, terminal, and connectors

The remaining fixes mostly remove small disruptions that compound over a day. Resizing the terminal no longer blanks the screen while the transcript is redrawn, and renaming a session no longer clears the terminal and replays the transcript. A resumed session now sends its earlier conversation with the first request when you start a run on a saved session id, so the continuation has its history from the outset. A todo list is recorded once, in the session whose call wrote it, instead of being duplicated. On the connector side, the Connectors settings page now shows a load error with a Retry option instead of reporting that no connectors are available — a misleading state that could send a user debugging a healthy setup. Trusting a folder from /cwd no longer clears the terminal or erases the change notice, a code span that crosses a line break no longer joins the words around it, alert actions stack under the text in narrow panes instead of squeezing it, and a failed gh or glab command whose error a pipe hides no longer records an artifact. Finally, turning telemetry off now also stops onboarding events from being sent, so the off setting covers the whole surface it appears to cover.

What to do

Update to 1.12.0. Nothing in the 1.12.0 notes asks for a settings change or a migration step before updating, and the account-switch and settings fixes argue against staying on 1.11.0 if you use more than one account. Single-account users get a quieter release: clearer tool rows, a calmer terminal, and a connectors page that tells the truth when a load fails. For the separate question of how Droid's harness performs — Factory's efficiency claims for the harness itself — see the claims page linked below; this release does not restate them, and its notes are about the product surface, not benchmark results.

Related playbooks

Sources

Back to: Coding playbooks hub · Also: Factory Droid 1.0 and the harness-efficiency claim · Antigravity CLI 1.5.7: Auto becomes the default