Foreman v1.0.0
The canvas is now the default view
Sessions used to live in a flat list you scrolled and guessed at. The new orchestration canvas lays out your whole operation as a map: each project is a box, each session a card with live status, git changes, and cost, and machines you connect add their projects to the same map. Cards expand in place when you need the full chat and tuck back down when you don't. You can also chain a follow-up onto a running session — when it finishes, the next session launches itself, seeded with a handoff digest of everything the first one did, either automatically or after you review it.
Race the same task across parallel sessions
When the right approach isn't obvious, you can now fan a prompt out to up to four sessions at once, each working in its own isolated worktree on its own branch — optionally with a different model or effort per lane. The group renders as one raced cluster on the canvas; when the lanes finish, a compare view puts the diffs side by side, an optional AI judge weighs in, and one click keeps the winner's branch and discards the rest. Fan-out launches go through the same throttled gate as bulk runs, and the lane cap is enforced in the app itself, not just the dialog.
Turn GitHub issues into sessions
Your repo's open issues are now browsable inside Foreman. Queue the ones worth doing to a per-project triage board — queueing never starts anything — then start each one when you're ready, with one click on your defaults or with per-issue agent, model, and branch choices. The session's first turn carries the issue body and its freshest discussion, the branch is namespaced per issue, and the resulting PR defaults to closing it. Alongside this, a new stage lens groups sessions by what they need from you — a plan waiting for review, changes to look at, still working, or quiet — in both the list and the canvas, with a reload button to refresh git state on demand.
Fresh worktrees boot ready to work
Sessions launched into a fresh worktree used to start in a bare checkout and burn their first turns discovering pnpm install. Each project can now define a setup script and a run script: the setup runs before the agent ever starts (with live output, and a loud error card if it fails), and the run script gets a stable per-worktree port so dev servers from parallel sessions don't collide.
Squash, multi-cherry-pick, and safer history editing
The commit graph gained real history tools: select a contiguous range of commits and squash them into one, or cherry-pick several commits at once. Squash refuses anything unsafe — published commits, merge commits, or a merge sitting above the range — rather than quietly rewriting topology you didn't select. Branch tip labels on the graph are also more accurate, and sessions with very long names no longer break the layout.
A new coat of clay, and simpler sign-in
Foreman's identity is now consistent everywhere: a new app icon, clay-orange accents, a refreshed dark default theme (your old theme choice is untouched), a tightened type scale across the app, and terminal colors that match whichever theme you run. Signing in to Claude also got simpler — Foreman now just uses your machine's own claude login or an API key, shows each CLI's login state as a badge, and no longer offers to store a pasted token.
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.