Skip to content

Foreman v1.5.0

Choose a tag to compare

@R3tter R3tter released this 23 Aug 07:12
62fd66a

Sessions stop insisting your login failed

A session that hit an expired CLI login was marked "Auth failed", and that mark was only ever reconsidered when the session next finished a turn. A session you had left idle never produces one — so signing back in fixed the CLI, the app kept saying otherwise, and the warning returned on every launch no matter how often you dismissed it. Verifying a sign-in now clears the mark from that machine's idle sessions too. It stays scoped: verifying Claude says nothing about a Codex session, and a session using its own API key is left alone, since no CLI sign-in would fix that one.

The attention dot lands on the session you were actually working in

When several sessions share one checkout, a pull-request signal — failed CI, a review, a branch ready to merge — is about the checkout rather than any one session, so Foreman marks a single session to carry it. It was picking the oldest record for that folder, which is restore order, not activity: a red CI run would light up a session nobody had opened in weeks while the one doing the work sat unmarked. It now marks the most recently active session instead, and skips sessions with nothing running behind them, where a dot read as "something happened here" when nothing had.

A project's MCP config can no longer run commands on your machine

Foreman's "log in" button for an MCP server built a small script from the server's name. A name is not necessarily yours — claude mcp list includes servers defined by a project's own .mcp.json, so opening a cloned repository could contribute one — and a name containing the right punctuation could break out of that script and run whatever it liked, on macOS, the moment you clicked to sign in to it. Server names are now quoted everywhere they are used, so a hostile one is inert text rather than a command. Nothing about signing in to your own MCP servers changes.


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.