Foreman v1.2.3
Load a handoff without it running off
Loading a saved handoff or memory into a session used to fire a fixed message the moment you picked one, and that message always told the agent to pick the work up and continue — which is only what you wanted about half the time. Often you're staging context for a conversation you haven't had yet, and the agent charging off before you've said what you actually want is worse than no help at all. There's now a step in between: the message is shown to you first, editable, before anything is sent. A toggle switches it to "load this, don't start working yet", which swaps in wording that says exactly that. Both templates live in Settings under Context, so if you keep rewording the same sentence every time you can just change it once.
Launch again after a fan-out that only half-launched
Racing one prompt across several lanes could stop partway — a rate-limited launch, a laptop dropping — leaving some lanes running and some never started, and pressing Launch again made it worse rather than better. The retry now continues the run you started instead of beginning a new one: lanes that already exist are left alone, only the missing ones are launched, and the form freezes once the first launch goes out, because editing the prompt or the lane count between attempts meant lanes of the same race quietly received different prompts, or the retry reported success while doing nothing at all. When you ask the AI to pick a winner, an answer that could equally name two lanes is now reported as no winner rather than guessed at, since silently keeping the loser is the one outcome worth avoiding. And pinning the winner out onto the canvas no longer makes the race it came from vanish — the group stays put, still explaining the lanes that were spent on it.
Sessions that are still setting themselves up say so
A session running a project's setup script showed up as "Running" with an empty chat, which reads as an agent that has hung. It now says "Setting up…" until the bootstrap finishes, so the wait is visibly the machine's rather than yours. Setup scripts also stopped competing with real launches: a slow bootstrap no longer holds a launch slot that another session is waiting for, and one that fails reports its error straight away instead of queueing that report behind unrelated work. On a remote machine, a setup that hits its timeout now actually stops the command it started rather than leaving it running out of sight.
A heads-up before a schedule fires, not hours after
The schedule dialog already warned you at authoring time about integrations that need an interactive login and about an agent CLI that isn't installed or signed in on the target laptop — the things an unattended run can't fix for itself. GitHub was the gap: a scheduled run that reads issues or opens pull requests would fail at three in the morning and only tell you afterwards. The dialog now checks the target laptop as you write the schedule and says so if GitHub is set up there but signed out. If it isn't installed at all — the normal case for a schedule that never touches GitHub — it stays quiet.
"Show me" links in What's new
The what's-new panel after an update could only describe a feature and hope you went looking for it. Its items can now carry a button that takes you straight there — opening the Git view, a settings pane, or the dialog the note is about — and the panel gets out of the way as it goes, rather than sitting on top of the thing it just pointed at. Links that need something selected to make sense simply aren't offered when nothing is.
Fixes
A dev server that can't start because its port is already taken now says so in the preview panel instead of showing a blank page. The commit graph tells local branches apart from their remote counterparts rather than labelling both the same way. Change badges fill in for sessions that appeared while their checkout was being read, and the refresh spinner stops when the last refresh finishes rather than the first. Starting a session from the canvas surfaces the failure on the card if it doesn't start. The setup wizard clears its sign-in warning once you've signed in, instead of leaving it on screen.
macOS, Apple Silicon. Signed with a Developer ID certificate and notarized by Apple — opens normally with no Gatekeeper warning, and in-app silent auto-update is enabled.