feat(code): GitHub settings page + cloud-mode missing-integration warning

[VojtechBartos]

Problem

Two adjacent gaps in the personal-GitHub UX for cloud tasks:

• If a user has no personal GitHub integration, the cloud repo picker silently renders empty — no signal that anything is wrong, no path to fix it.
• There's no dedicated place to manage personal GitHub installations. Users can have multiple (different orgs/accounts), but settings doesn't surface them and offers no Disconnect.

Solution

• Cloud-mode warning — when workspace mode is "cloud" and the user has no personal GitHub integration, render an amber callout under the prompt input with a one-click Connect GitHub button (uses the existing useGithubUserConnect hook).
• GitHub settings page — new sidebar category that lists every linked personal GitHub installation, each with its own Disconnect confirmation. Single Connect / Connect-another-account button at the top.
• Cloud tasks still use the user's personal integration only — no team-integration fallback, so cloud PRs are always authored as the user.

Combines the spirit of #1989 and #2009 with adjustments: drop the team fallback, keep the warning, extend the settings page to handle multiple installations.

Test plan

• No personal GitHub: switch task input to Cloud → amber notice appears → Connect opens GitHub install URL.
• One installation: Settings → GitHub shows one row → Disconnect → row disappears, cloud notice reappears in task input.
• Multiple installations: Connect another account → two rows render → disconnect one leaves the other intact.
• Saga unchanged: cloud task creation still sends `github_user_integration`; signal-report tasks still send `github_integration`.

---

Created with PostHog Code

[greptile-apps]

Prompt To Fix All With AI

Fix the following 2 code review issues. Work through them one at a time, proposing concise fixes.

---

### Issue 1 of 2
apps/code/src/renderer/features/task-detail/components/CloudGithubMissingNotice.tsx:13-16
`timed-out` state silently swallowed — no feedback to the user

When a GitHub connection attempt times out after 5 minutes (`POLL_TIMEOUT_MS = 300_000`), `state` becomes `"timed-out"`, but neither `isConnecting` (`state === "connecting"`) nor `hasError` (`state === "error"`) covers this case. The component falls back to the default "Connect your personal GitHub…" message and an enabled button with no indication that anything went wrong. The same issue exists in `GitHubSettings.tsx` where neither `isConnecting` nor `hasConnectError` handles `timed-out`. Consider treating `"timed-out"` similarly to an error, mapping it to a descriptive message like "Connection timed out — please try again."

### Issue 2 of 2
apps/code/src/renderer/features/settings/components/sections/GitHubSettings.tsx:49-55
The local `openInBrowser` function is identical to the private `openUrlInBrowser` already defined in `useGithubUserConnect.ts`. Having two copies of the same try/catch-then-`window.open` pattern violates OnceAndOnlyOnce. Consider exporting `openUrlInBrowser` from the hook file (or a shared `browser.ts` utility) and importing it here.

```suggestion
// Import openUrlInBrowser from a shared utility instead of duplicating here
export async function openInBrowser(url: string) {
  try {
    await trpcClient.os.openExternal.mutate({ url });
  } catch {
    window.open(url, "_blank", "noopener,noreferrer");
  }
}
```

_{Reviews (1): Last reviewed commit: "feat(code): GitHub settings page and clo..." | Re-trigger Greptile}

[greptile-apps]

timed-out state silently swallowed — no feedback to the user

When a GitHub connection attempt times out after 5 minutes (POLL_TIMEOUT_MS = 300_000), state becomes "timed-out", but neither isConnecting (state === "connecting") nor hasError (state === "error") covers this case. The component falls back to the default "Connect your personal GitHub…" message and an enabled button with no indication that anything went wrong. The same issue exists in GitHubSettings.tsx where neither isConnecting nor hasConnectError handles timed-out. Consider treating "timed-out" similarly to an error, mapping it to a descriptive message like "Connection timed out — please try again."

Prompt To Fix With AI

This is a comment left during a code review.
Path: apps/code/src/renderer/features/task-detail/components/CloudGithubMissingNotice.tsx
Line: 13-16

Comment:
`timed-out` state silently swallowed — no feedback to the user

When a GitHub connection attempt times out after 5 minutes (`POLL_TIMEOUT_MS = 300_000`), `state` becomes `"timed-out"`, but neither `isConnecting` (`state === "connecting"`) nor `hasError` (`state === "error"`) covers this case. The component falls back to the default "Connect your personal GitHub…" message and an enabled button with no indication that anything went wrong. The same issue exists in `GitHubSettings.tsx` where neither `isConnecting` nor `hasConnectError` handles `timed-out`. Consider treating `"timed-out"` similarly to an error, mapping it to a descriptive message like "Connection timed out — please try again."

How can I resolve this? If you propose a fix, please make it concise.

[joshsny]

LGTM

[joshsny]

general question (out of the scope of this PR) - how do we handle integration selection when multiple integrations have access to a repo?

[VojtechBartos]

If 2 integrations expose same repo we pick whichever resolve first. Kinda good enough, but we could in future extend the picker and allow users choose which integration they would like to use

[joshsny]

we can probably drop "cloud PRs are authored as you" - since this is the default experience users would expect

[VojtechBartos]

Updated