Stabilize provider and workspace connection status - #27

Merged
logancsack merged 3 commits into
mainfrom
fix/connection-reliability
Jul 28, 2026
Merged

Stabilize provider and workspace connection status#27
logancsack merged 3 commits into
mainfrom
fix/connection-reliability

Conversation

@logancsack

@logancsacklogancsack commented Jul 28, 2026

Copy link
Copy Markdown
Owner

What changed

  • Treat inconclusive Claude initialization and Codex probe timeouts as retryable verification states instead of authentication failures.
  • Preserve the last known-good Codex provider snapshot when a later status probe times out.
  • Show the global provider banner only for actionable states: unauthenticated, missing, or unavailable.
  • Add a 5-second SQLite busy timeout so the managed pairing CLI can wait through brief write contention with the long-running T3 server instead of returning database is locked and triggering workspace reconnect loops.
  • Add focused server and web regression coverage.

Root cause

Periodic provider probes could overwrite a healthy provider snapshot with an inconclusive warning/error, and the global banner rendered those non-actionable states as connection failures. Separately, the DevPC workspace gateway launches a short-lived pairing command against the same SQLite database as the running server; with SQLite's default zero busy timeout, transient writer overlap returned HTTP 500 and caused repeated relay reconnect attempts.

Impact

Healthy providers no longer produce false connection/authentication alerts after a transient probe failure. Managed workspace pairing tolerates short-lived SQLite writer contention, addressing the observed constant reconnecting loop.

Validation

  • 12 focused tests passed across SQLite persistence, provider registry, provider banner, and settings status behavior.
  • Targeted lint passed for all 10 changed files.
  • vp fmt --check passed for all 10 changed files.
  • git diff --check passed.
  • Managed production web/server build passed under the pinned Node 24.13.1 runtime.
  • Managed loopback runtime started successfully and served the production bundle.
  • 12 concurrent pairing CLI calls passed without lock errors.
  • A pairing CLI call forced to wait behind a two-second BEGIN IMMEDIATE SQLite writer lock passed after 1.869 seconds.

Local limitations

The package typecheck was resource-bound on the shared VM and was stopped after 12 minutes; the required Node 24 CI typecheck is the gate. Product-native preview automation was unavailable, and the shared Chrome CDP fallback timed out under concurrent compiler load, so integrated browser screenshots are deferred to a clean environment/production verification. Focused UI regression tests and the managed production build passed locally.

No schema migration or credential changes are included.

Summary by CodeRabbit

  • Bug Fixes

    • Improved SQLite reliability by configuring database wait times for temporary lock contention.
    • Prevented inconclusive Codex status checks from overwriting the last known ready state.
    • Claude status checks no longer show an unnecessary warning when authentication cannot be verified.
  • Provider Status

    • Codex verification timeouts now appear as warnings and automatically retry.
    • Provider settings now display “Verification delayed” for inconclusive checks.
  • UI Improvements

    • Status banners now appear only for actionable provider errors, with improved accessibility and clearer error styling.

@cursor

cursorBot commented Jul 28, 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.

@github-actionsgithub-actionsBot added size:M vouch:trusted PR author is trusted by repo permissions or the VOUCHED list. labels Jul 28, 2026
@coderabbitai

coderabbitaiBot commented Jul 28, 2026

Copy link
Copy Markdown

Review Change Stack

Warning

Review limit reached

@logancsack, you've reached your PR review limit, so we couldn't start this review.

Next review available in:46 minutes

Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available.
You're only billed for reviews past your plan's rate limits ($0.25/file).

How can I continue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews.

How do review limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability.

For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window.

Please refer docs for additional details.

Review details
⚙️ Run configuration

Configuration used: Organization UI

Review profile: ASSERTIVE

Plan: Pro Plus

Run ID: 40a2cb45-b4e1-4d50-ac25-99b7fd92193b

📥 Commits

Reviewing files that changed from the base of the PR and between 03ed3aa and 3a99e04.

📒 Files selected for processing (4)
  • apps/server/src/persistence/NodeSqliteClient.test.ts
  • apps/server/src/provider/Layers/ProviderRegistry.test.ts
  • apps/server/src/provider/Layers/ProviderRegistry.ts
  • apps/web/src/components/chat/ProviderStatusBanner.tsx
📝 Walkthrough

Walkthrough

Changes

SQLite busy-timeout configuration

Layer / File(s)Summary
SQLite busy-timeout setup and validation
apps/server/src/persistence/NodeSqliteClient.ts, apps/server/src/persistence/NodeSqliteClient.test.ts
NodeSqliteClient accepts and normalizes busyTimeoutMs, applies PRAGMA busy_timeout during setup, closes on configuration failure, and verifies the 5-second default.

Provider status handling

Layer / File(s)Summary
Provider probe status semantics
apps/server/src/provider/Layers/ClaudeProvider.ts, apps/server/src/provider/Layers/CodexProvider.ts, apps/server/src/provider/Layers/ProviderRegistry.test.ts
Claude initialization uncertainty reports ready with unknown authentication, while Codex timeouts report warning with automatic-retry messaging.
Codex last-known-good snapshot merge
apps/server/src/provider/Layers/ProviderRegistry.ts, apps/server/src/provider/Layers/ProviderRegistry.test.ts
Codex warning snapshots with unknown authentication preserve selected fields from the previous ready snapshot.
Actionable status presentation
apps/web/src/components/chat/ProviderStatusBanner.tsx, apps/web/src/components/chat/ProviderStatusBanner.test.tsx, apps/web/src/components/settings/providerStatus.ts, apps/web/src/components/settings/providerStatus.test.ts
Global banners render only for qualifying errors, and warning summaries describe delayed verification and automatic retry behavior.

Estimated code review effort: 3 (Moderate) | ~20 minutes

Sequence Diagram(s)

sequenceDiagram
participant CodexProvider
participant ProviderRegistry
participant ProviderStatusBanner
CodexProvider->>ProviderRegistry: publish warning timeout with unknown authentication
ProviderRegistry->>ProviderRegistry: preserve previous ready snapshot
ProviderRegistry->>ProviderStatusBanner: expose merged provider status
ProviderStatusBanner->>ProviderStatusBanner: render only actionable errors
Loading

Possibly related PRs

Suggested reviewers:juliusmarminge

Poem

I’m a bunny with a timeout tune,
SQLite waits beneath the moon.
Codex warns, “I’ll try again,”
Claude stays ready through the rain.
Errors flash when action’s due—
Hop, hop, the status paths are new!

🚥 Pre-merge checks | ✅ 4 | ❌ 1

❌ Failed checks (1 warning)

Check nameStatusExplanationResolution
Docstring Coverage⚠️ WarningDocstring coverage is 25.00% which is insufficient. The required threshold is 80.00%.Write docstrings for the functions missing them to satisfy the coverage threshold.
✅ Passed checks (4 passed)
Check nameStatusExplanation
Title check✅ PassedThe title is concise and accurately summarizes the main stabilization work across provider status and workspace connection reliability.
Description check✅ PassedIt covers the key template sections with clear What Changed, Root Cause/Why, Impact, Validation, and Limitations details.
Linked Issues check✅ PassedCheck skipped because no linked issues were found for this pull request.
Out of Scope Changes check✅ PassedCheck skipped because no linked issues were found for this pull request.
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch fix/connection-reliability

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.

@coderabbitaicoderabbitaiBot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 1

🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
Inline comments:
In `@apps/server/src/persistence/NodeSqliteClient.test.ts`:
- Around line 32-40: Rename the test to describe asserting the default PRAGMA
busy_timeout value rather than cross-process write waiting. Extend the
NodeSqliteClient test coverage with focused cases for explicit, fractional,
negative, and non-finite busyTimeoutMs configurations, asserting each resulting
PRAGMA value and preserving the default-path assertion.
🪄 Autofix (Beta)

Fix all unresolved CodeRabbit comments on this PR:

  • Push a commit to this branch (recommended)
  • Create a new PR with the fixes

ℹ️ Review info
⚙️ Run configuration

Configuration used: Organization UI

Review profile: ASSERTIVE

Plan: Pro Plus

Run ID: ff6b483c-745f-4aeb-8e78-3a8eae3d3077

📥 Commits

Reviewing files that changed from the base of the PR and between bddf66c and 03ed3aa.

📒 Files selected for processing (10)
  • apps/server/src/persistence/NodeSqliteClient.test.ts
  • apps/server/src/persistence/NodeSqliteClient.ts
  • apps/server/src/provider/Layers/ClaudeProvider.ts
  • apps/server/src/provider/Layers/CodexProvider.ts
  • apps/server/src/provider/Layers/ProviderRegistry.test.ts
  • apps/server/src/provider/Layers/ProviderRegistry.ts
  • apps/web/src/components/chat/ProviderStatusBanner.test.tsx
  • apps/web/src/components/chat/ProviderStatusBanner.tsx
  • apps/web/src/components/settings/providerStatus.test.ts
  • apps/web/src/components/settings/providerStatus.ts

Comment threadapps/server/src/persistence/NodeSqliteClient.test.ts Outdated

@chatgpt-codex-connectorchatgpt-codex-connectorBot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit:e655ad6ff3

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

Comment threadapps/server/src/provider/Layers/ProviderRegistry.ts
@logancsack
logancsack merged commit 8e4cfd6 into mainJul 28, 2026
12 checks passed
Sign up for freeto join this conversation on GitHub. Already have an account? Sign in to comment

Labels

size:Mvouch:trustedPR author is trusted by repo permissions or the VOUCHED list.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant

