v0.3.0

Forge v0.3.0 adds relays for faster GitHub updates, one-click agent quick actions, built-in MCP, federated workspaces, a dedicated phone workflow, and GitHub Actions controls.

Relays

Connect Forge to an optional shared relay to see GitHub pull request, issue, and CI updates sooner, between regular syncs. The Relay panel shows connection status and recent activity, and normal syncing catches up after an outage.

A relay can serve multiple Forge instances while each keeps its existing GitHub credentials. See the relay guide for connecting Forge or running a shared relay.

Coding agents and workspaces

• Quick actions let you create a workspace, launch an agent, and send a saved prompt from a pull request or issue in one click. Configure your actions in Settings.
• Forge now has a built-in MCP server. Connected tools can create or reuse workspaces, launch coding agents, and send follow-up prompts to running sessions. Configure it in Settings and get connection instructions with kenn-forge mcp quickstart.
• Agents can triage a repository's open pull requests using cached checks, review decisions, mergeability, labels, and recent activity, including filtering by label.
• Launch Pi alongside the existing coding agents, or use custom launch targets through MCP. When no agent is specified, MCP uses your recent launch history to choose one.
• Sort workspaces by agent status or recency, spot uncommitted changes in the list, and optionally show live agent status alongside pull requests, issues, and Activity.
• Resume saved Codex, Claude, and Pi conversations after a restart when possible, while preserving local commits and uncommitted files.
• Choose whether workspaces initially show the diff or their source pull request or issue, and optionally initialize RoboRev in Forge-managed workspaces.
• Workspace startup can reuse checkouts prepared in the background and no longer waits for automatic PR or issue assignment before starting setup.

Federated workspaces

Connect Forge instances in a hub-and-spoke fleet. One hub syncs provider data and presents workspaces across your machines, while each spoke runs its own local workspaces and agents.

See which machine owns a workspace and use the hub's Run on selector to place new repository work on a chosen machine. Local workspaces and agent launches remain available on spokes during hub outages.

See the fleet guide for setup, upgrades, and replacing a hub.

Phone workflows and terminals

• Use a dedicated phone workspace list and terminal view, with session switching, a growing input tray, and controls for Esc, Tab, arrows, and other keys missing from software keyboards.
• Review pull requests and issues, follow workspace links, and access CI status and merge actions from the phone layout.
• Terminals display images and support tmux mouse input, both configurable in Settings. Paste browser images into local or remote terminal sessions.

Pull requests, reviews, and Activity

• Run manual GitHub Actions workflows and inspect runs, jobs, and steps in the optional Actions workspace. Pull request pages offer Run workflow with inputs, environments, and Git ref selection.
• Save named repository filter presets and hide individual repositories from navigation without stopping their sync.
• Filter Activity by actor, search by issue or pull request number, find unassigned work, and use Involves me across work views. Issue lists can filter for items referenced by pull requests.
• Add review comments spanning multiple diff lines where the provider supports them, and request changes directly from the dropdown beside Approve.
• Navigate directly between changed files, collapse or expand all files, and hide the file tree to give the diff more room.
• See each pull request's position in its stack from the list.
• Optionally collapse single line breaks in descriptions and comments, or render commit messages as Markdown.

Sync, providers, and performance

• Give historical archiving its own GitHub App capacity so it competes less with ordinary sync.
• Configure faster refresh for recently active pull requests, including ones you have not opened.
• Use explicit base URLs for self-hosted Gitea installations.
• Reuse existing glab logins for GitLab and fj logins for Forgejo or Gitea when no explicit token is configured, just as GitHub can reuse gh authentication.
• Large Activity feeds and discussion histories load more efficiently. Idle workspaces, background browser tabs, and fleet monitoring use fewer resources, and terminal streams use less bandwidth.

Documentation and Go libraries

• Expanded guides cover Activity, repository browsing, workspaces, Docs, Settings, fleets, and relays. The website also offers a product walkthrough and Markdown documentation for agents.
• Go applications can use Forge's public provider clients and GitHub App helpers independently of its application database.
• A new landing-analysis library identifies landed work across merges, squashes, rebases, and fast-forwards, with GitHub.com evidence collection.

Upgrade notes

• Kata now owns task browsing and editing. Forge keeps task links and read-only details, with links to open Kata.
• The built-in MCP HTTP listener replaces the standalone MCP command and stdio transport. Update clients to use the listener configured under [mcp].
• Hub-and-spoke federation replaces SSH fleet control. Existing SSH fleet settings require migration. Existing protocol-3 fleets need the documented offline fleet migrate-protocol upgrade.
• Forge now uses a dedicated tmux server by default. Sessions created on the previous global server are no longer visible to Forge; see the configuration guide before upgrading active sessions. Explicit custom tmux commands remain supported.
• Workspace activity no longer changes pull request, issue, and Activity ordering by default. Enable workspace recency in Settings to restore that behavior.
• Background checkout preparation uses extra disk space: one spare checkout per source repository and workspace destination directory.
• For early relay deployments, remove the retired relay.poll_interval, database, and retention settings as described in the relay guide. Upgrade the relay and connected Forges before enabling workflow webhooks.
• Building Forge from source now requires Go 1.27. Documentation URLs have moved under /docs/; update bookmarks to old root-level pages.