Skip to content

v0.4.8

Choose a tag to compare

@github-actions github-actions released this 08 Nov 15:39
· 4 commits to main since this release
49199f2

What's new in v0.4.8

Cursor works from setup, with no Formula hand edits (#388). Cursor codes but can't plan, so a Cursor Lab needs a second agent for reading Issues and planning.

  • Setup pairs Cursor with a planning agent (#414, #415).
    • forgecell init --harness cursor now proposes a Formula that declares harnesses.analysis on the first ready Claude Code or Codex.
    • If neither is ready, it refuses and saves nothing.
    • In the setup UI, Cursor's card says it codes only, and you pick the planning agent.
    • The review step shows "Plans with X · Codes with Y".
  • Change a role's agent later (#413). forgecell init --harness ID --role analysis|coding|meta proposes a reviewed change to just that role, for example --harness codex --role analysis. You approve it like any other Formula change.
  • Doctor and the plan view read per-role bindings (#414).
    • "GitHub Issue workflow" reflects the planning agent, so a working Cursor Lab no longer shows as unsupported.
    • The plan view says when the coding allowlist doesn't apply. Only Claude Code enforces it.

Adapter protocol is unchanged (11). Labs on 0.4.6 or 0.4.7 need only a launcher rebind (forgecell init --lab DIR --rebind <harness>, then approve).

Verified this release cycle on an outside repository:

  • Every pairing ran to a draft PR with CI green: Claude Code, Codex, Cursor (planned by Claude Code), Codex planning with Claude Code coding, and Codex planning with Cursor coding.
  • The pairings with Codex planning ran on code Issues with new tests.

Native Forgecell CLI for macOS and Linux (amd64/arm64), with per-artifact SHA-256 files, MIT LICENSE and dependency notices. End users do not need Node, Go or source-repository access.

This is a draft release for review, not automatic publication. The rendered installer pins this exact version and its v-prefixed tag at DanielNetzer/forgecell. Approve public visibility and exact-head Actions results before draft review and approved publication. Verify anonymous install, upgrade and rollback before switching the documented legacy endpoint.

Installer activation smoke-checks the version and preserves Lab data. forgecell rollback restores the previous validated release. Running tickets requires Git, authenticated gh and a configured coding harness.