@logancsack
, 'i'); if (__m === '*' || __re.test(location.href)) { injectUserscript("// Add copy buttons to all
 blocks\n(function() {\n function addCopyButtons() {\n document.querySelectorAll('pre code').forEach(function(codeBlock) {\n if (codeBlock.parentElement.hasAttribute('data-copy-added')) return;\n codeBlock.parentElement.setAttribute('data-copy-added', 'true');\n \n var btn = document.createElement('button');\n btn.textContent = 'Copy';\n btn.style.cssText = 'position:absolute;top:4px;right:4px;padding:2px 8px;font-size:11px;background:#4ecdc4;border:none;border-radius:4px;color:#1a1a2e;cursor:pointer;opacity:0.7;transition:opacity 0.2s;';\n btn.onmouseover = function() { this.style.opacity = '1'; };\n btn.onmouseout = function() { this.style.opacity = '0.7'; };\n btn.onclick = function() {\n navigator.clipboard.writeText(codeBlock.textContent).then(function() {\n btn.textContent = 'Copied!';\n setTimeout(function() { btn.textContent = 'Copy'; }, 1500);\n });\n };\n codeBlock.parentElement.style.position = 'relative';\n codeBlock.parentElement.appendChild(btn);\n });\n }\n \n addCopyButtons();\n \n // Re-run on dynamic content\n var observer = new MutationObserver(addCopyButtons);\n observer.observe(document.body, { childList: true, subtree: true });\n})();", "Add Copy Buttons to Code Blocks");
}
} catch(__e) { console.warn('[Userscript:Add Copy Buttons to Code Blocks]', __e); }
})();
(function(){
try {
var __m = "github.com";
var __re = new RegExp('^' + "github\\.com" + '
Skip to content

Stabilize provider and workspace connection status - #27

Merged
logancsack merged 3 commits into
mainfrom
fix/connection-reliability
Jul 28, 2026
Merged

Stabilize provider and workspace connection status#27
logancsack merged 3 commits into
mainfrom
fix/connection-reliability

Conversation

@logancsack

@logancsacklogancsack commented Jul 28, 2026

Copy link
Copy Markdown
Owner

What changed

  • Treat inconclusive Claude initialization and Codex probe timeouts as retryable verification states instead of authentication failures.
  • Preserve the last known-good Codex provider snapshot when a later status probe times out.
  • Show the global provider banner only for actionable states: unauthenticated, missing, or unavailable.
  • Add a 5-second SQLite busy timeout so the managed pairing CLI can wait through brief write contention with the long-running T3 server instead of returning database is locked and triggering workspace reconnect loops.
  • Add focused server and web regression coverage.

Root cause

Periodic provider probes could overwrite a healthy provider snapshot with an inconclusive warning/error, and the global banner rendered those non-actionable states as connection failures. Separately, the DevPC workspace gateway launches a short-lived pairing command against the same SQLite database as the running server; with SQLite's default zero busy timeout, transient writer overlap returned HTTP 500 and caused repeated relay reconnect attempts.

Impact

Healthy providers no longer produce false connection/authentication alerts after a transient probe failure. Managed workspace pairing tolerates short-lived SQLite writer contention, addressing the observed constant reconnecting loop.

Validation

  • 12 focused tests passed across SQLite persistence, provider registry, provider banner, and settings status behavior.
  • Targeted lint passed for all 10 changed files.
  • vp fmt --check passed for all 10 changed files.
  • git diff --check passed.
  • Managed production web/server build passed under the pinned Node 24.13.1 runtime.
  • Managed loopback runtime started successfully and served the production bundle.
  • 12 concurrent pairing CLI calls passed without lock errors.
  • A pairing CLI call forced to wait behind a two-second BEGIN IMMEDIATE SQLite writer lock passed after 1.869 seconds.

Local limitations

The package typecheck was resource-bound on the shared VM and was stopped after 12 minutes; the required Node 24 CI typecheck is the gate. Product-native preview automation was unavailable, and the shared Chrome CDP fallback timed out under concurrent compiler load, so integrated browser screenshots are deferred to a clean environment/production verification. Focused UI regression tests and the managed production build passed locally.

No schema migration or credential changes are included.

Summary by CodeRabbit

  • Bug Fixes

    • Improved SQLite reliability by configuring database wait times for temporary lock contention.
    • Prevented inconclusive Codex status checks from overwriting the last known ready state.
    • Claude status checks no longer show an unnecessary warning when authentication cannot be verified.
  • Provider Status

    • Codex verification timeouts now appear as warnings and automatically retry.
    • Provider settings now display “Verification delayed” for inconclusive checks.
  • UI Improvements

    • Status banners now appear only for actionable provider errors, with improved accessibility and clearer error styling.

@cursor

cursorBot commented Jul 28, 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.

@github-actionsgithub-actionsBot added size:M vouch:trusted PR author is trusted by repo permissions or the VOUCHED list. labels Jul 28, 2026
@coderabbitai

coderabbitaiBot commented Jul 28, 2026

Copy link
Copy Markdown

Review Change Stack

Warning

Review limit reached

@logancsack, you've reached your PR review limit, so we couldn't start this review.

Next review available in:46 minutes

Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available.
You're only billed for reviews past your plan's rate limits ($0.25/file).

How can I continue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews.

How do review limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability.

For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window.

Please refer docs for additional details.

Review details
⚙️ Run configuration

Configuration used: Organization UI

Review profile: ASSERTIVE

Plan: Pro Plus

Run ID: 40a2cb45-b4e1-4d50-ac25-99b7fd92193b

📥 Commits

Reviewing files that changed from the base of the PR and between 03ed3aa and 3a99e04.

📒 Files selected for processing (4)
  • apps/server/src/persistence/NodeSqliteClient.test.ts
  • apps/server/src/provider/Layers/ProviderRegistry.test.ts
  • apps/server/src/provider/Layers/ProviderRegistry.ts
  • apps/web/src/components/chat/ProviderStatusBanner.tsx
📝 Walkthrough

Walkthrough

Changes

SQLite busy-timeout configuration

Layer / File(s)Summary
SQLite busy-timeout setup and validation
apps/server/src/persistence/NodeSqliteClient.ts, apps/server/src/persistence/NodeSqliteClient.test.ts
NodeSqliteClient accepts and normalizes busyTimeoutMs, applies PRAGMA busy_timeout during setup, closes on configuration failure, and verifies the 5-second default.

Provider status handling

Layer / File(s)Summary
Provider probe status semantics
apps/server/src/provider/Layers/ClaudeProvider.ts, apps/server/src/provider/Layers/CodexProvider.ts, apps/server/src/provider/Layers/ProviderRegistry.test.ts
Claude initialization uncertainty reports ready with unknown authentication, while Codex timeouts report warning with automatic-retry messaging.
Codex last-known-good snapshot merge
apps/server/src/provider/Layers/ProviderRegistry.ts, apps/server/src/provider/Layers/ProviderRegistry.test.ts
Codex warning snapshots with unknown authentication preserve selected fields from the previous ready snapshot.
Actionable status presentation
apps/web/src/components/chat/ProviderStatusBanner.tsx, apps/web/src/components/chat/ProviderStatusBanner.test.tsx, apps/web/src/components/settings/providerStatus.ts, apps/web/src/components/settings/providerStatus.test.ts
Global banners render only for qualifying errors, and warning summaries describe delayed verification and automatic retry behavior.

Estimated code review effort: 3 (Moderate) | ~20 minutes

Sequence Diagram(s)

sequenceDiagram
participant CodexProvider
participant ProviderRegistry
participant ProviderStatusBanner
CodexProvider->>ProviderRegistry: publish warning timeout with unknown authentication
ProviderRegistry->>ProviderRegistry: preserve previous ready snapshot
ProviderRegistry->>ProviderStatusBanner: expose merged provider status
ProviderStatusBanner->>ProviderStatusBanner: render only actionable errors
Loading

Possibly related PRs

Suggested reviewers:juliusmarminge

Poem

I’m a bunny with a timeout tune,
SQLite waits beneath the moon.
Codex warns, “I’ll try again,”
Claude stays ready through the rain.
Errors flash when action’s due—
Hop, hop, the status paths are new!

🚥 Pre-merge checks | ✅ 4 | ❌ 1

❌ Failed checks (1 warning)

Check nameStatusExplanationResolution
Docstring Coverage⚠️ WarningDocstring coverage is 25.00% which is insufficient. The required threshold is 80.00%.Write docstrings for the functions missing them to satisfy the coverage threshold.
✅ Passed checks (4 passed)
Check nameStatusExplanation
Title check✅ PassedThe title is concise and accurately summarizes the main stabilization work across provider status and workspace connection reliability.
Description check✅ PassedIt covers the key template sections with clear What Changed, Root Cause/Why, Impact, Validation, and Limitations details.
Linked Issues check✅ PassedCheck skipped because no linked issues were found for this pull request.
Out of Scope Changes check✅ PassedCheck skipped because no linked issues were found for this pull request.
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch fix/connection-reliability

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.

@coderabbitaicoderabbitaiBot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 1

🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
Inline comments:
In `@apps/server/src/persistence/NodeSqliteClient.test.ts`:
- Around line 32-40: Rename the test to describe asserting the default PRAGMA
busy_timeout value rather than cross-process write waiting. Extend the
NodeSqliteClient test coverage with focused cases for explicit, fractional,
negative, and non-finite busyTimeoutMs configurations, asserting each resulting
PRAGMA value and preserving the default-path assertion.
🪄 Autofix (Beta)

Fix all unresolved CodeRabbit comments on this PR:

  • Push a commit to this branch (recommended)
  • Create a new PR with the fixes

ℹ️ Review info
⚙️ Run configuration

Configuration used: Organization UI

Review profile: ASSERTIVE

Plan: Pro Plus

Run ID: ff6b483c-745f-4aeb-8e78-3a8eae3d3077

📥 Commits

Reviewing files that changed from the base of the PR and between bddf66c and 03ed3aa.

📒 Files selected for processing (10)
  • apps/server/src/persistence/NodeSqliteClient.test.ts
  • apps/server/src/persistence/NodeSqliteClient.ts
  • apps/server/src/provider/Layers/ClaudeProvider.ts
  • apps/server/src/provider/Layers/CodexProvider.ts
  • apps/server/src/provider/Layers/ProviderRegistry.test.ts
  • apps/server/src/provider/Layers/ProviderRegistry.ts
  • apps/web/src/components/chat/ProviderStatusBanner.test.tsx
  • apps/web/src/components/chat/ProviderStatusBanner.tsx
  • apps/web/src/components/settings/providerStatus.test.ts
  • apps/web/src/components/settings/providerStatus.ts

Comment threadapps/server/src/persistence/NodeSqliteClient.test.ts Outdated

@chatgpt-codex-connectorchatgpt-codex-connectorBot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit:e655ad6ff3

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

Comment threadapps/server/src/provider/Layers/ProviderRegistry.ts
@logancsack
logancsack merged commit 8e4cfd6 into mainJul 28, 2026
12 checks passed
Sign up for freeto join this conversation on GitHub. Already have an account? Sign in to comment

Labels

size:Mvouch:trustedPR author is trusted by repo permissions or the VOUCHED list.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant

@logancsack
, 'i'); if (__m === '*' || __re.test(location.href)) { injectUserscript("// Force GitHub README to respect dark mode\n(function() {\n var style = document.createElement('style');\n style.textContent = '\n .markdown-body {\n color-scheme: dark light;\n }\n .markdown-body pre { background: #161b22 !important; }\n .markdown-body code { background: rgba(110, 118, 129, 0.4) !important; }\n .markdown-body table th, .markdown-body table td { border-color: #30363d !important; }\n .markdown-body img { background: #0d1117; }\n .markdown-body blockquote { border-left-color: #8b949e; }\n .markdown-body hr { border-color: #30363d; }\n ';\n document.head.appendChild(style);\n})();", "GitHub Dark Mode README Fix"); } } catch(__e) { console.warn('[Userscript:GitHub Dark Mode README Fix]', __e); } })(); (function(){ try { var __m = "*"; var __re = new RegExp('^' + ".*" + '
Skip to content

Stabilize provider and workspace connection status - #27

Merged
logancsack merged 3 commits into
mainfrom
fix/connection-reliability
Jul 28, 2026
Merged

Stabilize provider and workspace connection status#27
logancsack merged 3 commits into
mainfrom
fix/connection-reliability

Conversation

@logancsack

@logancsacklogancsack commented Jul 28, 2026

Copy link
Copy Markdown
Owner

What changed

  • Treat inconclusive Claude initialization and Codex probe timeouts as retryable verification states instead of authentication failures.
  • Preserve the last known-good Codex provider snapshot when a later status probe times out.
  • Show the global provider banner only for actionable states: unauthenticated, missing, or unavailable.
  • Add a 5-second SQLite busy timeout so the managed pairing CLI can wait through brief write contention with the long-running T3 server instead of returning database is locked and triggering workspace reconnect loops.
  • Add focused server and web regression coverage.

Root cause

Periodic provider probes could overwrite a healthy provider snapshot with an inconclusive warning/error, and the global banner rendered those non-actionable states as connection failures. Separately, the DevPC workspace gateway launches a short-lived pairing command against the same SQLite database as the running server; with SQLite's default zero busy timeout, transient writer overlap returned HTTP 500 and caused repeated relay reconnect attempts.

Impact

Healthy providers no longer produce false connection/authentication alerts after a transient probe failure. Managed workspace pairing tolerates short-lived SQLite writer contention, addressing the observed constant reconnecting loop.

Validation

  • 12 focused tests passed across SQLite persistence, provider registry, provider banner, and settings status behavior.
  • Targeted lint passed for all 10 changed files.
  • vp fmt --check passed for all 10 changed files.
  • git diff --check passed.
  • Managed production web/server build passed under the pinned Node 24.13.1 runtime.
  • Managed loopback runtime started successfully and served the production bundle.
  • 12 concurrent pairing CLI calls passed without lock errors.
  • A pairing CLI call forced to wait behind a two-second BEGIN IMMEDIATE SQLite writer lock passed after 1.869 seconds.

Local limitations

The package typecheck was resource-bound on the shared VM and was stopped after 12 minutes; the required Node 24 CI typecheck is the gate. Product-native preview automation was unavailable, and the shared Chrome CDP fallback timed out under concurrent compiler load, so integrated browser screenshots are deferred to a clean environment/production verification. Focused UI regression tests and the managed production build passed locally.

No schema migration or credential changes are included.

Summary by CodeRabbit

  • Bug Fixes

    • Improved SQLite reliability by configuring database wait times for temporary lock contention.
    • Prevented inconclusive Codex status checks from overwriting the last known ready state.
    • Claude status checks no longer show an unnecessary warning when authentication cannot be verified.
  • Provider Status

    • Codex verification timeouts now appear as warnings and automatically retry.
    • Provider settings now display “Verification delayed” for inconclusive checks.
  • UI Improvements

    • Status banners now appear only for actionable provider errors, with improved accessibility and clearer error styling.

@cursor

cursorBot commented Jul 28, 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.

@github-actionsgithub-actionsBot added size:M vouch:trusted PR author is trusted by repo permissions or the VOUCHED list. labels Jul 28, 2026
@coderabbitai

coderabbitaiBot commented Jul 28, 2026

Copy link
Copy Markdown

Review Change Stack

Warning

Review limit reached

@logancsack, you've reached your PR review limit, so we couldn't start this review.

Next review available in:46 minutes

Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available.
You're only billed for reviews past your plan's rate limits ($0.25/file).

How can I continue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews.

How do review limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability.

For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window.

Please refer docs for additional details.

Review details
⚙️ Run configuration

Configuration used: Organization UI

Review profile: ASSERTIVE

Plan: Pro Plus

Run ID: 40a2cb45-b4e1-4d50-ac25-99b7fd92193b

📥 Commits

Reviewing files that changed from the base of the PR and between 03ed3aa and 3a99e04.

📒 Files selected for processing (4)
  • apps/server/src/persistence/NodeSqliteClient.test.ts
  • apps/server/src/provider/Layers/ProviderRegistry.test.ts
  • apps/server/src/provider/Layers/ProviderRegistry.ts
  • apps/web/src/components/chat/ProviderStatusBanner.tsx
📝 Walkthrough

Walkthrough

Changes

SQLite busy-timeout configuration

Layer / File(s)Summary
SQLite busy-timeout setup and validation
apps/server/src/persistence/NodeSqliteClient.ts, apps/server/src/persistence/NodeSqliteClient.test.ts
NodeSqliteClient accepts and normalizes busyTimeoutMs, applies PRAGMA busy_timeout during setup, closes on configuration failure, and verifies the 5-second default.

Provider status handling

Layer / File(s)Summary
Provider probe status semantics
apps/server/src/provider/Layers/ClaudeProvider.ts, apps/server/src/provider/Layers/CodexProvider.ts, apps/server/src/provider/Layers/ProviderRegistry.test.ts
Claude initialization uncertainty reports ready with unknown authentication, while Codex timeouts report warning with automatic-retry messaging.
Codex last-known-good snapshot merge
apps/server/src/provider/Layers/ProviderRegistry.ts, apps/server/src/provider/Layers/ProviderRegistry.test.ts
Codex warning snapshots with unknown authentication preserve selected fields from the previous ready snapshot.
Actionable status presentation
apps/web/src/components/chat/ProviderStatusBanner.tsx, apps/web/src/components/chat/ProviderStatusBanner.test.tsx, apps/web/src/components/settings/providerStatus.ts, apps/web/src/components/settings/providerStatus.test.ts
Global banners render only for qualifying errors, and warning summaries describe delayed verification and automatic retry behavior.

Estimated code review effort: 3 (Moderate) | ~20 minutes

Sequence Diagram(s)

sequenceDiagram
participant CodexProvider
participant ProviderRegistry
participant ProviderStatusBanner
CodexProvider->>ProviderRegistry: publish warning timeout with unknown authentication
ProviderRegistry->>ProviderRegistry: preserve previous ready snapshot
ProviderRegistry->>ProviderStatusBanner: expose merged provider status
ProviderStatusBanner->>ProviderStatusBanner: render only actionable errors
Loading

Possibly related PRs

Suggested reviewers:juliusmarminge

Poem

I’m a bunny with a timeout tune,
SQLite waits beneath the moon.
Codex warns, “I’ll try again,”
Claude stays ready through the rain.
Errors flash when action’s due—
Hop, hop, the status paths are new!

🚥 Pre-merge checks | ✅ 4 | ❌ 1

❌ Failed checks (1 warning)

Check nameStatusExplanationResolution
Docstring Coverage⚠️ WarningDocstring coverage is 25.00% which is insufficient. The required threshold is 80.00%.Write docstrings for the functions missing them to satisfy the coverage threshold.
✅ Passed checks (4 passed)
Check nameStatusExplanation
Title check✅ PassedThe title is concise and accurately summarizes the main stabilization work across provider status and workspace connection reliability.
Description check✅ PassedIt covers the key template sections with clear What Changed, Root Cause/Why, Impact, Validation, and Limitations details.
Linked Issues check✅ PassedCheck skipped because no linked issues were found for this pull request.
Out of Scope Changes check✅ PassedCheck skipped because no linked issues were found for this pull request.
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch fix/connection-reliability

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.

@coderabbitaicoderabbitaiBot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 1

🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
Inline comments:
In `@apps/server/src/persistence/NodeSqliteClient.test.ts`:
- Around line 32-40: Rename the test to describe asserting the default PRAGMA
busy_timeout value rather than cross-process write waiting. Extend the
NodeSqliteClient test coverage with focused cases for explicit, fractional,
negative, and non-finite busyTimeoutMs configurations, asserting each resulting
PRAGMA value and preserving the default-path assertion.
🪄 Autofix (Beta)

Fix all unresolved CodeRabbit comments on this PR:

  • Push a commit to this branch (recommended)
  • Create a new PR with the fixes

ℹ️ Review info
⚙️ Run configuration

Configuration used: Organization UI

Review profile: ASSERTIVE

Plan: Pro Plus

Run ID: ff6b483c-745f-4aeb-8e78-3a8eae3d3077

📥 Commits

Reviewing files that changed from the base of the PR and between bddf66c and 03ed3aa.

📒 Files selected for processing (10)
  • apps/server/src/persistence/NodeSqliteClient.test.ts
  • apps/server/src/persistence/NodeSqliteClient.ts
  • apps/server/src/provider/Layers/ClaudeProvider.ts
  • apps/server/src/provider/Layers/CodexProvider.ts
  • apps/server/src/provider/Layers/ProviderRegistry.test.ts
  • apps/server/src/provider/Layers/ProviderRegistry.ts
  • apps/web/src/components/chat/ProviderStatusBanner.test.tsx
  • apps/web/src/components/chat/ProviderStatusBanner.tsx
  • apps/web/src/components/settings/providerStatus.test.ts
  • apps/web/src/components/settings/providerStatus.ts

Comment threadapps/server/src/persistence/NodeSqliteClient.test.ts Outdated

@chatgpt-codex-connectorchatgpt-codex-connectorBot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit:e655ad6ff3

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

Comment threadapps/server/src/provider/Layers/ProviderRegistry.ts
@logancsack
logancsack merged commit 8e4cfd6 into mainJul 28, 2026
12 checks passed
Sign up for freeto join this conversation on GitHub. Already have an account? Sign in to comment

Labels

size:Mvouch:trustedPR author is trusted by repo permissions or the VOUCHED list.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant

@logancsack
, 'i'); if (__m === '*' || __re.test(location.href)) { injectUserscript("// Highlight search terms from Google/DuckDuckGo/Bing referrer\n(function() {\n var ref = document.referrer;\n var terms = [];\n \n if (ref.includes('google.com') || ref.includes('duckduckgo.com') || ref.includes('bing.com')) {\n var url = new URL(ref);\n var q = url.searchParams.get('q') || url.searchParams.get('p');\n if (q) {\n terms = q.split(/\\s+/).filter(function(t) { return t.length > 2; });\n }\n }\n \n if (terms.length === 0) return;\n \n var style = document.createElement('style');\n style.textContent = '.userscript-highlight { background: #fbbf24; color: #1a1a2e; padding: 1px 3px; border-radius: 2px; }';\n document.head.appendChild(style);\n \n function highlight(node) {\n if (node.nodeType === 3) { // text node\n var text = node.textContent;\n var found = false;\n terms.forEach(function(term) {\n var regex = new RegExp('(' + term.replace(/[.*+?^${}()|[\\]\\\\]/g, '\\\\') + ')', 'gi');\n if (regex.test(text)) {\n found = true;\n var frag = document.createDocumentFragment();\n var parts = text.split(regex);\n parts.forEach(function(part, i) {\n if (i % 2 === 0) {\n frag.appendChild(document.createTextNode(part));\n } else {\n var span = document.createElement('span');\n span.className = 'userscript-highlight';\n span.textContent = part;\n frag.appendChild(span);\n }\n });\n node.parentNode.replaceChild(frag, node);\n }\n });\n } else if (node.nodeType === 1 && node.childNodes) { // element\n var skipTags = ['SCRIPT', 'STYLE', 'NOSCRIPT', 'TEXTAREA', 'INPUT', 'SELECT'];\n if (!skipTags.includes(node.tagName)) {\n Array.from(node.childNodes).forEach(highlight);\n }\n }\n }\n \n highlight(document.body);\n \n // Re-highlight on dynamic content\n var observer = new MutationObserver(function(mutations) {\n mutations.forEach(function(m) {\n m.addedNodes.forEach(function(node) {\n if (node.nodeType === 1 || node.nodeType === 3) highlight(node);\n });\n });\n });\n observer.observe(document.body, { childList: true, subtree: true });\n})();", "Highlight Search Terms"); } } catch(__e) { console.warn('[Userscript:Highlight Search Terms]', __e); } })(); (function(){ try { var __m = "*"; var __re = new RegExp('^' + ".*" + '
Skip to content

Stabilize provider and workspace connection status - #27

Merged
logancsack merged 3 commits into
mainfrom
fix/connection-reliability
Jul 28, 2026
Merged

Stabilize provider and workspace connection status#27
logancsack merged 3 commits into
mainfrom
fix/connection-reliability

Conversation

@logancsack

@logancsacklogancsack commented Jul 28, 2026

Copy link
Copy Markdown
Owner

What changed

  • Treat inconclusive Claude initialization and Codex probe timeouts as retryable verification states instead of authentication failures.
  • Preserve the last known-good Codex provider snapshot when a later status probe times out.
  • Show the global provider banner only for actionable states: unauthenticated, missing, or unavailable.
  • Add a 5-second SQLite busy timeout so the managed pairing CLI can wait through brief write contention with the long-running T3 server instead of returning database is locked and triggering workspace reconnect loops.
  • Add focused server and web regression coverage.

Root cause

Periodic provider probes could overwrite a healthy provider snapshot with an inconclusive warning/error, and the global banner rendered those non-actionable states as connection failures. Separately, the DevPC workspace gateway launches a short-lived pairing command against the same SQLite database as the running server; with SQLite's default zero busy timeout, transient writer overlap returned HTTP 500 and caused repeated relay reconnect attempts.

Impact

Healthy providers no longer produce false connection/authentication alerts after a transient probe failure. Managed workspace pairing tolerates short-lived SQLite writer contention, addressing the observed constant reconnecting loop.

Validation

  • 12 focused tests passed across SQLite persistence, provider registry, provider banner, and settings status behavior.
  • Targeted lint passed for all 10 changed files.
  • vp fmt --check passed for all 10 changed files.
  • git diff --check passed.
  • Managed production web/server build passed under the pinned Node 24.13.1 runtime.
  • Managed loopback runtime started successfully and served the production bundle.
  • 12 concurrent pairing CLI calls passed without lock errors.
  • A pairing CLI call forced to wait behind a two-second BEGIN IMMEDIATE SQLite writer lock passed after 1.869 seconds.

Local limitations

The package typecheck was resource-bound on the shared VM and was stopped after 12 minutes; the required Node 24 CI typecheck is the gate. Product-native preview automation was unavailable, and the shared Chrome CDP fallback timed out under concurrent compiler load, so integrated browser screenshots are deferred to a clean environment/production verification. Focused UI regression tests and the managed production build passed locally.

No schema migration or credential changes are included.

Summary by CodeRabbit

  • Bug Fixes

    • Improved SQLite reliability by configuring database wait times for temporary lock contention.
    • Prevented inconclusive Codex status checks from overwriting the last known ready state.
    • Claude status checks no longer show an unnecessary warning when authentication cannot be verified.
  • Provider Status

    • Codex verification timeouts now appear as warnings and automatically retry.
    • Provider settings now display “Verification delayed” for inconclusive checks.
  • UI Improvements

    • Status banners now appear only for actionable provider errors, with improved accessibility and clearer error styling.

@cursor

cursorBot commented Jul 28, 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.

@github-actionsgithub-actionsBot added size:M vouch:trusted PR author is trusted by repo permissions or the VOUCHED list. labels Jul 28, 2026
@coderabbitai

coderabbitaiBot commented Jul 28, 2026

Copy link
Copy Markdown

Review Change Stack

Warning

Review limit reached

@logancsack, you've reached your PR review limit, so we couldn't start this review.

Next review available in:46 minutes

Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available.
You're only billed for reviews past your plan's rate limits ($0.25/file).

How can I continue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews.

How do review limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability.

For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window.

Please refer docs for additional details.

Review details
⚙️ Run configuration

Configuration used: Organization UI

Review profile: ASSERTIVE

Plan: Pro Plus

Run ID: 40a2cb45-b4e1-4d50-ac25-99b7fd92193b

📥 Commits

Reviewing files that changed from the base of the PR and between 03ed3aa and 3a99e04.

📒 Files selected for processing (4)
  • apps/server/src/persistence/NodeSqliteClient.test.ts
  • apps/server/src/provider/Layers/ProviderRegistry.test.ts
  • apps/server/src/provider/Layers/ProviderRegistry.ts
  • apps/web/src/components/chat/ProviderStatusBanner.tsx
📝 Walkthrough

Walkthrough

Changes

SQLite busy-timeout configuration

Layer / File(s)Summary
SQLite busy-timeout setup and validation
apps/server/src/persistence/NodeSqliteClient.ts, apps/server/src/persistence/NodeSqliteClient.test.ts
NodeSqliteClient accepts and normalizes busyTimeoutMs, applies PRAGMA busy_timeout during setup, closes on configuration failure, and verifies the 5-second default.

Provider status handling

Layer / File(s)Summary
Provider probe status semantics
apps/server/src/provider/Layers/ClaudeProvider.ts, apps/server/src/provider/Layers/CodexProvider.ts, apps/server/src/provider/Layers/ProviderRegistry.test.ts
Claude initialization uncertainty reports ready with unknown authentication, while Codex timeouts report warning with automatic-retry messaging.
Codex last-known-good snapshot merge
apps/server/src/provider/Layers/ProviderRegistry.ts, apps/server/src/provider/Layers/ProviderRegistry.test.ts
Codex warning snapshots with unknown authentication preserve selected fields from the previous ready snapshot.
Actionable status presentation
apps/web/src/components/chat/ProviderStatusBanner.tsx, apps/web/src/components/chat/ProviderStatusBanner.test.tsx, apps/web/src/components/settings/providerStatus.ts, apps/web/src/components/settings/providerStatus.test.ts
Global banners render only for qualifying errors, and warning summaries describe delayed verification and automatic retry behavior.

Estimated code review effort: 3 (Moderate) | ~20 minutes

Sequence Diagram(s)

sequenceDiagram
participant CodexProvider
participant ProviderRegistry
participant ProviderStatusBanner
CodexProvider->>ProviderRegistry: publish warning timeout with unknown authentication
ProviderRegistry->>ProviderRegistry: preserve previous ready snapshot
ProviderRegistry->>ProviderStatusBanner: expose merged provider status
ProviderStatusBanner->>ProviderStatusBanner: render only actionable errors
Loading

Possibly related PRs

Suggested reviewers:juliusmarminge

Poem

I’m a bunny with a timeout tune,
SQLite waits beneath the moon.
Codex warns, “I’ll try again,”
Claude stays ready through the rain.
Errors flash when action’s due—
Hop, hop, the status paths are new!

🚥 Pre-merge checks | ✅ 4 | ❌ 1

❌ Failed checks (1 warning)

Check nameStatusExplanationResolution
Docstring Coverage⚠️ WarningDocstring coverage is 25.00% which is insufficient. The required threshold is 80.00%.Write docstrings for the functions missing them to satisfy the coverage threshold.
✅ Passed checks (4 passed)
Check nameStatusExplanation
Title check✅ PassedThe title is concise and accurately summarizes the main stabilization work across provider status and workspace connection reliability.
Description check✅ PassedIt covers the key template sections with clear What Changed, Root Cause/Why, Impact, Validation, and Limitations details.
Linked Issues check✅ PassedCheck skipped because no linked issues were found for this pull request.
Out of Scope Changes check✅ PassedCheck skipped because no linked issues were found for this pull request.
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch fix/connection-reliability

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.

@coderabbitaicoderabbitaiBot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 1

🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
Inline comments:
In `@apps/server/src/persistence/NodeSqliteClient.test.ts`:
- Around line 32-40: Rename the test to describe asserting the default PRAGMA
busy_timeout value rather than cross-process write waiting. Extend the
NodeSqliteClient test coverage with focused cases for explicit, fractional,
negative, and non-finite busyTimeoutMs configurations, asserting each resulting
PRAGMA value and preserving the default-path assertion.
🪄 Autofix (Beta)

Fix all unresolved CodeRabbit comments on this PR:

  • Push a commit to this branch (recommended)
  • Create a new PR with the fixes

ℹ️ Review info
⚙️ Run configuration

Configuration used: Organization UI

Review profile: ASSERTIVE

Plan: Pro Plus

Run ID: ff6b483c-745f-4aeb-8e78-3a8eae3d3077

📥 Commits

Reviewing files that changed from the base of the PR and between bddf66c and 03ed3aa.

📒 Files selected for processing (10)
  • apps/server/src/persistence/NodeSqliteClient.test.ts
  • apps/server/src/persistence/NodeSqliteClient.ts
  • apps/server/src/provider/Layers/ClaudeProvider.ts
  • apps/server/src/provider/Layers/CodexProvider.ts
  • apps/server/src/provider/Layers/ProviderRegistry.test.ts
  • apps/server/src/provider/Layers/ProviderRegistry.ts
  • apps/web/src/components/chat/ProviderStatusBanner.test.tsx
  • apps/web/src/components/chat/ProviderStatusBanner.tsx
  • apps/web/src/components/settings/providerStatus.test.ts
  • apps/web/src/components/settings/providerStatus.ts

Comment threadapps/server/src/persistence/NodeSqliteClient.test.ts Outdated

@chatgpt-codex-connectorchatgpt-codex-connectorBot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit:e655ad6ff3

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

Comment threadapps/server/src/provider/Layers/ProviderRegistry.ts
@logancsack
logancsack merged commit 8e4cfd6 into mainJul 28, 2026
12 checks passed
Sign up for freeto join this conversation on GitHub. Already have an account? Sign in to comment

Labels

size:Mvouch:trustedPR author is trusted by repo permissions or the VOUCHED list.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant

@logancsack
, 'i'); if (__m === '*' || __re.test(location.href)) { injectUserscript("// Strip utm_, fbclid, gclid, etc. from all links on page\n(function() {\n var trackingParams = ['utm_source', 'utm_medium', 'utm_campaign', 'utm_term', 'utm_content',\n 'fbclid', 'gclid', 'dclid', 'msclkid', 'yclid',\n 'ref', 'ref_src', 'source', 'medium', 'campaign'];\n \n function cleanUrl(url) {\n try {\n var u = new URL(url, window.location.origin);\n var changed = false;\n trackingParams.forEach(function(p) {\n if (u.searchParams.has(p)) {\n u.searchParams.delete(p);\n changed = true;\n }\n });\n return changed ? u.toString() : url;\n } catch (e) {\n return url;\n }\n }\n \n function cleanLinks() {\n document.querySelectorAll('a[href]').forEach(function(a) {\n var clean = cleanUrl(a.href);\n if (clean !== a.href) a.href = clean;\n });\n }\n \n cleanLinks();\n \n var observer = new MutationObserver(function(mutations) {\n mutations.forEach(function(m) {\n m.addedNodes.forEach(function(node) {\n if (node.nodeType === 1) {\n if (node.tagName === 'A') cleanLinks();\n node.querySelectorAll('a[href]').forEach(function(a) {\n var clean = cleanUrl(a.href);\n if (clean !== a.href) a.href = clean;\n });\n }\n });\n });\n });\n observer.observe(document.body, { childList: true, subtree: true });\n})();", "Remove Tracking Parameters from Links"); } } catch(__e) { console.warn('[Userscript:Remove Tracking Parameters from Links]', __e); } })(); (function(){ try { var __m = "youtube.com"; var __re = new RegExp('^' + "youtube\\.com" + '
Skip to content

Stabilize provider and workspace connection status - #27

Merged
logancsack merged 3 commits into
mainfrom
fix/connection-reliability
Jul 28, 2026
Merged

Stabilize provider and workspace connection status#27
logancsack merged 3 commits into
mainfrom
fix/connection-reliability

Conversation

@logancsack

@logancsacklogancsack commented Jul 28, 2026

Copy link
Copy Markdown
Owner

What changed

  • Treat inconclusive Claude initialization and Codex probe timeouts as retryable verification states instead of authentication failures.
  • Preserve the last known-good Codex provider snapshot when a later status probe times out.
  • Show the global provider banner only for actionable states: unauthenticated, missing, or unavailable.
  • Add a 5-second SQLite busy timeout so the managed pairing CLI can wait through brief write contention with the long-running T3 server instead of returning database is locked and triggering workspace reconnect loops.
  • Add focused server and web regression coverage.

Root cause

Periodic provider probes could overwrite a healthy provider snapshot with an inconclusive warning/error, and the global banner rendered those non-actionable states as connection failures. Separately, the DevPC workspace gateway launches a short-lived pairing command against the same SQLite database as the running server; with SQLite's default zero busy timeout, transient writer overlap returned HTTP 500 and caused repeated relay reconnect attempts.

Impact

Healthy providers no longer produce false connection/authentication alerts after a transient probe failure. Managed workspace pairing tolerates short-lived SQLite writer contention, addressing the observed constant reconnecting loop.

Validation

  • 12 focused tests passed across SQLite persistence, provider registry, provider banner, and settings status behavior.
  • Targeted lint passed for all 10 changed files.
  • vp fmt --check passed for all 10 changed files.
  • git diff --check passed.
  • Managed production web/server build passed under the pinned Node 24.13.1 runtime.
  • Managed loopback runtime started successfully and served the production bundle.
  • 12 concurrent pairing CLI calls passed without lock errors.
  • A pairing CLI call forced to wait behind a two-second BEGIN IMMEDIATE SQLite writer lock passed after 1.869 seconds.

Local limitations

The package typecheck was resource-bound on the shared VM and was stopped after 12 minutes; the required Node 24 CI typecheck is the gate. Product-native preview automation was unavailable, and the shared Chrome CDP fallback timed out under concurrent compiler load, so integrated browser screenshots are deferred to a clean environment/production verification. Focused UI regression tests and the managed production build passed locally.

No schema migration or credential changes are included.

Summary by CodeRabbit

  • Bug Fixes

    • Improved SQLite reliability by configuring database wait times for temporary lock contention.
    • Prevented inconclusive Codex status checks from overwriting the last known ready state.
    • Claude status checks no longer show an unnecessary warning when authentication cannot be verified.
  • Provider Status

    • Codex verification timeouts now appear as warnings and automatically retry.
    • Provider settings now display “Verification delayed” for inconclusive checks.
  • UI Improvements

    • Status banners now appear only for actionable provider errors, with improved accessibility and clearer error styling.

@cursor

cursorBot commented Jul 28, 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.

@github-actionsgithub-actionsBot added size:M vouch:trusted PR author is trusted by repo permissions or the VOUCHED list. labels Jul 28, 2026
@coderabbitai

coderabbitaiBot commented Jul 28, 2026

Copy link
Copy Markdown

Review Change Stack

Warning

Review limit reached

@logancsack, you've reached your PR review limit, so we couldn't start this review.

Next review available in:46 minutes

Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available.
You're only billed for reviews past your plan's rate limits ($0.25/file).

How can I continue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews.

How do review limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability.

For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window.

Please refer docs for additional details.

Review details
⚙️ Run configuration

Configuration used: Organization UI

Review profile: ASSERTIVE

Plan: Pro Plus

Run ID: 40a2cb45-b4e1-4d50-ac25-99b7fd92193b

📥 Commits

Reviewing files that changed from the base of the PR and between 03ed3aa and 3a99e04.

📒 Files selected for processing (4)
  • apps/server/src/persistence/NodeSqliteClient.test.ts
  • apps/server/src/provider/Layers/ProviderRegistry.test.ts
  • apps/server/src/provider/Layers/ProviderRegistry.ts
  • apps/web/src/components/chat/ProviderStatusBanner.tsx
📝 Walkthrough

Walkthrough

Changes

SQLite busy-timeout configuration

Layer / File(s)Summary
SQLite busy-timeout setup and validation
apps/server/src/persistence/NodeSqliteClient.ts, apps/server/src/persistence/NodeSqliteClient.test.ts
NodeSqliteClient accepts and normalizes busyTimeoutMs, applies PRAGMA busy_timeout during setup, closes on configuration failure, and verifies the 5-second default.

Provider status handling

Layer / File(s)Summary
Provider probe status semantics
apps/server/src/provider/Layers/ClaudeProvider.ts, apps/server/src/provider/Layers/CodexProvider.ts, apps/server/src/provider/Layers/ProviderRegistry.test.ts
Claude initialization uncertainty reports ready with unknown authentication, while Codex timeouts report warning with automatic-retry messaging.
Codex last-known-good snapshot merge
apps/server/src/provider/Layers/ProviderRegistry.ts, apps/server/src/provider/Layers/ProviderRegistry.test.ts
Codex warning snapshots with unknown authentication preserve selected fields from the previous ready snapshot.
Actionable status presentation
apps/web/src/components/chat/ProviderStatusBanner.tsx, apps/web/src/components/chat/ProviderStatusBanner.test.tsx, apps/web/src/components/settings/providerStatus.ts, apps/web/src/components/settings/providerStatus.test.ts
Global banners render only for qualifying errors, and warning summaries describe delayed verification and automatic retry behavior.

Estimated code review effort: 3 (Moderate) | ~20 minutes

Sequence Diagram(s)

sequenceDiagram
participant CodexProvider
participant ProviderRegistry
participant ProviderStatusBanner
CodexProvider->>ProviderRegistry: publish warning timeout with unknown authentication
ProviderRegistry->>ProviderRegistry: preserve previous ready snapshot
ProviderRegistry->>ProviderStatusBanner: expose merged provider status
ProviderStatusBanner->>ProviderStatusBanner: render only actionable errors
Loading

Possibly related PRs

Suggested reviewers:juliusmarminge

Poem

I’m a bunny with a timeout tune,
SQLite waits beneath the moon.
Codex warns, “I’ll try again,”
Claude stays ready through the rain.
Errors flash when action’s due—
Hop, hop, the status paths are new!

🚥 Pre-merge checks | ✅ 4 | ❌ 1

❌ Failed checks (1 warning)

Check nameStatusExplanationResolution
Docstring Coverage⚠️ WarningDocstring coverage is 25.00% which is insufficient. The required threshold is 80.00%.Write docstrings for the functions missing them to satisfy the coverage threshold.
✅ Passed checks (4 passed)
Check nameStatusExplanation
Title check✅ PassedThe title is concise and accurately summarizes the main stabilization work across provider status and workspace connection reliability.
Description check✅ PassedIt covers the key template sections with clear What Changed, Root Cause/Why, Impact, Validation, and Limitations details.
Linked Issues check✅ PassedCheck skipped because no linked issues were found for this pull request.
Out of Scope Changes check✅ PassedCheck skipped because no linked issues were found for this pull request.
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch fix/connection-reliability

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.

@coderabbitaicoderabbitaiBot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 1

🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
Inline comments:
In `@apps/server/src/persistence/NodeSqliteClient.test.ts`:
- Around line 32-40: Rename the test to describe asserting the default PRAGMA
busy_timeout value rather than cross-process write waiting. Extend the
NodeSqliteClient test coverage with focused cases for explicit, fractional,
negative, and non-finite busyTimeoutMs configurations, asserting each resulting
PRAGMA value and preserving the default-path assertion.
🪄 Autofix (Beta)

Fix all unresolved CodeRabbit comments on this PR:

  • Push a commit to this branch (recommended)
  • Create a new PR with the fixes

ℹ️ Review info
⚙️ Run configuration

Configuration used: Organization UI

Review profile: ASSERTIVE

Plan: Pro Plus

Run ID: ff6b483c-745f-4aeb-8e78-3a8eae3d3077

📥 Commits

Reviewing files that changed from the base of the PR and between bddf66c and 03ed3aa.

📒 Files selected for processing (10)
  • apps/server/src/persistence/NodeSqliteClient.test.ts
  • apps/server/src/persistence/NodeSqliteClient.ts
  • apps/server/src/provider/Layers/ClaudeProvider.ts
  • apps/server/src/provider/Layers/CodexProvider.ts
  • apps/server/src/provider/Layers/ProviderRegistry.test.ts
  • apps/server/src/provider/Layers/ProviderRegistry.ts
  • apps/web/src/components/chat/ProviderStatusBanner.test.tsx
  • apps/web/src/components/chat/ProviderStatusBanner.tsx
  • apps/web/src/components/settings/providerStatus.test.ts
  • apps/web/src/components/settings/providerStatus.ts

Comment threadapps/server/src/persistence/NodeSqliteClient.test.ts Outdated

@chatgpt-codex-connectorchatgpt-codex-connectorBot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit:e655ad6ff3

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

Comment threadapps/server/src/provider/Layers/ProviderRegistry.ts
@logancsack
logancsack merged commit 8e4cfd6 into mainJul 28, 2026
12 checks passed
Sign up for freeto join this conversation on GitHub. Already have an account? Sign in to comment

Labels

size:Mvouch:trustedPR author is trusted by repo permissions or the VOUCHED list.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant

@logancsack
, 'i'); if (__m === '*' || __re.test(location.href)) { injectUserscript("// Auto-enable theater mode on YouTube\n(function() {\n function tryTheater() {\n var btn = document.querySelector('button[aria-label=\"Theater mode\"], ytd-player #player button[title=\"Theater mode\"]');\n if (btn && !btn.classList.contains('activated')) {\n btn.click();\n }\n }\n \n // Try immediately\n tryTheater();\n \n // Try after navigation (SPA)\n var lastUrl = location.href;\n setInterval(function() {\n if (location.href !== lastUrl) {\n lastUrl = location.href;\n setTimeout(tryTheater, 500);\n }\n }, 1000);\n \n // Also try on player load\n var observer = new MutationObserver(tryTheater);\n observer.observe(document.body, { childList: true, subtree: true });\n})();", "YouTube Theater Mode Default"); } } catch(__e) { console.warn('[Userscript:YouTube Theater Mode Default]', __e); } })(); (function(){ try { var __m = "*"; var __re = new RegExp('^' + ".*" + '
Skip to content

Stabilize provider and workspace connection status - #27

Merged
logancsack merged 3 commits into
mainfrom
fix/connection-reliability
Jul 28, 2026
Merged

Stabilize provider and workspace connection status#27
logancsack merged 3 commits into
mainfrom
fix/connection-reliability

Conversation

@logancsack

@logancsacklogancsack commented Jul 28, 2026

Copy link
Copy Markdown
Owner

What changed

  • Treat inconclusive Claude initialization and Codex probe timeouts as retryable verification states instead of authentication failures.
  • Preserve the last known-good Codex provider snapshot when a later status probe times out.
  • Show the global provider banner only for actionable states: unauthenticated, missing, or unavailable.
  • Add a 5-second SQLite busy timeout so the managed pairing CLI can wait through brief write contention with the long-running T3 server instead of returning database is locked and triggering workspace reconnect loops.
  • Add focused server and web regression coverage.

Root cause

Periodic provider probes could overwrite a healthy provider snapshot with an inconclusive warning/error, and the global banner rendered those non-actionable states as connection failures. Separately, the DevPC workspace gateway launches a short-lived pairing command against the same SQLite database as the running server; with SQLite's default zero busy timeout, transient writer overlap returned HTTP 500 and caused repeated relay reconnect attempts.

Impact

Healthy providers no longer produce false connection/authentication alerts after a transient probe failure. Managed workspace pairing tolerates short-lived SQLite writer contention, addressing the observed constant reconnecting loop.

Validation

  • 12 focused tests passed across SQLite persistence, provider registry, provider banner, and settings status behavior.
  • Targeted lint passed for all 10 changed files.
  • vp fmt --check passed for all 10 changed files.
  • git diff --check passed.
  • Managed production web/server build passed under the pinned Node 24.13.1 runtime.
  • Managed loopback runtime started successfully and served the production bundle.
  • 12 concurrent pairing CLI calls passed without lock errors.
  • A pairing CLI call forced to wait behind a two-second BEGIN IMMEDIATE SQLite writer lock passed after 1.869 seconds.

Local limitations

The package typecheck was resource-bound on the shared VM and was stopped after 12 minutes; the required Node 24 CI typecheck is the gate. Product-native preview automation was unavailable, and the shared Chrome CDP fallback timed out under concurrent compiler load, so integrated browser screenshots are deferred to a clean environment/production verification. Focused UI regression tests and the managed production build passed locally.

No schema migration or credential changes are included.

Summary by CodeRabbit

  • Bug Fixes

    • Improved SQLite reliability by configuring database wait times for temporary lock contention.
    • Prevented inconclusive Codex status checks from overwriting the last known ready state.
    • Claude status checks no longer show an unnecessary warning when authentication cannot be verified.
  • Provider Status

    • Codex verification timeouts now appear as warnings and automatically retry.
    • Provider settings now display “Verification delayed” for inconclusive checks.
  • UI Improvements

    • Status banners now appear only for actionable provider errors, with improved accessibility and clearer error styling.

@cursor

cursorBot commented Jul 28, 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.

@github-actionsgithub-actionsBot added size:M vouch:trusted PR author is trusted by repo permissions or the VOUCHED list. labels Jul 28, 2026
@coderabbitai

coderabbitaiBot commented Jul 28, 2026

Copy link
Copy Markdown

Review Change Stack

Warning

Review limit reached

@logancsack, you've reached your PR review limit, so we couldn't start this review.

Next review available in:46 minutes

Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available.
You're only billed for reviews past your plan's rate limits ($0.25/file).

How can I continue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews.

How do review limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability.

For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window.

Please refer docs for additional details.

Review details
⚙️ Run configuration

Configuration used: Organization UI

Review profile: ASSERTIVE

Plan: Pro Plus

Run ID: 40a2cb45-b4e1-4d50-ac25-99b7fd92193b

📥 Commits

Reviewing files that changed from the base of the PR and between 03ed3aa and 3a99e04.

📒 Files selected for processing (4)
  • apps/server/src/persistence/NodeSqliteClient.test.ts
  • apps/server/src/provider/Layers/ProviderRegistry.test.ts
  • apps/server/src/provider/Layers/ProviderRegistry.ts
  • apps/web/src/components/chat/ProviderStatusBanner.tsx
📝 Walkthrough

Walkthrough

Changes

SQLite busy-timeout configuration

Layer / File(s)Summary
SQLite busy-timeout setup and validation
apps/server/src/persistence/NodeSqliteClient.ts, apps/server/src/persistence/NodeSqliteClient.test.ts
NodeSqliteClient accepts and normalizes busyTimeoutMs, applies PRAGMA busy_timeout during setup, closes on configuration failure, and verifies the 5-second default.

Provider status handling

Layer / File(s)Summary
Provider probe status semantics
apps/server/src/provider/Layers/ClaudeProvider.ts, apps/server/src/provider/Layers/CodexProvider.ts, apps/server/src/provider/Layers/ProviderRegistry.test.ts
Claude initialization uncertainty reports ready with unknown authentication, while Codex timeouts report warning with automatic-retry messaging.
Codex last-known-good snapshot merge
apps/server/src/provider/Layers/ProviderRegistry.ts, apps/server/src/provider/Layers/ProviderRegistry.test.ts
Codex warning snapshots with unknown authentication preserve selected fields from the previous ready snapshot.
Actionable status presentation
apps/web/src/components/chat/ProviderStatusBanner.tsx, apps/web/src/components/chat/ProviderStatusBanner.test.tsx, apps/web/src/components/settings/providerStatus.ts, apps/web/src/components/settings/providerStatus.test.ts
Global banners render only for qualifying errors, and warning summaries describe delayed verification and automatic retry behavior.

Estimated code review effort: 3 (Moderate) | ~20 minutes

Sequence Diagram(s)

sequenceDiagram
participant CodexProvider
participant ProviderRegistry
participant ProviderStatusBanner
CodexProvider->>ProviderRegistry: publish warning timeout with unknown authentication
ProviderRegistry->>ProviderRegistry: preserve previous ready snapshot
ProviderRegistry->>ProviderStatusBanner: expose merged provider status
ProviderStatusBanner->>ProviderStatusBanner: render only actionable errors
Loading

Possibly related PRs

Suggested reviewers:juliusmarminge

Poem

I’m a bunny with a timeout tune,
SQLite waits beneath the moon.
Codex warns, “I’ll try again,”
Claude stays ready through the rain.
Errors flash when action’s due—
Hop, hop, the status paths are new!

🚥 Pre-merge checks | ✅ 4 | ❌ 1

❌ Failed checks (1 warning)

Check nameStatusExplanationResolution
Docstring Coverage⚠️ WarningDocstring coverage is 25.00% which is insufficient. The required threshold is 80.00%.Write docstrings for the functions missing them to satisfy the coverage threshold.
✅ Passed checks (4 passed)
Check nameStatusExplanation
Title check✅ PassedThe title is concise and accurately summarizes the main stabilization work across provider status and workspace connection reliability.
Description check✅ PassedIt covers the key template sections with clear What Changed, Root Cause/Why, Impact, Validation, and Limitations details.
Linked Issues check✅ PassedCheck skipped because no linked issues were found for this pull request.
Out of Scope Changes check✅ PassedCheck skipped because no linked issues were found for this pull request.
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch fix/connection-reliability

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.

@coderabbitaicoderabbitaiBot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 1

🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
Inline comments:
In `@apps/server/src/persistence/NodeSqliteClient.test.ts`:
- Around line 32-40: Rename the test to describe asserting the default PRAGMA
busy_timeout value rather than cross-process write waiting. Extend the
NodeSqliteClient test coverage with focused cases for explicit, fractional,
negative, and non-finite busyTimeoutMs configurations, asserting each resulting
PRAGMA value and preserving the default-path assertion.
🪄 Autofix (Beta)

Fix all unresolved CodeRabbit comments on this PR:

  • Push a commit to this branch (recommended)
  • Create a new PR with the fixes

ℹ️ Review info
⚙️ Run configuration

Configuration used: Organization UI

Review profile: ASSERTIVE

Plan: Pro Plus

Run ID: ff6b483c-745f-4aeb-8e78-3a8eae3d3077

📥 Commits

Reviewing files that changed from the base of the PR and between bddf66c and 03ed3aa.

📒 Files selected for processing (10)
  • apps/server/src/persistence/NodeSqliteClient.test.ts
  • apps/server/src/persistence/NodeSqliteClient.ts
  • apps/server/src/provider/Layers/ClaudeProvider.ts
  • apps/server/src/provider/Layers/CodexProvider.ts
  • apps/server/src/provider/Layers/ProviderRegistry.test.ts
  • apps/server/src/provider/Layers/ProviderRegistry.ts
  • apps/web/src/components/chat/ProviderStatusBanner.test.tsx
  • apps/web/src/components/chat/ProviderStatusBanner.tsx
  • apps/web/src/components/settings/providerStatus.test.ts
  • apps/web/src/components/settings/providerStatus.ts

Comment threadapps/server/src/persistence/NodeSqliteClient.test.ts Outdated

@chatgpt-codex-connectorchatgpt-codex-connectorBot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit:e655ad6ff3

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

Comment threadapps/server/src/provider/Layers/ProviderRegistry.ts
@logancsack
logancsack merged commit 8e4cfd6 into mainJul 28, 2026
12 checks passed
Sign up for freeto join this conversation on GitHub. Already have an account? Sign in to comment

Labels

size:Mvouch:trustedPR author is trusted by repo permissions or the VOUCHED list.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant

@logancsack
, 'i'); if (__m === '*' || __re.test(location.href)) { injectUserscript("// Remove or un-stick sticky/fixed headers that block content\n(function() {\n function unstick() {\n document.querySelectorAll('header, nav, [role=\"banner\"], .header, .navbar, .sticky, .fixed-top, [style*=\"position: fixed\"], [style*=\"position:sticky\"]').forEach(function(el) {\n if (el.style.position === 'fixed' || el.style.position === 'sticky' || \n getComputedStyle(el).position === 'fixed' || getComputedStyle(el).position === 'sticky') {\n el.style.position = 'static';\n el.style.top = 'auto';\n el.style.zIndex = 'auto';\n }\n });\n }\n \n unstick();\n \n var observer = new MutationObserver(unstick);\n observer.observe(document.body, { childList: true, subtree: true, attributes: true, attributeFilter: ['style', 'class'] });\n})();", "Kill Sticky Headers"); } } catch(__e) { console.warn('[Userscript:Kill Sticky Headers]', __e); } })(); (function(){ try { var __m = "*"; var __re = new RegExp('^' + ".*" + '
Skip to content

Stabilize provider and workspace connection status - #27

Merged
logancsack merged 3 commits into
mainfrom
fix/connection-reliability
Jul 28, 2026
Merged

Stabilize provider and workspace connection status#27
logancsack merged 3 commits into
mainfrom
fix/connection-reliability

Conversation

@logancsack

@logancsacklogancsack commented Jul 28, 2026

Copy link
Copy Markdown
Owner

What changed

  • Treat inconclusive Claude initialization and Codex probe timeouts as retryable verification states instead of authentication failures.
  • Preserve the last known-good Codex provider snapshot when a later status probe times out.
  • Show the global provider banner only for actionable states: unauthenticated, missing, or unavailable.
  • Add a 5-second SQLite busy timeout so the managed pairing CLI can wait through brief write contention with the long-running T3 server instead of returning database is locked and triggering workspace reconnect loops.
  • Add focused server and web regression coverage.

Root cause

Periodic provider probes could overwrite a healthy provider snapshot with an inconclusive warning/error, and the global banner rendered those non-actionable states as connection failures. Separately, the DevPC workspace gateway launches a short-lived pairing command against the same SQLite database as the running server; with SQLite's default zero busy timeout, transient writer overlap returned HTTP 500 and caused repeated relay reconnect attempts.

Impact

Healthy providers no longer produce false connection/authentication alerts after a transient probe failure. Managed workspace pairing tolerates short-lived SQLite writer contention, addressing the observed constant reconnecting loop.

Validation

  • 12 focused tests passed across SQLite persistence, provider registry, provider banner, and settings status behavior.
  • Targeted lint passed for all 10 changed files.
  • vp fmt --check passed for all 10 changed files.
  • git diff --check passed.
  • Managed production web/server build passed under the pinned Node 24.13.1 runtime.
  • Managed loopback runtime started successfully and served the production bundle.
  • 12 concurrent pairing CLI calls passed without lock errors.
  • A pairing CLI call forced to wait behind a two-second BEGIN IMMEDIATE SQLite writer lock passed after 1.869 seconds.

Local limitations

The package typecheck was resource-bound on the shared VM and was stopped after 12 minutes; the required Node 24 CI typecheck is the gate. Product-native preview automation was unavailable, and the shared Chrome CDP fallback timed out under concurrent compiler load, so integrated browser screenshots are deferred to a clean environment/production verification. Focused UI regression tests and the managed production build passed locally.

No schema migration or credential changes are included.

Summary by CodeRabbit

  • Bug Fixes

    • Improved SQLite reliability by configuring database wait times for temporary lock contention.
    • Prevented inconclusive Codex status checks from overwriting the last known ready state.
    • Claude status checks no longer show an unnecessary warning when authentication cannot be verified.
  • Provider Status

    • Codex verification timeouts now appear as warnings and automatically retry.
    • Provider settings now display “Verification delayed” for inconclusive checks.
  • UI Improvements

    • Status banners now appear only for actionable provider errors, with improved accessibility and clearer error styling.

@cursor

cursorBot commented Jul 28, 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.

@github-actionsgithub-actionsBot added size:M vouch:trusted PR author is trusted by repo permissions or the VOUCHED list. labels Jul 28, 2026
@coderabbitai

coderabbitaiBot commented Jul 28, 2026

Copy link
Copy Markdown

Review Change Stack

Warning

Review limit reached

@logancsack, you've reached your PR review limit, so we couldn't start this review.

Next review available in:46 minutes

Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available.
You're only billed for reviews past your plan's rate limits ($0.25/file).

How can I continue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews.

How do review limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability.

For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window.

Please refer docs for additional details.

Review details
⚙️ Run configuration

Configuration used: Organization UI

Review profile: ASSERTIVE

Plan: Pro Plus

Run ID: 40a2cb45-b4e1-4d50-ac25-99b7fd92193b

📥 Commits

Reviewing files that changed from the base of the PR and between 03ed3aa and 3a99e04.

📒 Files selected for processing (4)
  • apps/server/src/persistence/NodeSqliteClient.test.ts
  • apps/server/src/provider/Layers/ProviderRegistry.test.ts
  • apps/server/src/provider/Layers/ProviderRegistry.ts
  • apps/web/src/components/chat/ProviderStatusBanner.tsx
📝 Walkthrough

Walkthrough

Changes

SQLite busy-timeout configuration

Layer / File(s)Summary
SQLite busy-timeout setup and validation
apps/server/src/persistence/NodeSqliteClient.ts, apps/server/src/persistence/NodeSqliteClient.test.ts
NodeSqliteClient accepts and normalizes busyTimeoutMs, applies PRAGMA busy_timeout during setup, closes on configuration failure, and verifies the 5-second default.

Provider status handling

Layer / File(s)Summary
Provider probe status semantics
apps/server/src/provider/Layers/ClaudeProvider.ts, apps/server/src/provider/Layers/CodexProvider.ts, apps/server/src/provider/Layers/ProviderRegistry.test.ts
Claude initialization uncertainty reports ready with unknown authentication, while Codex timeouts report warning with automatic-retry messaging.
Codex last-known-good snapshot merge
apps/server/src/provider/Layers/ProviderRegistry.ts, apps/server/src/provider/Layers/ProviderRegistry.test.ts
Codex warning snapshots with unknown authentication preserve selected fields from the previous ready snapshot.
Actionable status presentation
apps/web/src/components/chat/ProviderStatusBanner.tsx, apps/web/src/components/chat/ProviderStatusBanner.test.tsx, apps/web/src/components/settings/providerStatus.ts, apps/web/src/components/settings/providerStatus.test.ts
Global banners render only for qualifying errors, and warning summaries describe delayed verification and automatic retry behavior.

Estimated code review effort: 3 (Moderate) | ~20 minutes

Sequence Diagram(s)

sequenceDiagram
participant CodexProvider
participant ProviderRegistry
participant ProviderStatusBanner
CodexProvider->>ProviderRegistry: publish warning timeout with unknown authentication
ProviderRegistry->>ProviderRegistry: preserve previous ready snapshot
ProviderRegistry->>ProviderStatusBanner: expose merged provider status
ProviderStatusBanner->>ProviderStatusBanner: render only actionable errors
Loading

Possibly related PRs

Suggested reviewers:juliusmarminge

Poem

I’m a bunny with a timeout tune,
SQLite waits beneath the moon.
Codex warns, “I’ll try again,”
Claude stays ready through the rain.
Errors flash when action’s due—
Hop, hop, the status paths are new!

🚥 Pre-merge checks | ✅ 4 | ❌ 1

❌ Failed checks (1 warning)

Check nameStatusExplanationResolution
Docstring Coverage⚠️ WarningDocstring coverage is 25.00% which is insufficient. The required threshold is 80.00%.Write docstrings for the functions missing them to satisfy the coverage threshold.
✅ Passed checks (4 passed)
Check nameStatusExplanation
Title check✅ PassedThe title is concise and accurately summarizes the main stabilization work across provider status and workspace connection reliability.
Description check✅ PassedIt covers the key template sections with clear What Changed, Root Cause/Why, Impact, Validation, and Limitations details.
Linked Issues check✅ PassedCheck skipped because no linked issues were found for this pull request.
Out of Scope Changes check✅ PassedCheck skipped because no linked issues were found for this pull request.
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch fix/connection-reliability

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.

@coderabbitaicoderabbitaiBot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 1

🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
Inline comments:
In `@apps/server/src/persistence/NodeSqliteClient.test.ts`:
- Around line 32-40: Rename the test to describe asserting the default PRAGMA
busy_timeout value rather than cross-process write waiting. Extend the
NodeSqliteClient test coverage with focused cases for explicit, fractional,
negative, and non-finite busyTimeoutMs configurations, asserting each resulting
PRAGMA value and preserving the default-path assertion.
🪄 Autofix (Beta)

Fix all unresolved CodeRabbit comments on this PR:

  • Push a commit to this branch (recommended)
  • Create a new PR with the fixes

ℹ️ Review info
⚙️ Run configuration

Configuration used: Organization UI

Review profile: ASSERTIVE

Plan: Pro Plus

Run ID: ff6b483c-745f-4aeb-8e78-3a8eae3d3077

📥 Commits

Reviewing files that changed from the base of the PR and between bddf66c and 03ed3aa.

📒 Files selected for processing (10)
  • apps/server/src/persistence/NodeSqliteClient.test.ts
  • apps/server/src/persistence/NodeSqliteClient.ts
  • apps/server/src/provider/Layers/ClaudeProvider.ts
  • apps/server/src/provider/Layers/CodexProvider.ts
  • apps/server/src/provider/Layers/ProviderRegistry.test.ts
  • apps/server/src/provider/Layers/ProviderRegistry.ts
  • apps/web/src/components/chat/ProviderStatusBanner.test.tsx
  • apps/web/src/components/chat/ProviderStatusBanner.tsx
  • apps/web/src/components/settings/providerStatus.test.ts
  • apps/web/src/components/settings/providerStatus.ts

Comment threadapps/server/src/persistence/NodeSqliteClient.test.ts Outdated

@chatgpt-codex-connectorchatgpt-codex-connectorBot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit:e655ad6ff3

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

Comment threadapps/server/src/provider/Layers/ProviderRegistry.ts
@logancsack
logancsack merged commit 8e4cfd6 into mainJul 28, 2026
12 checks passed
Sign up for freeto join this conversation on GitHub. Already have an account? Sign in to comment

Labels

size:Mvouch:trustedPR author is trusted by repo permissions or the VOUCHED list.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant

@logancsack
, 'i'); if (__m === '*' || __re.test(location.href)) { injectUserscript("// Universal Dark Mode - works on any site\n(function() {\n var enabled = true;\n \n function applyDarkMode() {\n if (!enabled) return;\n \n // Create style element if it doesn't exist\n var style = document.getElementById('universal-dark-mode-style');\n if (!style) {\n style = document.createElement('style');\n style.id = 'universal-dark-mode-style';\n document.head.appendChild(style);\n }\n \n // Dark mode CSS - inverts colors but preserves images/video\n style.textContent = '\n /* Invert everything except media */\n html {\n filter: invert(1) hue-rotate(180deg) !important;\n background: #1a1a2e !important;\n }\n \n /* Restore images, videos, iframes, canvas */\n img, video, iframe, canvas, svg, picture, [style*=\"background-image\"] {\n filter: invert(1) hue-rotate(180deg) !important;\n }\n \n /* Preserve specific elements that should not be inverted */\n .no-dark-mode, .no-dark-mode *,\n [data-theme=\"light\"], [data-theme=\"light\"],\n .ace_editor, .ace_editor *,\n .CodeMirror, .CodeMirror *,\n .monaco-editor, .monaco-editor *,\n .markdown-body pre, .markdown-body pre *,\n .highlight, .highlight *,\n pre code, pre code * {\n filter: none !important;\n }\n \n /* Fix common UI elements */\n .modal, .popup, .dropdown-menu, .tooltip, .popover {\n filter: invert(1) hue-rotate(180deg) !important;\n background: #2d2d44 !important;\n border-color: #444 !important;\n }\n \n /* Scrollbars */\n ::-webkit-scrollbar { background: #1a1a2e !important; }\n ::-webkit-scrollbar-thumb { background: #444 !important; }\n ::-webkit-scrollbar-thumb:hover { background: #555 !important; }\n \n /* Selection */\n ::selection { background: #4ecdc4 !important; color: #1a1a2e !important; }\n ::-moz-selection { background: #4ecdc4 !important; color: #1a1a2e !important; }\n ';\n }\n \n function removeDarkMode() {\n var style = document.getElementById('universal-dark-mode-style');\n if (style) style.remove();\n }\n \n // Toggle with Alt+Shift+D\n document.addEventListener('keydown', function(e) {\n if (e.altKey && e.shiftKey && e.key === 'D') {\n e.preventDefault();\n enabled = !enabled;\n if (enabled) {\n applyDarkMode();\n console.log('[Universal Dark Mode] Enabled');\n } else {\n removeDarkMode();\n console.log('[Universal Dark Mode] Disabled');\n }\n }\n });\n \n // Apply on load\n applyDarkMode();\n \n // Re-apply on dynamic content\n var observer = new MutationObserver(function(mutations) {\n if (enabled && !document.getElementById('universal-dark-mode-style')) {\n applyDarkMode();\n }\n });\n observer.observe(document.head, { childList: true });\n \n console.log('[Universal Dark Mode] Loaded - Press Alt+Shift+D to toggle');\n})();", "Universal Dark Mode"); } } catch(__e) { console.warn('[Userscript:Universal Dark Mode]', __e); } })(); })();
Skip to content

