GitDesktop v0.3.0

Added

• AI generation can now run through your agent CLI. Commit messages, PR
  descriptions, branch names, issue drafts, release notes, and repo descriptions
  can be generated by an installed agent CLI — Claude Code, Codex, GitHub
  Copilot, or opencode — using its own subscription login, no API key needed.
  Pick a CLI as your AI provider in Settings → AI. Generation stays
  prompt-only (the agent never explores the repo), and because it runs the CLI
  per request it's slower than an HTTP provider and draws on your plan's quota.
• Code TODOs tab. Scan your working tree for TODO, FIXME, HACK, BUG, and
  XXX comment markers (tracked and new-but-not-ignored files), grouped by file and
  filterable by text, path, or marker. Select one for a syntax-highlighted excerpt with
  blame attribution, then open it in your editor, copy its path:line, or promote it to a
  local issue (pre-filled with the comment and a path:line reference) that you can publish
  to GitHub or Jira.
• Fork · Upstream lens for GitHub forks. On a fork (a repo with an
  upstream remote), the Pull Requests and Issues tabs gain a
  Fork | Upstream switcher in the list toolbar — remembered per repo,
  defaulting to your fork. Switch to Upstream and the remote list, detail
  views, comments, reactions, and metadata pickers all read and write the
  parent repository (your local to-dos and Jira issues are untouched).
  Creating an issue under the Upstream lens opens it on the parent, with the
  dialog saying so plainly. Two palette commands, Switch to fork view and
  Switch to upstream view, flip the lens without the mouse. A fork with
  issues turned off now offers a one-click Switch to upstream to browse the
  parent's issues instead of a dead end.

Changed

• Large diffs in TextMate-highlighted languages (Rust, TSX, Astro, Svelte, and
  other Shiki-rendered or custom-grammar languages) no longer lose their
  VSCode-fidelity highlighting past the size budget in commit, history, and
  pull-request diffs — they now tokenize in a background thread and fill in when
  ready, with standard highlighting shown in the interim.
• Opening a pull request now targets a repository explicitly. On a fork the
  create dialog lets you choose where the PR lands — your fork or the
  upstream repository (defaulting to upstream), listing the chosen
  repository's base branches; previously the target was left to gh's implicit
  resolution. Labels and assignees aren't available when you open the PR on the
  upstream repository. Targeting the upstream repository requires an upstream
  remote; on a fork cloned without one, the create dialog now offers to add it.

Fixed

• Fixed over-eager AI label suggestions in generated PR descriptions. The AI
  PR-description generator now weighs each label's stated purpose (its description),
  not just its name, and follows a conservative policy: for most changes the right
  outcome is one label or none. It no longer pushes rare process labels — changelog
  or release controls, triage states, and dependency-bot ecosystem labels (a
  language or tooling name a bot applies to dependency bumps) — onto ordinary code
  changes, suggesting them only when the change is precisely that case.
• On a GitHub fork, the app now consistently targets your fork instead of the
  parent repository. Previously the GitHub CLI's own auto-resolution preferred the
  upstream repo, so PR and issue surfaces (lists, detail views, comments, reviews,
  merges, labels, assignees, milestones, stars, reactions) and the PR-notification
  poller could silently act on the parent's data. They now all pin to the fork's
  own origin. This also covers the History tab: commit diffs and commit comments
  resolve against your fork, and a new commit comment is posted to your fork rather
  than the parent. Forks with issues turned off (GitHub's default for new forks) now
  show an informative "issues are disabled" notice instead of a failing retry.
  Repositories without an upstream remote are unaffected — the behavior there is
  identical to before.
• Fixed private-repo Fetch/Pull/Push failing on a Finder-launched macOS app.
  When the app was launched from Finder or the Dock, network operations against a
  private HTTPS repo could fail with "Repository not found" because git's
  credential helper couldn't find gh/glab on the minimal launchd PATH, so the
  request went out unauthenticated. Fetch, pull, and push now inject the forge
  credential helper with a resolved absolute CLI path, so authentication is
  deterministic regardless of how the app was launched.