fix(desktop): increase backend readiness timeout from 10s to 30s by rowalth · Pull Request #1979 · pingdotgg/t3code

rowalth · 2026-04-13T07:50:12Z

What Changed

DEFAULT_TIMEOUT_MS in apps/desktop/src/backendReadiness.ts from 10_000 to 30_000.

Why

The 10-second timeout is too tight for many machines. The backend consistently needs 10–12s to start (Node.js init → SQLite → migrations → HTTP listen), so the desktop gives up before the backend is ready — sometimes by less than a second.

Log evidence (v0.0.17, macOS x64):

Last successful start: 9.18s (0.82s under the limit)
Every cold start after that: 10.5–12s → timeout
Backend reaches Listening 0.35–2s after the desktop gives up

30s gives comfortable headroom without affecting fast machines — the readiness check still polls every 100ms and resolves immediately when the backend responds.

Fixes#1916

Checklist

This PR is small and focused
I explained what changed and why
I included before/after screenshots for any UI changes
I included a video for animation/interaction changes

Note

Low Risk
Low risk: only adjusts a default timeout value for desktop backend readiness polling, with no logic or data-handling changes.

Overview
Increases the default backend readiness wait timeout in the desktop app from 10s to 30s, reducing startup failures on slower/cold machines while keeping the existing polling behavior unchanged.

^{Reviewed by Cursor Bugbot for commit e273835. Bugbot is set up for automated code reviews on this repo. Configure here.}

Note

Increase backend readiness timeout from 10s to 30s in desktop app

Raises DEFAULT_TIMEOUT_MS in backendReadiness.ts from 10,000ms to 30,000ms, giving the backend more time to become ready before timing out.

^{Macroscope summarized e273835.}

The 10-second timeout is too tight for many machines. Log analysis shows the backend consistently needs 10-12s to start (Node.js init + SQLite + migrations + HTTP server), causing the desktop to give up before the backend is ready. Reported by multiple users after upgrading to v0.0.17. Fixespingdotgg#1916

coderabbitai · 2026-04-13T07:50:20Z

Important

Review skipped

Auto reviews are disabled on this repository. Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: Repository UI

Review profile: CHILL

Plan: Pro

Run ID: 372a8bae-ab85-46ef-9c09-677cc86ac383

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

🔍 Trigger review

✨ Finishing Touches

🧪 Generate unit tests (beta)

Create PR with unit tests

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

macroscopeapp · 2026-04-13T07:51:10Z

Approvability

Verdict: Approved

Single-line change increasing a timeout constant from 10s to 30s. This is a simple, low-risk configuration tweak with no logic changes or side effects beyond allowing more time for backend readiness checks.