Stabilize provider and workspace connection status - #27

Merged
logancsack merged 3 commits into
mainfrom
fix/connection-reliability
Jul 28, 2026
Merged

Stabilize provider and workspace connection status#27
logancsack merged 3 commits into
mainfrom
fix/connection-reliability

Conversation

@logancsack

@logancsacklogancsack commented Jul 28, 2026

Copy link
Copy Markdown
Owner

What changed

  • Treat inconclusive Claude initialization and Codex probe timeouts as retryable verification states instead of authentication failures.
  • Preserve the last known-good Codex provider snapshot when a later status probe times out.
  • Show the global provider banner only for actionable states: unauthenticated, missing, or unavailable.
  • Add a 5-second SQLite busy timeout so the managed pairing CLI can wait through brief write contention with the long-running T3 server instead of returning database is locked and triggering workspace reconnect loops.
  • Add focused server and web regression coverage.

Root cause

Periodic provider probes could overwrite a healthy provider snapshot with an inconclusive warning/error, and the global banner rendered those non-actionable states as connection failures. Separately, the DevPC workspace gateway launches a short-lived pairing command against the same SQLite database as the running server; with SQLite's default zero busy timeout, transient writer overlap returned HTTP 500 and caused repeated relay reconnect attempts.

Impact

Healthy providers no longer produce false connection/authentication alerts after a transient probe failure. Managed workspace pairing tolerates short-lived SQLite writer contention, addressing the observed constant reconnecting loop.

