ForgeLoopProduct updates
What changed in ForgeLoop.
Selected shipped milestones. For installer assets and checksums, follow the linked runner releases.
October 12, 2026 — Flexible issue intake
Choose how repository issues become eligible for ForgeLoop without changing execution or merge safeguards.
- Issue Chat can add the configured intake label when you approve issue creation.
- Administrators can bypass the label requirement per repository. Assignee rules, budgets and verification still apply.
- Both options retain the existing safer defaults; enabling earlier intake can incur provider charges.
October 12, 2026 — Runner 1.0.11 and consistent branding
The desktop runner and website now share the updated ForgeLoop logo mark.
- Matching Windows, macOS and Linux launcher/installer icons.
- Consistent dashboard tab headers and cleaner repository cards.
- Published installer checksums; desktop packages remain unsigned previews.
October 12, 2026 — Consolidated settings and chat management
Workspace configuration is easier to find and routine dashboard interactions require fewer steps.
- One Settings page for policy, repository budgets, intake and retained records; manual runs inherit configured limits.
- Persistent getting-started banner dismissal and remembered repository disclosure states.
- Confirmed chat-history deletion with permission checks; linked issues, runs and cost records are retained.
October 9, 2026 — Runner 1.0.10 and unattended delivery validation
Improved desktop navigation and corrected the verified-delivery approval flow.
- Refined review context and acceptance-criterion handling, plus safe no-op repair handling.
- Verified automatic publication and merge on a second repository without a human approval click.
- Windows and macOS packages plus Linux DEB, RPM, portable tarball and native Arch formats, for x64 and ARM64 targets.
Ready for your first run?
Connect a repository, set up your runner, and start with a small change you can review.