Repository navigation
feat: port Forge to OpenCode v2.2.5 - #61
Merged
Merged
Conversation
Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com> Co-authored-by: LukeParkerDev <[email protected]>
Co-authored-by: Aiden Cline <[email protected]>
…r tray (anomalyco#60284) Co-authored-by: Kit Langton <[email protected]> Co-authored-by: Aiden Cline <[email protected]>
…nomalyco#59310) Co-authored-by: vimtor <[email protected]>
Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com> Co-authored-by: Aiden Cline <[email protected]>
…invalid checks immediately (anomalyco#60349)
… rail's resize handle
divyanshusingh2903
force-pushed
the
v2-port
branch
from
November 4, 2026 04:39
110d6a8 to
fe5c939
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Issue for this PR
Part of #60
Type of change
What does this PR do?
Moves Forge from the OpenCode v1 line (last synced at v1.19.0) to OpenCode v2.2.5. v2 removed
packages/opencodeand split it intocore,server,protocol,clientandcli, so a rebase wasn't possible.v2-portis a fresh branch from thev2.2.5tag with Forge's changes ported on top. The last v1 release is taggedforge-v1-final.What's on the branch, beyond upstream v2.2.5:
forge://, icons, accent colour, wordmark and README. The Forge name replaces OpenCode in the UI strings, while OpenCode's own services keep their names.forge-releaseworkflow, plus Linux window controls.Existing v1 sessions don't carry over (no DB migration), as decided in #60.
Still open, tracked in #60: terminal on the v2 pty, chapters, background tasks, instance registry and crash recovery, and UI polish. The Codex websocket pool moved to post-port.
Merging: this branch shared no history with
mainpast upstream055d95bb7e, and a normal merge conflicted in 732 files.mainis now merged into this branch with-s ours, which keeps v1's history but takes the v2 tree, so the PR merges cleanly. CI now runs on GitHub-hosted runners formain, with macOS added to the unit and build jobs.How did you verify your code works?
bun run check(typecheck for every package) passes on push.forge-releaseworkflow (it has never run), and a real update on macOS or Windows. The rewritten auto-approve e2e spec wasn't run, because Playwright browsers aren't installed locally.Screenshots / recordings
Covered in #60.
Checklist