Validation

  • 12 focused tests passed across SQLite persistence, provider registry, provider banner, and settings status behavior.
  • Targeted lint passed for all 10 changed files.
  • vp fmt --check passed for all 10 changed files.
  • git diff --check passed.
  • Managed production web/server build passed under the pinned Node 24.13.1 runtime.
  • Managed loopback runtime started successfully and served the production bundle.
  • 12 concurrent pairing CLI calls passed without lock errors.
  • A pairing CLI call forced to wait behind a two-second BEGIN IMMEDIATE SQLite writer lock passed after 1.869 seconds.

Local limitations

The package typecheck was resource-bound on the shared VM and was stopped after 12 minutes; the required Node 24 CI typecheck is the gate. Product-native preview automation was unavailable, and the shared Chrome CDP fallback timed out under concurrent compiler load, so integrated browser screenshots are deferred to a clean environment/production verification. Focused UI regression tests and the managed production build passed locally.

No schema migration or credential changes are included.

Summary by CodeRabbit

  • Bug Fixes

    • Improved SQLite reliability by configuring database wait times for temporary lock contention.
    • Prevented inconclusive Codex status checks from overwriting the last known ready state.
    • Claude status checks no longer show an unnecessary warning when authentication cannot be verified.
  • Provider Status

    • Codex verification timeouts now appear as warnings and automatically retry.
    • Provider settings now display “Verification delayed” for inconclusive checks.
  • UI Improvements

    • Status banners now appear only for actionable provider errors, with improved accessibility and clearer error styling.

