Skip to content

Sync with upstream anomalyco/opencode (dev) - #9

Open
dannypaz wants to merge 87 commits into
devfrom
claude/amazing-goldberg-lqq5ul
Open

Sync with upstream anomalyco/opencode (dev)#9
dannypaz wants to merge 87 commits into
devfrom
claude/amazing-goldberg-lqq5ul

Conversation

@dannypaz

Copy link
Copy Markdown
Owner

Issue for this PR

N/A — scheduled upstream sync.

Type of change

  • Refactor / code improvement (merge/sync)

What does this PR do?

Merges anomalyco/opencode's dev branch (upstream) into this fork's dev branch, bringing in ~86 upstream commits while keeping every fork-specific change intact. No fork commits were dropped, rebased, or altered — this is a straight merge (git merge upstream/dev), so the fork's full commit history is preserved as-is and only new upstream work is layered on top.

Fork-specific features/removals preserved by this merge (verified untouched, see below):

  • Electron auto-updater removal
  • Sentry crash/error reporting removal (web + desktop)
  • OpenTelemetry removal + models.dev network fetch stripped
  • CLI self-upgrade / version-check mechanism removal
  • Session share feature removal (docs + code)
  • CI-only PostHog download stats script removal
  • Desktop netlog gated behind explicit opt-in
  • Single-tenant AWS Lambda MicroVMs control plane for dynamic cloud sessions
  • "Disable automatic PR checks and PR auto-labeling"

Merge conflicts

Exactly one textual conflict, in packages/app/src/components/titlebar.tsx. Upstream changed the title bar's right-side region to accept state={v2RightState()}, wiring it to a new "Update" pill (TitlebarUpdatePillState) tied to upstream's in-app update/auto-updater flow. This fork already deleted that entire auto-update subsystem, so v2RightState/TitlebarUpdatePillState don't exist here.

Resolution: kept this fork's version — <TitlebarV2Right /> (no props) plus the existing electronWindows() / data-tauri-decorum-tb handling. Taking upstream's line as-is would have reintroduced a reference to code this fork intentionally removed and broken the build. No fork behavior was changed to resolve this; the fork's simplified title bar is unchanged.

Architectural / hard-to-resolve issues worth flagging

  • Auto-update UI (titlebar) will keep diverging. Upstream is actively building out update-notification UI (TitlebarUpdatePillState, v2RightState) on top of its auto-updater, which this fork removed. Every future upstream sync touching titlebar.tsx's right-hand region is likely to re-trigger this same conflict. There's no code action needed now, but it's worth deciding whether to permanently fork this component or periodically re-evaluate whether to re-adopt update UI (without the actual updater) as upstream evolves it.
  • Everything else auto-merged cleanly — no other fork removals (Sentry/OTel/PostHog/self-upgrade/session-share/Electron-updater) were touched or reintroduced by this sync; verified by grepping the merged tree for their identifying strings post-merge.
  • bun install in this sandbox failed fetching a GitHub-hosted dependency tarball (ghostty-web) with a 403, which is an environment/network-policy restriction unrelated to this merge — full bun install / typecheck / build could not be run here. Recommend running bun install && bun run typecheck locally or in CI before merging to be safe, since this PR could not be fully build-verified in this environment.

How did you verify your code works?

  • Confirmed all 17 fork-only commits (upstream/dev..dev) remain ancestors of the merge commit.
  • Grepped the fully-merged tree for sentry, opentelemetry, posthog, electron-updater/autoUpdater, session-share, and CLI self-upgrade identifiers to confirm none were reintroduced.
  • Confirmed no leftover conflict markers anywhere in the tree after resolution.
  • Could not run the project's build/typecheck/test suite in this sandbox (see note above under "Architectural issues").

Screenshots / recordings

N/A — no UI behavior change; the one hand-resolved conflict preserves the fork's existing title bar behavior exactly.

Checklist

  • I have not included unrelated changes in this PR (this is a pure merge from anomalyco/opencode's dev, plus one hand-resolved conflict)
  • I have tested my changes locally — could not run bun install/build in this sandbox (network-restricted); please verify CI is green before merging

Generated by Claude Code

arvsrn and others added 30 commits July 21, 2026 17:56
Co-authored-by: Luke Parker <10430890+Hona@users.noreply.github.com>
Co-authored-by: Luke Parker <10430890+Hona@users.noreply.github.com>
Co-authored-by: opencode <noreply@opencode.ai>
fwang and others added 29 commits July 24, 2026 14:15
Co-authored-by: Brendan Allan <14191578+Brendonovich@users.noreply.github.com>
Co-authored-by: Brendan Allan <git@brendonovich.dev>
Co-authored-by: Brendan Allan <git@brendonovich.dev>
Co-authored-by: Brendan Allan <git@brendonovich.dev>
Pulls in ~86 new commits from the upstream opencode project while
preserving all fork-specific changes (Electron auto-updater removal,
Sentry/OpenTelemetry/PostHog stripping, CLI self-upgrade removal,
session share feature removal, AWS Lambda MicroVMs cloud control
plane).

Resolved one conflict in packages/app/src/components/titlebar.tsx:
kept the fork's simplified TitlebarV2Right() (no props) instead of
upstream's TitlebarV2Right({state}) / v2RightState(), since that
upstream change wires the title bar to an "Update" pill tied to the
auto-update system this fork intentionally removed. Adopting it would
have reintroduced dead/broken references.

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01QUTEPXcSbvKqm7D79a7Bkc
@cursor

cursor Bot commented Jul 27, 2026

Copy link
Copy Markdown

Bugbot is not enabled for your account, so this pull request was not reviewed.

Enable Bugbot in the Cursor dashboard to get automatic reviews on future PRs.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.