^{You can customize Macroscope's approvability policy. Learn more.}

juliusmarminge · 2026-04-13T08:08:08Z

also working on startup time improvements!

Integrates upstream/main (d22c6f5) into the fork while preserving all multi-provider support (codex, claudeAgent, copilot, cursor, opencode, geminiCli, amp, kilo) and fork UI/UX additions. Highlights adopted from upstream: - Nightly release channel + update channel selector (pingdotgg#2012, pingdotgg#2049, pingdotgg#1969) - Filesystem browse API + command palette project picker (pingdotgg#2024) - Launch Args setting for Claude provider (pingdotgg#1971) - Kiro editor support in open picker (pingdotgg#1974) - Claude plan events for TodoWrite during input streaming (pingdotgg#1541) - Lost provider session recovery (pingdotgg#1938) - Cache provider status and gate desktop startup (pingdotgg#1962) - LegendList migration for chat scrolling and branch lists (pingdotgg#1953) - Shell snapshot queries + backfill migration (pingdotgg#1973, pingdotgg#2004) - PATH hydration + fallback detection (pingdotgg#1799) - Warm sidebar thread subscriptions (pingdotgg#2001) - Full thread title tooltip (pingdotgg#1994) - Markdown file link UX (pingdotgg#1956), composer polish (pingdotgg#1944, pingdotgg#1992, pingdotgg#1985) - Worktree/branch state + draft reuse fixes (pingdotgg#2005, pingdotgg#2003, pingdotgg#1995, pingdotgg#1936) - Window controls overlay for Windows/Linux (pingdotgg#1969) - Backend readiness timeout 10s→30s (pingdotgg#1979) - Clear tracked RPCs on reconnect, live stream subscriptions (pingdotgg#2000, pingdotgg#1972) - Various misc fixes (pingdotgg#2051, pingdotgg#2052, pingdotgg#2025, pingdotgg#2027, pingdotgg#2049, pingdotgg#1997, pingdotgg#1975) Fork features preserved and reconciled: - All 8 provider adapters + conformance tests - Extended ProviderKind union across contracts/model/settings/provider - appearance/accentColor/themeConfig/ProviderLogo UI system - customModels + gitTextGeneration + providerModelOptions - Migration IDs 23 (NormalizeLegacyProviderKinds) and 24 (RepairProjectionThreadProposedPlanImplementationColumns) kept; new upstream migrations registered at IDs 25-26 to avoid breaking deployed fork databases - DesktopBridge: log directory channels (LOG_DIR/LIST/READ/OPEN_DIR) retained; getWsUrl replaced by upstream's getAppBranding - PROVIDER_CACHE_IDS extended to all 8 providers

…gdotgg#1979)

rowalth · 2026-04-13T07:50:12Z

What Changed

DEFAULT_TIMEOUT_MS in apps/desktop/src/backendReadiness.ts from 10_000 to 30_000.

Why

The 10-second timeout is too tight for many machines. The backend consistently needs 10–12s to start (Node.js init → SQLite → migrations → HTTP listen), so the desktop gives up before the backend is ready — sometimes by less than a second.

Log evidence (v0.0.17, macOS x64):

Last successful start: 9.18s (0.82s under the limit)
Every cold start after that: 10.5–12s → timeout
Backend reaches Listening 0.35–2s after the desktop gives up

30s gives comfortable headroom without affecting fast machines — the readiness check still polls every 100ms and resolves immediately when the backend responds.

Fixes#1916

Checklist

This PR is small and focused
I explained what changed and why
I included before/after screenshots for any UI changes
I included a video for animation/interaction changes

Note

Low Risk
Low risk: only adjusts a default timeout value for desktop backend readiness polling, with no logic or data-handling changes.

Overview
Increases the default backend readiness wait timeout in the desktop app from 10s to 30s, reducing startup failures on slower/cold machines while keeping the existing polling behavior unchanged.

^{Reviewed by Cursor Bugbot for commit e273835. Bugbot is set up for automated code reviews on this repo. Configure here.}

Note

Increase backend readiness timeout from 10s to 30s in desktop app

Raises DEFAULT_TIMEOUT_MS in backendReadiness.ts from 10,000ms to 30,000ms, giving the backend more time to become ready before timing out.

^{Macroscope summarized e273835.}

The 10-second timeout is too tight for many machines. Log analysis shows the backend consistently needs 10-12s to start (Node.js init + SQLite + migrations + HTTP server), causing the desktop to give up before the backend is ready. Reported by multiple users after upgrading to v0.0.17. Fixespingdotgg#1916

coderabbitai · 2026-04-13T07:50:20Z

Important

Review skipped

Auto reviews are disabled on this repository. Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: Repository UI

Review profile: CHILL

Plan: Pro

Run ID: 372a8bae-ab85-46ef-9c09-677cc86ac383

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

🔍 Trigger review

✨ Finishing Touches

🧪 Generate unit tests (beta)

Create PR with unit tests

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

macroscopeapp · 2026-04-13T07:51:10Z

Approvability

Verdict: Approved

Single-line change increasing a timeout constant from 10s to 30s. This is a simple, low-risk configuration tweak with no logic changes or side effects beyond allowing more time for backend readiness checks.

^{You can customize Macroscope's approvability policy. Learn more.}

juliusmarminge · 2026-04-13T08:08:08Z

also working on startup time improvements!

Integrates upstream/main (d22c6f5) into the fork while preserving all multi-provider support (codex, claudeAgent, copilot, cursor, opencode, geminiCli, amp, kilo) and fork UI/UX additions. Highlights adopted from upstream: - Nightly release channel + update channel selector (pingdotgg#2012, pingdotgg#2049, pingdotgg#1969) - Filesystem browse API + command palette project picker (pingdotgg#2024) - Launch Args setting for Claude provider (pingdotgg#1971) - Kiro editor support in open picker (pingdotgg#1974) - Claude plan events for TodoWrite during input streaming (pingdotgg#1541) - Lost provider session recovery (pingdotgg#1938) - Cache provider status and gate desktop startup (pingdotgg#1962) - LegendList migration for chat scrolling and branch lists (pingdotgg#1953) - Shell snapshot queries + backfill migration (pingdotgg#1973, pingdotgg#2004) - PATH hydration + fallback detection (pingdotgg#1799) - Warm sidebar thread subscriptions (pingdotgg#2001) - Full thread title tooltip (pingdotgg#1994) - Markdown file link UX (pingdotgg#1956), composer polish (pingdotgg#1944, pingdotgg#1992, pingdotgg#1985) - Worktree/branch state + draft reuse fixes (pingdotgg#2005, pingdotgg#2003, pingdotgg#1995, pingdotgg#1936) - Window controls overlay for Windows/Linux (pingdotgg#1969) - Backend readiness timeout 10s→30s (pingdotgg#1979) - Clear tracked RPCs on reconnect, live stream subscriptions (pingdotgg#2000, pingdotgg#1972) - Various misc fixes (pingdotgg#2051, pingdotgg#2052, pingdotgg#2025, pingdotgg#2027, pingdotgg#2049, pingdotgg#1997, pingdotgg#1975) Fork features preserved and reconciled: - All 8 provider adapters + conformance tests - Extended ProviderKind union across contracts/model/settings/provider - appearance/accentColor/themeConfig/ProviderLogo UI system - customModels + gitTextGeneration + providerModelOptions - Migration IDs 23 (NormalizeLegacyProviderKinds) and 24 (RepairProjectionThreadProposedPlanImplementationColumns) kept; new upstream migrations registered at IDs 25-26 to avoid breaking deployed fork databases - DesktopBridge: log directory channels (LOG_DIR/LIST/READ/OPEN_DIR) retained; getWsUrl replaced by upstream's getAppBranding - PROVIDER_CACHE_IDS extended to all 8 providers

…gdotgg#1979)

rowalth · 2026-04-13T07:50:12Z

What Changed

DEFAULT_TIMEOUT_MS in apps/desktop/src/backendReadiness.ts from 10_000 to 30_000.

Why

The 10-second timeout is too tight for many machines. The backend consistently needs 10–12s to start (Node.js init → SQLite → migrations → HTTP listen), so the desktop gives up before the backend is ready — sometimes by less than a second.

Log evidence (v0.0.17, macOS x64):

Last successful start: 9.18s (0.82s under the limit)
Every cold start after that: 10.5–12s → timeout
Backend reaches Listening 0.35–2s after the desktop gives up

30s gives comfortable headroom without affecting fast machines — the readiness check still polls every 100ms and resolves immediately when the backend responds.

Fixes#1916

Checklist

This PR is small and focused
I explained what changed and why
I included before/after screenshots for any UI changes
I included a video for animation/interaction changes

Note

Low Risk
Low risk: only adjusts a default timeout value for desktop backend readiness polling, with no logic or data-handling changes.

Overview
Increases the default backend readiness wait timeout in the desktop app from 10s to 30s, reducing startup failures on slower/cold machines while keeping the existing polling behavior unchanged.

^{Reviewed by Cursor Bugbot for commit e273835. Bugbot is set up for automated code reviews on this repo. Configure here.}

Note

Increase backend readiness timeout from 10s to 30s in desktop app

Raises DEFAULT_TIMEOUT_MS in backendReadiness.ts from 10,000ms to 30,000ms, giving the backend more time to become ready before timing out.

^{Macroscope summarized e273835.}

The 10-second timeout is too tight for many machines. Log analysis shows the backend consistently needs 10-12s to start (Node.js init + SQLite + migrations + HTTP server), causing the desktop to give up before the backend is ready. Reported by multiple users after upgrading to v0.0.17. Fixespingdotgg#1916

coderabbitai · 2026-04-13T07:50:20Z

Important

Review skipped

Auto reviews are disabled on this repository. Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: Repository UI

Review profile: CHILL

Plan: Pro

Run ID: 372a8bae-ab85-46ef-9c09-677cc86ac383

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

🔍 Trigger review

✨ Finishing Touches

🧪 Generate unit tests (beta)

Create PR with unit tests

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

macroscopeapp · 2026-04-13T07:51:10Z

Approvability

Verdict: Approved

Single-line change increasing a timeout constant from 10s to 30s. This is a simple, low-risk configuration tweak with no logic changes or side effects beyond allowing more time for backend readiness checks.

^{You can customize Macroscope's approvability policy. Learn more.}

juliusmarminge · 2026-04-13T08:08:08Z

also working on startup time improvements!

Integrates upstream/main (d22c6f5) into the fork while preserving all multi-provider support (codex, claudeAgent, copilot, cursor, opencode, geminiCli, amp, kilo) and fork UI/UX additions. Highlights adopted from upstream: - Nightly release channel + update channel selector (pingdotgg#2012, pingdotgg#2049, pingdotgg#1969) - Filesystem browse API + command palette project picker (pingdotgg#2024) - Launch Args setting for Claude provider (pingdotgg#1971) - Kiro editor support in open picker (pingdotgg#1974) - Claude plan events for TodoWrite during input streaming (pingdotgg#1541) - Lost provider session recovery (pingdotgg#1938) - Cache provider status and gate desktop startup (pingdotgg#1962) - LegendList migration for chat scrolling and branch lists (pingdotgg#1953) - Shell snapshot queries + backfill migration (pingdotgg#1973, pingdotgg#2004) - PATH hydration + fallback detection (pingdotgg#1799) - Warm sidebar thread subscriptions (pingdotgg#2001) - Full thread title tooltip (pingdotgg#1994) - Markdown file link UX (pingdotgg#1956), composer polish (pingdotgg#1944, pingdotgg#1992, pingdotgg#1985) - Worktree/branch state + draft reuse fixes (pingdotgg#2005, pingdotgg#2003, pingdotgg#1995, pingdotgg#1936) - Window controls overlay for Windows/Linux (pingdotgg#1969) - Backend readiness timeout 10s→30s (pingdotgg#1979) - Clear tracked RPCs on reconnect, live stream subscriptions (pingdotgg#2000, pingdotgg#1972) - Various misc fixes (pingdotgg#2051, pingdotgg#2052, pingdotgg#2025, pingdotgg#2027, pingdotgg#2049, pingdotgg#1997, pingdotgg#1975) Fork features preserved and reconciled: - All 8 provider adapters + conformance tests - Extended ProviderKind union across contracts/model/settings/provider - appearance/accentColor/themeConfig/ProviderLogo UI system - customModels + gitTextGeneration + providerModelOptions - Migration IDs 23 (NormalizeLegacyProviderKinds) and 24 (RepairProjectionThreadProposedPlanImplementationColumns) kept; new upstream migrations registered at IDs 25-26 to avoid breaking deployed fork databases - DesktopBridge: log directory channels (LOG_DIR/LIST/READ/OPEN_DIR) retained; getWsUrl replaced by upstream's getAppBranding - PROVIDER_CACHE_IDS extended to all 8 providers

…gdotgg#1979)

rowalth · 2026-04-13T07:50:12Z

What Changed

DEFAULT_TIMEOUT_MS in apps/desktop/src/backendReadiness.ts from 10_000 to 30_000.

Why

The 10-second timeout is too tight for many machines. The backend consistently needs 10–12s to start (Node.js init → SQLite → migrations → HTTP listen), so the desktop gives up before the backend is ready — sometimes by less than a second.

Log evidence (v0.0.17, macOS x64):

Last successful start: 9.18s (0.82s under the limit)
Every cold start after that: 10.5–12s → timeout
Backend reaches Listening 0.35–2s after the desktop gives up

30s gives comfortable headroom without affecting fast machines — the readiness check still polls every 100ms and resolves immediately when the backend responds.

Fixes#1916

Checklist

This PR is small and focused
I explained what changed and why
I included before/after screenshots for any UI changes
I included a video for animation/interaction changes

Note

Low Risk
Low risk: only adjusts a default timeout value for desktop backend readiness polling, with no logic or data-handling changes.

Overview
Increases the default backend readiness wait timeout in the desktop app from 10s to 30s, reducing startup failures on slower/cold machines while keeping the existing polling behavior unchanged.

^{Reviewed by Cursor Bugbot for commit e273835. Bugbot is set up for automated code reviews on this repo. Configure here.}

Note

Increase backend readiness timeout from 10s to 30s in desktop app

Raises DEFAULT_TIMEOUT_MS in backendReadiness.ts from 10,000ms to 30,000ms, giving the backend more time to become ready before timing out.

^{Macroscope summarized e273835.}

The 10-second timeout is too tight for many machines. Log analysis shows the backend consistently needs 10-12s to start (Node.js init + SQLite + migrations + HTTP server), causing the desktop to give up before the backend is ready. Reported by multiple users after upgrading to v0.0.17. Fixespingdotgg#1916

coderabbitai · 2026-04-13T07:50:20Z

Important

Review skipped

Auto reviews are disabled on this repository. Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: Repository UI

Review profile: CHILL

Plan: Pro

Run ID: 372a8bae-ab85-46ef-9c09-677cc86ac383

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

🔍 Trigger review

✨ Finishing Touches

🧪 Generate unit tests (beta)

Create PR with unit tests

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

macroscopeapp · 2026-04-13T07:51:10Z

Approvability

Verdict: Approved

Single-line change increasing a timeout constant from 10s to 30s. This is a simple, low-risk configuration tweak with no logic changes or side effects beyond allowing more time for backend readiness checks.

^{You can customize Macroscope's approvability policy. Learn more.}

juliusmarminge · 2026-04-13T08:08:08Z

also working on startup time improvements!

Integrates upstream/main (d22c6f5) into the fork while preserving all multi-provider support (codex, claudeAgent, copilot, cursor, opencode, geminiCli, amp, kilo) and fork UI/UX additions. Highlights adopted from upstream: - Nightly release channel + update channel selector (pingdotgg#2012, pingdotgg#2049, pingdotgg#1969) - Filesystem browse API + command palette project picker (pingdotgg#2024) - Launch Args setting for Claude provider (pingdotgg#1971) - Kiro editor support in open picker (pingdotgg#1974) - Claude plan events for TodoWrite during input streaming (pingdotgg#1541) - Lost provider session recovery (pingdotgg#1938) - Cache provider status and gate desktop startup (pingdotgg#1962) - LegendList migration for chat scrolling and branch lists (pingdotgg#1953) - Shell snapshot queries + backfill migration (pingdotgg#1973, pingdotgg#2004) - PATH hydration + fallback detection (pingdotgg#1799) - Warm sidebar thread subscriptions (pingdotgg#2001) - Full thread title tooltip (pingdotgg#1994) - Markdown file link UX (pingdotgg#1956), composer polish (pingdotgg#1944, pingdotgg#1992, pingdotgg#1985) - Worktree/branch state + draft reuse fixes (pingdotgg#2005, pingdotgg#2003, pingdotgg#1995, pingdotgg#1936) - Window controls overlay for Windows/Linux (pingdotgg#1969) - Backend readiness timeout 10s→30s (pingdotgg#1979) - Clear tracked RPCs on reconnect, live stream subscriptions (pingdotgg#2000, pingdotgg#1972) - Various misc fixes (pingdotgg#2051, pingdotgg#2052, pingdotgg#2025, pingdotgg#2027, pingdotgg#2049, pingdotgg#1997, pingdotgg#1975) Fork features preserved and reconciled: - All 8 provider adapters + conformance tests - Extended ProviderKind union across contracts/model/settings/provider - appearance/accentColor/themeConfig/ProviderLogo UI system - customModels + gitTextGeneration + providerModelOptions - Migration IDs 23 (NormalizeLegacyProviderKinds) and 24 (RepairProjectionThreadProposedPlanImplementationColumns) kept; new upstream migrations registered at IDs 25-26 to avoid breaking deployed fork databases - DesktopBridge: log directory channels (LOG_DIR/LIST/READ/OPEN_DIR) retained; getWsUrl replaced by upstream's getAppBranding - PROVIDER_CACHE_IDS extended to all 8 providers

…gdotgg#1979)

rowalth · 2026-04-13T07:50:12Z

What Changed

DEFAULT_TIMEOUT_MS in apps/desktop/src/backendReadiness.ts from 10_000 to 30_000.

Why

The 10-second timeout is too tight for many machines. The backend consistently needs 10–12s to start (Node.js init → SQLite → migrations → HTTP listen), so the desktop gives up before the backend is ready — sometimes by less than a second.

Log evidence (v0.0.17, macOS x64):

Last successful start: 9.18s (0.82s under the limit)
Every cold start after that: 10.5–12s → timeout
Backend reaches Listening 0.35–2s after the desktop gives up

30s gives comfortable headroom without affecting fast machines — the readiness check still polls every 100ms and resolves immediately when the backend responds.

Fixes#1916

Checklist

This PR is small and focused
I explained what changed and why
I included before/after screenshots for any UI changes
I included a video for animation/interaction changes

Note

Low Risk
Low risk: only adjusts a default timeout value for desktop backend readiness polling, with no logic or data-handling changes.

Overview
Increases the default backend readiness wait timeout in the desktop app from 10s to 30s, reducing startup failures on slower/cold machines while keeping the existing polling behavior unchanged.

^{Reviewed by Cursor Bugbot for commit e273835. Bugbot is set up for automated code reviews on this repo. Configure here.}

Note

Increase backend readiness timeout from 10s to 30s in desktop app

Raises DEFAULT_TIMEOUT_MS in backendReadiness.ts from 10,000ms to 30,000ms, giving the backend more time to become ready before timing out.

^{Macroscope summarized e273835.}

The 10-second timeout is too tight for many machines. Log analysis shows the backend consistently needs 10-12s to start (Node.js init + SQLite + migrations + HTTP server), causing the desktop to give up before the backend is ready. Reported by multiple users after upgrading to v0.0.17. Fixespingdotgg#1916

coderabbitai · 2026-04-13T07:50:20Z

Important

Review skipped

Auto reviews are disabled on this repository. Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: Repository UI

Review profile: CHILL

Plan: Pro

Run ID: 372a8bae-ab85-46ef-9c09-677cc86ac383

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

🔍 Trigger review

✨ Finishing Touches

🧪 Generate unit tests (beta)

Create PR with unit tests

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

macroscopeapp · 2026-04-13T07:51:10Z

Approvability

Verdict: Approved

Single-line change increasing a timeout constant from 10s to 30s. This is a simple, low-risk configuration tweak with no logic changes or side effects beyond allowing more time for backend readiness checks.

^{You can customize Macroscope's approvability policy. Learn more.}

juliusmarminge · 2026-04-13T08:08:08Z

also working on startup time improvements!

Integrates upstream/main (d22c6f5) into the fork while preserving all multi-provider support (codex, claudeAgent, copilot, cursor, opencode, geminiCli, amp, kilo) and fork UI/UX additions. Highlights adopted from upstream: - Nightly release channel + update channel selector (pingdotgg#2012, pingdotgg#2049, pingdotgg#1969) - Filesystem browse API + command palette project picker (pingdotgg#2024) - Launch Args setting for Claude provider (pingdotgg#1971) - Kiro editor support in open picker (pingdotgg#1974) - Claude plan events for TodoWrite during input streaming (pingdotgg#1541) - Lost provider session recovery (pingdotgg#1938) - Cache provider status and gate desktop startup (pingdotgg#1962) - LegendList migration for chat scrolling and branch lists (pingdotgg#1953) - Shell snapshot queries + backfill migration (pingdotgg#1973, pingdotgg#2004) - PATH hydration + fallback detection (pingdotgg#1799) - Warm sidebar thread subscriptions (pingdotgg#2001) - Full thread title tooltip (pingdotgg#1994) - Markdown file link UX (pingdotgg#1956), composer polish (pingdotgg#1944, pingdotgg#1992, pingdotgg#1985) - Worktree/branch state + draft reuse fixes (pingdotgg#2005, pingdotgg#2003, pingdotgg#1995, pingdotgg#1936) - Window controls overlay for Windows/Linux (pingdotgg#1969) - Backend readiness timeout 10s→30s (pingdotgg#1979) - Clear tracked RPCs on reconnect, live stream subscriptions (pingdotgg#2000, pingdotgg#1972) - Various misc fixes (pingdotgg#2051, pingdotgg#2052, pingdotgg#2025, pingdotgg#2027, pingdotgg#2049, pingdotgg#1997, pingdotgg#1975) Fork features preserved and reconciled: - All 8 provider adapters + conformance tests - Extended ProviderKind union across contracts/model/settings/provider - appearance/accentColor/themeConfig/ProviderLogo UI system - customModels + gitTextGeneration + providerModelOptions - Migration IDs 23 (NormalizeLegacyProviderKinds) and 24 (RepairProjectionThreadProposedPlanImplementationColumns) kept; new upstream migrations registered at IDs 25-26 to avoid breaking deployed fork databases - DesktopBridge: log directory channels (LOG_DIR/LIST/READ/OPEN_DIR) retained; getWsUrl replaced by upstream's getAppBranding - PROVIDER_CACHE_IDS extended to all 8 providers

…gdotgg#1979)

rowalth · 2026-04-13T07:50:12Z

What Changed

DEFAULT_TIMEOUT_MS in apps/desktop/src/backendReadiness.ts from 10_000 to 30_000.

Why

The 10-second timeout is too tight for many machines. The backend consistently needs 10–12s to start (Node.js init → SQLite → migrations → HTTP listen), so the desktop gives up before the backend is ready — sometimes by less than a second.

Log evidence (v0.0.17, macOS x64):

Last successful start: 9.18s (0.82s under the limit)
Every cold start after that: 10.5–12s → timeout
Backend reaches Listening 0.35–2s after the desktop gives up

30s gives comfortable headroom without affecting fast machines — the readiness check still polls every 100ms and resolves immediately when the backend responds.

Fixes#1916

Checklist

This PR is small and focused
I explained what changed and why
I included before/after screenshots for any UI changes
I included a video for animation/interaction changes

Note

Low Risk
Low risk: only adjusts a default timeout value for desktop backend readiness polling, with no logic or data-handling changes.

Overview
Increases the default backend readiness wait timeout in the desktop app from 10s to 30s, reducing startup failures on slower/cold machines while keeping the existing polling behavior unchanged.

^{Reviewed by Cursor Bugbot for commit e273835. Bugbot is set up for automated code reviews on this repo. Configure here.}

Note

Increase backend readiness timeout from 10s to 30s in desktop app

Raises DEFAULT_TIMEOUT_MS in backendReadiness.ts from 10,000ms to 30,000ms, giving the backend more time to become ready before timing out.

^{Macroscope summarized e273835.}

The 10-second timeout is too tight for many machines. Log analysis shows the backend consistently needs 10-12s to start (Node.js init + SQLite + migrations + HTTP server), causing the desktop to give up before the backend is ready. Reported by multiple users after upgrading to v0.0.17. Fixespingdotgg#1916

coderabbitai · 2026-04-13T07:50:20Z

Important

Review skipped

Auto reviews are disabled on this repository. Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: Repository UI

Review profile: CHILL

Plan: Pro

Run ID: 372a8bae-ab85-46ef-9c09-677cc86ac383

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

🔍 Trigger review

✨ Finishing Touches

🧪 Generate unit tests (beta)

Create PR with unit tests

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

macroscopeapp · 2026-04-13T07:51:10Z

Approvability

Verdict: Approved

Single-line change increasing a timeout constant from 10s to 30s. This is a simple, low-risk configuration tweak with no logic changes or side effects beyond allowing more time for backend readiness checks.

^{You can customize Macroscope's approvability policy. Learn more.}

juliusmarminge · 2026-04-13T08:08:08Z

also working on startup time improvements!

Integrates upstream/main (d22c6f5) into the fork while preserving all multi-provider support (codex, claudeAgent, copilot, cursor, opencode, geminiCli, amp, kilo) and fork UI/UX additions. Highlights adopted from upstream: - Nightly release channel + update channel selector (pingdotgg#2012, pingdotgg#2049, pingdotgg#1969) - Filesystem browse API + command palette project picker (pingdotgg#2024) - Launch Args setting for Claude provider (pingdotgg#1971) - Kiro editor support in open picker (pingdotgg#1974) - Claude plan events for TodoWrite during input streaming (pingdotgg#1541) - Lost provider session recovery (pingdotgg#1938) - Cache provider status and gate desktop startup (pingdotgg#1962) - LegendList migration for chat scrolling and branch lists (pingdotgg#1953) - Shell snapshot queries + backfill migration (pingdotgg#1973, pingdotgg#2004) - PATH hydration + fallback detection (pingdotgg#1799) - Warm sidebar thread subscriptions (pingdotgg#2001) - Full thread title tooltip (pingdotgg#1994) - Markdown file link UX (pingdotgg#1956), composer polish (pingdotgg#1944, pingdotgg#1992, pingdotgg#1985) - Worktree/branch state + draft reuse fixes (pingdotgg#2005, pingdotgg#2003, pingdotgg#1995, pingdotgg#1936) - Window controls overlay for Windows/Linux (pingdotgg#1969) - Backend readiness timeout 10s→30s (pingdotgg#1979) - Clear tracked RPCs on reconnect, live stream subscriptions (pingdotgg#2000, pingdotgg#1972) - Various misc fixes (pingdotgg#2051, pingdotgg#2052, pingdotgg#2025, pingdotgg#2027, pingdotgg#2049, pingdotgg#1997, pingdotgg#1975) Fork features preserved and reconciled: - All 8 provider adapters + conformance tests - Extended ProviderKind union across contracts/model/settings/provider - appearance/accentColor/themeConfig/ProviderLogo UI system - customModels + gitTextGeneration + providerModelOptions - Migration IDs 23 (NormalizeLegacyProviderKinds) and 24 (RepairProjectionThreadProposedPlanImplementationColumns) kept; new upstream migrations registered at IDs 25-26 to avoid breaking deployed fork databases - DesktopBridge: log directory channels (LOG_DIR/LIST/READ/OPEN_DIR) retained; getWsUrl replaced by upstream's getAppBranding - PROVIDER_CACHE_IDS extended to all 8 providers

…gdotgg#1979)

rowalth · 2026-04-13T07:50:12Z

What Changed

DEFAULT_TIMEOUT_MS in apps/desktop/src/backendReadiness.ts from 10_000 to 30_000.

Why

The 10-second timeout is too tight for many machines. The backend consistently needs 10–12s to start (Node.js init → SQLite → migrations → HTTP listen), so the desktop gives up before the backend is ready — sometimes by less than a second.

Log evidence (v0.0.17, macOS x64):

Last successful start: 9.18s (0.82s under the limit)
Every cold start after that: 10.5–12s → timeout
Backend reaches Listening 0.35–2s after the desktop gives up

30s gives comfortable headroom without affecting fast machines — the readiness check still polls every 100ms and resolves immediately when the backend responds.

Fixes#1916

Checklist

This PR is small and focused
I explained what changed and why
I included before/after screenshots for any UI changes
I included a video for animation/interaction changes

Note

Low Risk
Low risk: only adjusts a default timeout value for desktop backend readiness polling, with no logic or data-handling changes.

Overview
Increases the default backend readiness wait timeout in the desktop app from 10s to 30s, reducing startup failures on slower/cold machines while keeping the existing polling behavior unchanged.

^{Reviewed by Cursor Bugbot for commit e273835. Bugbot is set up for automated code reviews on this repo. Configure here.}

Note

Increase backend readiness timeout from 10s to 30s in desktop app

Raises DEFAULT_TIMEOUT_MS in backendReadiness.ts from 10,000ms to 30,000ms, giving the backend more time to become ready before timing out.

^{Macroscope summarized e273835.}

The 10-second timeout is too tight for many machines. Log analysis shows the backend consistently needs 10-12s to start (Node.js init + SQLite + migrations + HTTP server), causing the desktop to give up before the backend is ready. Reported by multiple users after upgrading to v0.0.17. Fixespingdotgg#1916

coderabbitai · 2026-04-13T07:50:20Z

Important

Review skipped

Auto reviews are disabled on this repository. Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: Repository UI

Review profile: CHILL

Plan: Pro

Run ID: 372a8bae-ab85-46ef-9c09-677cc86ac383

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

🔍 Trigger review

✨ Finishing Touches

🧪 Generate unit tests (beta)

Create PR with unit tests

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

macroscopeapp · 2026-04-13T07:51:10Z

Approvability

Verdict: Approved

Single-line change increasing a timeout constant from 10s to 30s. This is a simple, low-risk configuration tweak with no logic changes or side effects beyond allowing more time for backend readiness checks.

^{You can customize Macroscope's approvability policy. Learn more.}

juliusmarminge · 2026-04-13T08:08:08Z

also working on startup time improvements!

Integrates upstream/main (d22c6f5) into the fork while preserving all multi-provider support (codex, claudeAgent, copilot, cursor, opencode, geminiCli, amp, kilo) and fork UI/UX additions. Highlights adopted from upstream: - Nightly release channel + update channel selector (pingdotgg#2012, pingdotgg#2049, pingdotgg#1969) - Filesystem browse API + command palette project picker (pingdotgg#2024) - Launch Args setting for Claude provider (pingdotgg#1971) - Kiro editor support in open picker (pingdotgg#1974) - Claude plan events for TodoWrite during input streaming (pingdotgg#1541) - Lost provider session recovery (pingdotgg#1938) - Cache provider status and gate desktop startup (pingdotgg#1962) - LegendList migration for chat scrolling and branch lists (pingdotgg#1953) - Shell snapshot queries + backfill migration (pingdotgg#1973, pingdotgg#2004) - PATH hydration + fallback detection (pingdotgg#1799) - Warm sidebar thread subscriptions (pingdotgg#2001) - Full thread title tooltip (pingdotgg#1994) - Markdown file link UX (pingdotgg#1956), composer polish (pingdotgg#1944, pingdotgg#1992, pingdotgg#1985) - Worktree/branch state + draft reuse fixes (pingdotgg#2005, pingdotgg#2003, pingdotgg#1995, pingdotgg#1936) - Window controls overlay for Windows/Linux (pingdotgg#1969) - Backend readiness timeout 10s→30s (pingdotgg#1979) - Clear tracked RPCs on reconnect, live stream subscriptions (pingdotgg#2000, pingdotgg#1972) - Various misc fixes (pingdotgg#2051, pingdotgg#2052, pingdotgg#2025, pingdotgg#2027, pingdotgg#2049, pingdotgg#1997, pingdotgg#1975) Fork features preserved and reconciled: - All 8 provider adapters + conformance tests - Extended ProviderKind union across contracts/model/settings/provider - appearance/accentColor/themeConfig/ProviderLogo UI system - customModels + gitTextGeneration + providerModelOptions - Migration IDs 23 (NormalizeLegacyProviderKinds) and 24 (RepairProjectionThreadProposedPlanImplementationColumns) kept; new upstream migrations registered at IDs 25-26 to avoid breaking deployed fork databases - DesktopBridge: log directory channels (LOG_DIR/LIST/READ/OPEN_DIR) retained; getWsUrl replaced by upstream's getAppBranding - PROVIDER_CACHE_IDS extended to all 8 providers

…gdotgg#1979)

rowalth · 2026-04-13T07:50:12Z

What Changed

DEFAULT_TIMEOUT_MS in apps/desktop/src/backendReadiness.ts from 10_000 to 30_000.

Why

The 10-second timeout is too tight for many machines. The backend consistently needs 10–12s to start (Node.js init → SQLite → migrations → HTTP listen), so the desktop gives up before the backend is ready — sometimes by less than a second.

Log evidence (v0.0.17, macOS x64):

Last successful start: 9.18s (0.82s under the limit)
Every cold start after that: 10.5–12s → timeout
Backend reaches Listening 0.35–2s after the desktop gives up

30s gives comfortable headroom without affecting fast machines — the readiness check still polls every 100ms and resolves immediately when the backend responds.

Fixes#1916

Checklist

This PR is small and focused
I explained what changed and why
I included before/after screenshots for any UI changes
I included a video for animation/interaction changes

Note

Low Risk
Low risk: only adjusts a default timeout value for desktop backend readiness polling, with no logic or data-handling changes.

Overview
Increases the default backend readiness wait timeout in the desktop app from 10s to 30s, reducing startup failures on slower/cold machines while keeping the existing polling behavior unchanged.

^{Reviewed by Cursor Bugbot for commit e273835. Bugbot is set up for automated code reviews on this repo. Configure here.}

Note

Increase backend readiness timeout from 10s to 30s in desktop app

Raises DEFAULT_TIMEOUT_MS in backendReadiness.ts from 10,000ms to 30,000ms, giving the backend more time to become ready before timing out.

^{Macroscope summarized e273835.}

The 10-second timeout is too tight for many machines. Log analysis shows the backend consistently needs 10-12s to start (Node.js init + SQLite + migrations + HTTP server), causing the desktop to give up before the backend is ready. Reported by multiple users after upgrading to v0.0.17. Fixespingdotgg#1916

coderabbitai · 2026-04-13T07:50:20Z

Important

Review skipped

Auto reviews are disabled on this repository. Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: Repository UI

Review profile: CHILL

Plan: Pro

Run ID: 372a8bae-ab85-46ef-9c09-677cc86ac383

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

🔍 Trigger review

✨ Finishing Touches

🧪 Generate unit tests (beta)

Create PR with unit tests

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

macroscopeapp · 2026-04-13T07:51:10Z

Approvability

Verdict: Approved

Single-line change increasing a timeout constant from 10s to 30s. This is a simple, low-risk configuration tweak with no logic changes or side effects beyond allowing more time for backend readiness checks.

^{You can customize Macroscope's approvability policy. Learn more.}

juliusmarminge · 2026-04-13T08:08:08Z

also working on startup time improvements!

Integrates upstream/main (d22c6f5) into the fork while preserving all multi-provider support (codex, claudeAgent, copilot, cursor, opencode, geminiCli, amp, kilo) and fork UI/UX additions. Highlights adopted from upstream: - Nightly release channel + update channel selector (pingdotgg#2012, pingdotgg#2049, pingdotgg#1969) - Filesystem browse API + command palette project picker (pingdotgg#2024) - Launch Args setting for Claude provider (pingdotgg#1971) - Kiro editor support in open picker (pingdotgg#1974) - Claude plan events for TodoWrite during input streaming (pingdotgg#1541) - Lost provider session recovery (pingdotgg#1938) - Cache provider status and gate desktop startup (pingdotgg#1962) - LegendList migration for chat scrolling and branch lists (pingdotgg#1953) - Shell snapshot queries + backfill migration (pingdotgg#1973, pingdotgg#2004) - PATH hydration + fallback detection (pingdotgg#1799) - Warm sidebar thread subscriptions (pingdotgg#2001) - Full thread title tooltip (pingdotgg#1994) - Markdown file link UX (pingdotgg#1956), composer polish (pingdotgg#1944, pingdotgg#1992, pingdotgg#1985) - Worktree/branch state + draft reuse fixes (pingdotgg#2005, pingdotgg#2003, pingdotgg#1995, pingdotgg#1936) - Window controls overlay for Windows/Linux (pingdotgg#1969) - Backend readiness timeout 10s→30s (pingdotgg#1979) - Clear tracked RPCs on reconnect, live stream subscriptions (pingdotgg#2000, pingdotgg#1972) - Various misc fixes (pingdotgg#2051, pingdotgg#2052, pingdotgg#2025, pingdotgg#2027, pingdotgg#2049, pingdotgg#1997, pingdotgg#1975) Fork features preserved and reconciled: - All 8 provider adapters + conformance tests - Extended ProviderKind union across contracts/model/settings/provider - appearance/accentColor/themeConfig/ProviderLogo UI system - customModels + gitTextGeneration + providerModelOptions - Migration IDs 23 (NormalizeLegacyProviderKinds) and 24 (RepairProjectionThreadProposedPlanImplementationColumns) kept; new upstream migrations registered at IDs 25-26 to avoid breaking deployed fork databases - DesktopBridge: log directory channels (LOG_DIR/LIST/READ/OPEN_DIR) retained; getWsUrl replaced by upstream's getAppBranding - PROVIDER_CACHE_IDS extended to all 8 providers

…gdotgg#1979)

github-actionsBot added size:XS 0-9 changed lines (additions + deletions). vouch:unvouched PR author is not yet trusted in the VOUCHED list. labels Apr 13, 2026

macroscopeappBot approved these changes Apr 13, 2026
View reviewed changes

juliusmarminge approved these changes Apr 13, 2026
View reviewed changes

juliusmarminge enabled auto-merge (squash) April 13, 2026 08:07

juliusmarminge merged commit 850c912 into pingdotgg:mainApr 13, 2026
12 checks passed

juliusmarminge pushed a commit that referenced this pull request Apr 13, 2026
fix(desktop): increase backend readiness timeout from 10s to 30s (#1979)
8c4b15e

adammansfield mentioned this pull request Apr 14, 2026
[Bug]: Timed out waiting for backend readiness at http://127.0.0.1:3773. #1998
Closed
2 tasks

aaditagrawal mentioned this pull request Apr 16, 2026
sync: merge 35 upstream commits from pingdotgg/t3code aaditagrawal/t3code#69
Merged
9 tasks

mwolson mentioned this pull request Apr 20, 2026
[Bug]: ~2s cold start from decoding archived+deleted threads (linear) #2245
Closed
2 tasks

youpele52 referenced this pull request in youpele52/bigbud Jun 17, 2026
fix(desktop): increase backend readiness timeout from 10s to 30s (#1979)
8a868d4

carlospedreira mentioned this pull request Jul 29, 2026
fix(desktop): increase backend readiness timeout to 3 minutes #4825
Closed

NeilTheFisher pushed a commit to NeilTheFisher/t3code that referenced this pull request Aug 18, 2026
fix(desktop): increase backend readiness timeout from 10s to 30s (pin…
e3783aa
…gdotgg#1979)