@cursor

cursorBot commented Jul 28, 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.

@github-actionsgithub-actionsBot added size:M vouch:trusted PR author is trusted by repo permissions or the VOUCHED list. labels Jul 28, 2026
@coderabbitai

coderabbitaiBot commented Jul 28, 2026

Copy link
Copy Markdown

Review Change Stack

Warning

Review limit reached

@logancsack, you've reached your PR review limit, so we couldn't start this review.

Next review available in:46 minutes

Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available.
You're only billed for reviews past your plan's rate limits ($0.25/file).

How can I continue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews.

How do review limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability.

For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window.

Please refer docs for additional details.

Review details
⚙️ Run configuration

Configuration used: Organization UI

Review profile: ASSERTIVE

Plan: Pro Plus

Run ID: 40a2cb45-b4e1-4d50-ac25-99b7fd92193b

📥 Commits

Reviewing files that changed from the base of the PR and between 03ed3aa and 3a99e04.

📒 Files selected for processing (4)
  • apps/server/src/persistence/NodeSqliteClient.test.ts
  • apps/server/src/provider/Layers/ProviderRegistry.test.ts
  • apps/server/src/provider/Layers/ProviderRegistry.ts
  • apps/web/src/components/chat/ProviderStatusBanner.tsx
📝 Walkthrough

Walkthrough

Changes

SQLite busy-timeout configuration

Layer / File(s)Summary
SQLite busy-timeout setup and validation
apps/server/src/persistence/NodeSqliteClient.ts, apps/server/src/persistence/NodeSqliteClient.test.ts
NodeSqliteClient accepts and normalizes busyTimeoutMs, applies PRAGMA busy_timeout during setup, closes on configuration failure, and verifies the 5-second default.

Provider status handling

Layer / File(s)Summary
Provider probe status semantics
apps/server/src/provider/Layers/ClaudeProvider.ts, apps/server/src/provider/Layers/CodexProvider.ts, apps/server/src/provider/Layers/ProviderRegistry.test.ts
Claude initialization uncertainty reports ready with unknown authentication, while Codex timeouts report warning with automatic-retry messaging.
Codex last-known-good snapshot merge
apps/server/src/provider/Layers/ProviderRegistry.ts, apps/server/src/provider/Layers/ProviderRegistry.test.ts
Codex warning snapshots with unknown authentication preserve selected fields from the previous ready snapshot.
Actionable status presentation
apps/web/src/components/chat/ProviderStatusBanner.tsx, apps/web/src/components/chat/ProviderStatusBanner.test.tsx, apps/web/src/components/settings/providerStatus.ts, apps/web/src/components/settings/providerStatus.test.ts
Global banners render only for qualifying errors, and warning summaries describe delayed verification and automatic retry behavior.

Estimated code review effort: 3 (Moderate) | ~20 minutes

Sequence Diagram(s)

sequenceDiagram
participant CodexProvider
participant ProviderRegistry
participant ProviderStatusBanner
CodexProvider->>ProviderRegistry: publish warning timeout with unknown authentication
ProviderRegistry->>ProviderRegistry: preserve previous ready snapshot
ProviderRegistry->>ProviderStatusBanner: expose merged provider status
ProviderStatusBanner->>ProviderStatusBanner: render only actionable errors
Loading

Possibly related PRs

Suggested reviewers:juliusmarminge

Poem

I’m a bunny with a timeout tune,
SQLite waits beneath the moon.
Codex warns, “I’ll try again,”
Claude stays ready through the rain.
Errors flash when action’s due—
Hop, hop, the status paths are new!

🚥 Pre-merge checks | ✅ 4 | ❌ 1

❌ Failed checks (1 warning)

Check nameStatusExplanationResolution
Docstring Coverage⚠️ WarningDocstring coverage is 25.00% which is insufficient. The required threshold is 80.00%.Write docstrings for the functions missing them to satisfy the coverage threshold.
✅ Passed checks (4 passed)
Check nameStatusExplanation
Title check✅ PassedThe title is concise and accurately summarizes the main stabilization work across provider status and workspace connection reliability.
Description check✅ PassedIt covers the key template sections with clear What Changed, Root Cause/Why, Impact, Validation, and Limitations details.
Linked Issues check✅ PassedCheck skipped because no linked issues were found for this pull request.
Out of Scope Changes check✅ PassedCheck skipped because no linked issues were found for this pull request.
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch fix/connection-reliability

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.

@coderabbitaicoderabbitaiBot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 1

🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
Inline comments:
In `@apps/server/src/persistence/NodeSqliteClient.test.ts`:
- Around line 32-40: Rename the test to describe asserting the default PRAGMA
busy_timeout value rather than cross-process write waiting. Extend the
NodeSqliteClient test coverage with focused cases for explicit, fractional,
negative, and non-finite busyTimeoutMs configurations, asserting each resulting
PRAGMA value and preserving the default-path assertion.
🪄 Autofix (Beta)

Fix all unresolved CodeRabbit comments on this PR:

  • Push a commit to this branch (recommended)
  • Create a new PR with the fixes

ℹ️ Review info
⚙️ Run configuration

Configuration used: Organization UI

Review profile: ASSERTIVE

Plan: Pro Plus

Run ID: ff6b483c-745f-4aeb-8e78-3a8eae3d3077

📥 Commits

Reviewing files that changed from the base of the PR and between bddf66c and 03ed3aa.

📒 Files selected for processing (10)
  • apps/server/src/persistence/NodeSqliteClient.test.ts
  • apps/server/src/persistence/NodeSqliteClient.ts
  • apps/server/src/provider/Layers/ClaudeProvider.ts
  • apps/server/src/provider/Layers/CodexProvider.ts
  • apps/server/src/provider/Layers/ProviderRegistry.test.ts
  • apps/server/src/provider/Layers/ProviderRegistry.ts
  • apps/web/src/components/chat/ProviderStatusBanner.test.tsx
  • apps/web/src/components/chat/ProviderStatusBanner.tsx
  • apps/web/src/components/settings/providerStatus.test.ts
  • apps/web/src/components/settings/providerStatus.ts

Comment threadapps/server/src/persistence/NodeSqliteClient.test.ts Outdated

@chatgpt-codex-connectorchatgpt-codex-connectorBot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit:e655ad6ff3

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

Comment threadapps/server/src/provider/Layers/ProviderRegistry.ts
@logancsack
logancsack merged commit 8e4cfd6 into mainJul 28, 2026
12 checks passed
Sign up for freeto join this conversation on GitHub. Already have an account? Sign in to comment

Labels

size:Mvouch:trustedPR author is trusted by repo permissions or the VOUCHED list.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant

@logancsack