Skip to content

👯 fix: Preserve MCP Connect Results Across Replicas - #17571

Merged
dustinhealy merged 5 commits into
feat/mcp-connection-observationfrom
fix/mcp-integration-status
Nov 19, 2026
Merged

dustinhealy merged 5 commits into
feat/mcp-connection-observationfrom
fix/mcp-integration-status

Conversation

@dustinhealy

@dustinhealy dustinhealy commented Oct 29, 2026 •

Copy link
Copy Markdown
Collaborator

Summary

In a multi-replica deployment, Connect can succeed on one replica and the next status request can land on a replica that has never opened the MCP transport. The settings row then returns to Connect, and some tool controls treat the server as unusable.

A successful Connect keeps the existing Reconnect action and tool selection available in the current browser session. The status dot stays neutral when the serving replica has no transport observation. The connection result is acknowledged by the existing toast. A real failure shows the existing Error and leaves Connect available for retry.

How it works

The API distinguishes actual transport observations, durable authorization, and the absence of an observation. The client combines these observations with the current Connect result. The existing status indicators describe known observations. With no transport observation, Settings and the compact palette keep a neutral dot and announce the server name without a status label. The expanded catalog shows the existing MCP Servers category subtitle. Agent Builder leaves out the status strip and keeps any applicable controls. The composer can attach a ready on-demand server, and Agent Builder selects discovered tools after a successful Connect.

The operation result is scoped to the browser session, user, tenant, server configuration, and authorization generation. Attempt ordering and later observations fence out obsolete results. React Query keeps the original server responses. Each API process still owns its transport. The status and operation fields used here come from #18473.

Type of change

  • Bug fix
  • Refactor
  • Tests / tooling / CI

Testing

Tested environments and configuration

Chromium with production builds, two LibreChat API processes, shared disposable MongoDB and Redis, a real MCP SDK HTTP fixture, a credential-dependent stdio fixture, and a local OAuth consent provider.

  • Connect on A and verify the existing success toast. Refresh status from cold B and reload before B opens any transport. Settings retains Reconnect in the current session and offers Connect after reload. The MCP fixture recorded one initialization through those steps. The first tool call on B added one initialization. A second tool call used the same transport after A stopped.

  • Make the fixture reject a real reconnect. Settings shows Error and Connect, then returns to Connected after a successful retry.

  • Connect from Agent Builder and route the next status request to cold B. The discovered tools are selected. Save custom variables and initialize the stdio server. Complete OAuth consent and confirm tool discovery and selection. An authorization-only status read from cold B keeps Reconnect and selection without a transport label. Exercise the existing pending and cancel controls.

  • In the expanded composer catalog, verify the selected card shows its standard subtitle after a cold status read. A failed reconnect still shows Error. Both checks ran in light and dark mode.

Automated tests

  • 285 focused client and composer tests passed, including operation ordering, generation and ownership checks, cancellation and logout, settings actions, composer selection, and Agent Builder readiness.
  • Client TypeScript, production client build, and commit checks passed. The browser paths above use the running app and real API responses.

Screenshots / recordings

Matched captures from the running application with identical fixtures, permissions, and 1280 × 720 viewports. The images use matching crops where the affected controls are small. The before column uses current dev at 584102d9b1. Expand the groups to inspect light and dark mode.

MCP Settings

Hover the connection action after Connect on A and a status read from cold B. Current dev offers Connect again. The revision keeps the existing Reconnect action with a neutral dot.

Theme Current dev Revision
Light Current dev · Cold read shows Connect · light mode Revision · Cold read keeps Reconnect with a neutral dot · light mode
Dark Current dev · Cold read shows Connect · dark mode Revision · Cold read keeps Reconnect with a neutral dot · dark mode

Fail a real reconnect and hover the available action. Current dev still shows Connected and Reconnect. The revision shows the error dot and the existing Connect action.

Theme Current dev Revision
Light Current dev · Failed retry still shows Connected · light mode Revision · Failed retry shows Error and Connect · light mode
Dark Current dev · Failed retry still shows Connected · dark mode Revision · Failed retry shows Error and Connect · dark mode

Restore the MCP fixture and retry. The revision confirms recovery with the connected dot and Reconnect. The prior capture shows that the same appearance on dev can survive a failed response.

Theme Current dev Revision
Light Current dev · Connected appearance after retry · light mode Revision · Connected after confirmed recovery · light mode
Dark Current dev · Connected appearance after retry · dark mode Revision · Connected after confirmed recovery · dark mode
Credential configuration

Open the variables dialog before entering a value. The original Disconnected badge, field, and actions are shown.

Theme Current dev Revision
Light Current dev · Unset variables with original controls · light mode Revision · Unset variables with original controls · light mode
Dark Current dev · Unset variables with original controls · dark mode Revision · Unset variables with original controls · dark mode

Save a value and initialize on A. The dialog shows Set, Active, and Reinitialize.

Theme Current dev Revision
Light Current dev · Saved variables with Active and Reinitialize · light mode Revision · Saved variables with Active and Reinitialize · light mode
Dark Current dev · Saved variables with Active and Reinitialize · dark mode Revision · Saved variables with Active and Reinitialize · dark mode

Keep the dialog open and read status from cold B. The revision keeps Reinitialize without showing an Active badge. Current dev shows Disconnected and Initialize.

Theme Current dev Revision
Light Current dev · Cold read shows Disconnected and Initialize · light mode Revision · Cold read keeps Reinitialize · light mode
Dark Current dev · Cold read shows Disconnected and Initialize · dark mode Revision · Cold read keeps Reinitialize · dark mode
Composer tool palette

Open Attach and tools after ordinary Connect and a cold-replica status read. The selected server remains in the composer, and the existing palette rows and dots are visible.

Theme Current dev Revision
Light Current dev · Selected server in the composer · light mode Revision · Selected server in the composer · light mode
Dark Current dev · Selected server in the composer · dark mode Revision · Selected server in the composer · dark mode

Select an on-demand server with its required variables already set. Current dev opens the variables dialog again. The revision attaches the server and keeps Configure available.

Theme Current dev Revision
Light Current dev · Selecting opens the variables dialog again · light mode Revision · Selecting attaches the server and exposes Configure · light mode
Dark Current dev · Selecting opens the variables dialog again · dark mode Revision · Selecting attaches the server and exposes Configure · dark mode

Open Show all MCP Servers after a successful Connect on A and a status read from cold B. Both cards are selected, as shown by the green outline and checkmark. The revision shows the standard MCP Servers subtitle.

Theme Current dev Revision
Light Current dev · Selected catalog card shows Disconnected · light mode Revision · Selected catalog card shows the MCP Servers subtitle · light mode
Dark Current dev · Selected catalog card shows Disconnected · dark mode Revision · Selected catalog card shows the MCP Servers subtitle · dark mode

Open the expanded catalog after a failed Reconnect on the replica that attempted it. The card shows the existing Error status.

Theme Current dev Revision
Light Current dev · Failed reconnect leaves Connected on the card · light mode Revision · Failed reconnect shows Error on the card · light mode
Dark Current dev · Failed reconnect leaves Connected on the card · dark mode Revision · Failed reconnect shows Error on the card · dark mode
Agent Builder

Inspect the already available server after Connect elsewhere in the same session. Current dev still offers the full-width Connect action. The revision keeps the tool controls and omits the status strip.

Theme Current dev Revision
Light Current dev · Cold read shows Disconnected and Connect · light mode Revision · Tool controls without an unobserved status · light mode
Dark Current dev · Cold read shows Disconnected and Connect · dark mode Revision · Tool controls without an unobserved status · dark mode

Connect from the server detail itself and read status from cold B. Current dev leaves the discovered tool unchecked. The revision checks the tool and bulk selector, and the library card shows the existing selection check.

Theme Current dev Revision
Light Current dev · Discovered tool remains unchecked · light mode Revision · Discovered tool and bulk selector are checked · light mode
Dark Current dev · Discovered tool remains unchecked · dark mode Revision · Discovered tool and bulk selector are checked · dark mode

Inspect a previously initialized server with saved variables after a status read on cold B. The revision keeps the existing Configure key button and leaves out the unobserved status.

Theme Current dev Revision
Light Current dev · Saved variables and the Connect control · light mode Revision · Saved variables with Configure available · light mode
Dark Current dev · Saved variables and the Connect control · dark mode Revision · Saved variables with Configure available · dark mode
Pending OAuth

Connect to a server that requires OAuth. The existing prompt shows the link, copy and QR controls, and Continue with OAuth.

Theme Current dev Revision
Light Current dev · Pending OAuth prompt · light mode Revision · Pending OAuth prompt · light mode
Dark Current dev · Pending OAuth prompt · dark mode Revision · Pending OAuth prompt · dark mode

Dismiss the prompt while authorization is pending, then hover the settings action. The existing Cancel control remains available.

Theme Current dev Revision
Light Current dev · Cancel is available while OAuth waits · light mode Revision · Cancel is available while OAuth waits · light mode
Dark Current dev · Cancel is available while OAuth waits · dark mode Revision · Cancel is available while OAuth waits · dark mode

Accessibility and behavior

Surface What the browser verifies
MCP Settings The cold row is announced by its server name. Reconnect is available in the same browser session, and a reload on cold B offers Connect. A real failed attempt is labeled Error.
Composer The ordinary selected row keeps its pressed state and neutral dot. The compact palette announces the server and its selection without a status label. In the expanded catalog, the selected card includes its standard category subtitle and still announces concrete errors. An eligible on-demand row changes to pressed and exposes its existing Configure action.
Agent Builder A ready server removes the redundant Connect control from the tab order and accessibility tree. With no transport observation, the detail omits the status strip and any status announcement. Connect within the dialog selects the discovered tools once they are available.
Credentials and OAuth The existing form labels and OAuth controls remain. The browser also verifies credential save and initialization, OAuth consent and readiness, and tool execution after one replica stops.

Risk / compatibility

The client uses additive status metadata. Older API responses follow conservative handling. Operation results are session-local and do not change persisted data. A fresh browser load at a cold replica shows the server name and existing Connect action until the browser receives a transport observation or starts a connection.

The cold status request and reload produced zero extra MCP initializations in the controlled browser scenario. The revised presentation adds no periodic network requests. Reconciliation compares configuration and authorization generations locally. Large server collections and production Connect latency were not benchmarked.

Checklist

  • I reviewed my own changes
  • Relevant tests have been added or updated
  • Existing relevant tests pass
  • Required documentation PR is not applicable

@dustinhealy
dustinhealy added this pull request to stack #17572 October 29, 2026 00:58

Copy link
Copy Markdown
Collaborator Author

@codex review

@chatgpt-codex-connector

chatgpt-codex-connector Bot commented Oct 29, 2026 •

Copy link
Copy Markdown
Codex Review Summary: ✅ Completed

This comment shows the latest Codex review activity on this pull request.

Review Status Commit Review trigger
📝 Code Review ✅ Completed 2026-11-19T06:33:22.287347Z 3edecca Manual request
ℹ️ 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" or "@codex security review".

Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings.

@chatgpt-codex-connector chatgpt-codex-connector Bot 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: 72981b317d

ℹ️ 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".

@codegraph-librechat codegraph-librechat Bot added 🗺️ Core Platform codegraph: the taxonomy area this belongs to (classifier, confidence ≥ 0.9) 🛡️ security review labels Oct 29, 2026
Copilot AI balanced review requested due to automatic review settings October 29, 2026 01:10

Copy link
Copy Markdown
Collaborator Author

@codex review

Copilot AI left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

🟡 Changes recommended

OAuth cancellation can leave initialization stuck or block polling on retries, while recovery-related timestamp changes can invalidate a successful connection result and incorrectly show Disconnected.

3 open issues
What changed in this PR

This PR preserves explicit MCP Connect outcomes within the signed-in browser session, preventing status reads from a replica without a local connection from incorrectly showing Disconnected.

Changes:

  • Moves Connect handling and status resolution into the TypeScript API package, with explicit status sources and authorization generations.
  • Adds session-scoped Connect results, retry ordering, logout cleanup, and shared status presentation.
  • Adds focused regressions and a two-replica browser test wired into CI.
File Description
packages/​data-provider/​src/​types/​queries.ts Adds connection status source metadata.
packages/​data-provider/​src/​types/​mcpServers.ts Adds authorization generation to Connect responses.
packages/​data-provider/​src/​data-service.ts Applies the configurable Connect timeout.
packages/​data-provider/​src/​clientLimits.ts Defines the Connect timeout setting and default.
packages/​data-provider/​src/​clientLimits.spec.ts Tests Connect timeout defaults and validation.
packages/​api/​src/​mcp/​readiness.ts Resolves transport and authorization status separately.
packages/​api/​src/​mcp/​readiness.spec.ts Tests replica-local status observations.
packages/​api/​src/​mcp/​connection.ts Exposes the local connection state.
packages/​api/​src/​mcp/​connect.ts Implements injected Connect handling and fresh retries.
packages/​api/​src/​mcp/​connect.spec.ts Tests Connect outcomes, OAuth responses, and safe errors.
packages/​api/​src/​index.ts Exports the new MCP handlers.
e2e/​specs/​mock/​mcp-connect-replicas.spec.ts Tests cross-replica status, tool calls, and retry recovery.
e2e/​setup/​start-server-cluster.js Adds replica targeting and controlled primary shutdown.
e2e/​setup/​fake-model.js Adds a deterministic replica-test tool call.
e2e/​setup/​fake-mcp-status-server.js Provides a controllable MCP server fixture.
e2e/​playwright.config.mock.ts Configures the MCP connection fixture.
e2e/​playwright.config.mcp-connect.ts Defines the dedicated browser-test configuration.
client/​src/​store/​mcp.ts Stores session-owned Connect results and reset behavior.
client/​src/​Providers/​__tests__/​BadgeRowContext.spec.tsx Supplies authentication context for manager consumers.
client/​src/​locales/​en/​translation.json Removes the obsolete Offline translation key.
client/​src/​hooks/​MCP/​useMCPServerManager.ts Integrates Connect results, attempt ordering, and cleanup.
client/​src/​hooks/​MCP/​connection.ts Applies results using owner, configuration, and generation checks.
client/​src/​hooks/​MCP/​__tests__/​useMCPServerManager.spec.tsx Tests polling, retry ordering, and session invalidation.
client/​src/​hooks/​MCP/​__tests__/​connection.spec.ts Tests configuration identity and metadata changes.
client/​src/​hooks/​AuthContext.tsx Clears MCP session state at logout.
client/​src/​hooks/​__tests__/​AuthContext.spec.tsx Tests logout cleanup of MCP state.
client/​src/​components/​SidePanel/​MCPBuilder/​MCPStatusBadge.tsx Removes the builder-specific badge implementation.
client/​src/​components/​SidePanel/​MCPBuilder/​MCPServerCard.tsx Uses shared status helpers and configuration readiness.
client/​src/​components/​SidePanel/​MCPBuilder/​MCPServerCard.spec.tsx Updates the shared badge mock.
client/​src/​components/​MCP/​MCPStatusBadge.tsx Provides shared status badge rendering.
client/​src/​components/​MCP/​MCPStatusBadge.spec.tsx Tests visibility of request-scoped errors.
client/​src/​components/​MCP/​mcpServerUtils.ts Unifies status presentation and required-variable checks.
client/​src/​components/​MCP/​mcpServerUtils.spec.ts Tests attachment blocking when variables are missing.
client/​src/​components/​MCP/​MCPServerStatusIcon.tsx Uses shared status colors.
client/​src/​components/​MCP/​MCPConfigDialog.tsx Reuses shared status labels and badges.
client/​src/​components/​Chat/​__tests__/​ChatView.subagent.spec.tsx Supplies authentication context in chat tests.
api/​server/​services/​MCP.spec.js Updates assertions for the status resolver contract.
api/​server/​services/​MCP.js Delegates status resolution to the TypeScript package.
api/​server/​routes/​mcp.js Wires the Connect handler and exposes status sources.
api/​server/​routes/​__tests__/​mcp.spec.js Updates credential-loading assertions after extraction.
.github/​workflows/​playwright-mock.yml Runs the Connect regression in the two-replica job.

Review effort: Balanced

Comment thread client/src/hooks/MCP/connection.ts Resolved

@chatgpt-codex-connector chatgpt-codex-connector Bot 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: 4ec35977da

ℹ️ 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 thread packages/api/src/mcp/connect.ts Resolved
Comment thread packages/api/src/mcp/readiness.ts Resolved

Copy link
Copy Markdown
Collaborator Author

@codex review

@chatgpt-codex-connector chatgpt-codex-connector Bot 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: 2b2b3adff8

ℹ️ 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 thread client/src/hooks/MCP/connection.ts Resolved

Copy link
Copy Markdown
Collaborator Author

@codex review

@chatgpt-codex-connector chatgpt-codex-connector Bot 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: f4a87db393

ℹ️ 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 thread client/src/hooks/MCP/connection.ts Resolved

Copy link
Copy Markdown
Collaborator Author

@codex review

@chatgpt-codex-connector

Copy link
Copy Markdown

Codex Review: Didn't find any major issues. 🎉

Reviewed commit: ddbaddec65

ℹ️ 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".

@dustinhealy
dustinhealy marked this pull request as ready for review October 29, 2026 21:20
Base automatically changed from fix/agent-builder-mcp-discovery to dev November 18, 2026 21:07
@dustinhealy
dustinhealy force-pushed the fix/mcp-integration-status branch from 7bce4c0 to deafe9d Compare November 18, 2026 21:46

Copy link
Copy Markdown
Collaborator Author

@codex review

Copy link
Copy Markdown
Collaborator Author

/quality risk scopes=api,server

@github-actions

github-actions Bot commented Nov 18, 2026 •

Copy link
Copy Markdown
Contributor

Quality report

Outdated: this request is for an earlier PR commit.

Gate: open. The selected checks completed. Scores and risk levels are advisory.

Status: completed (success). Actions run, attempt 1.

  • Commit: deafe9d87e8f47ff1680f3fc11a01574f988aef4
  • Requested by: @dustinhealy
  • Check: risk
  • Scopes: api, server
  • Static mutants: off (not used by change risk)
  • Change risk: api, server
  • Mutation testing (experimental, data-schemas only): none

Change risk

Takeaway: 4 changed lines have no test. Highest CRAP among changed functions: (anonymous) at packages/api/src/mcp/connect.ts:86, CRAP 31.1 with 96% coverage.

Workspace Files measured Incomplete Unavailable Changed lines with no test Highest CRAP
api 4 of 4 0 0 4 31.1
server 2 of 2 0 0 0 8.0

Changed lines with no test

packages/api/src/mcp/readiness.ts: 2 lines (api)

Line 61

    authorizationState = 'authorizing';

Line 63

    authorizationState = 'error';
packages/api/src/mcp/connect.ts: 1 line (api)

Line 233

        return next(error);
packages/api/src/mcp/connection.ts: 1 line (api)

Line 3256

    return this.connectionState;

Refactor hints (highest CRAP first)

Function Complexity Coverage CRAP Location
(anonymous) 31 96% 31.1 packages/api/src/mcp/connect.ts:86
resolveMCPConnectionStatus 29 95% 29.1 packages/api/src/mcp/readiness.ts:26
(anonymous) 8 100% 8.0 api/server/routes/mcp.js:1005
(anonymous) 5 100% 5.0 api/server/routes/mcp.js:960
getMCPReinitializeOAuthTimeout 3 100% 3.0 packages/api/src/mcp/connect.ts:64
getServerConnectionStatus 2 100% 2.0 api/server/services/MCP.js:1727
getMCPUnavailableStatus 2 100% 2.0 packages/api/src/mcp/readiness.ts:108
getConnectionState 1 0% 2.0 packages/api/src/mcp/connection.ts:3255
abort 1 50% 1.1 packages/api/src/mcp/connect.ts:149
getOAuthFlowId 1 100% 1.0 api/server/routes/mcp.js:923

4 more functions below the threshold (or cut for size) are in report.md.

CRAP = complexity² × (1 − coverage)³ + complexity

Jobs (2)
Check Result
Change risk (api) success
Change risk (server) success

All data (quality-report artifact) · Run page

The gate opens only when the workflow, source selection, tooling verification, and every report job succeed. A report job fails on a failed test in its workspace's own Jest run, a tool error, a job timeout, or an incomplete mutation report, including a mutation shard that reaches its execution budget. A cancelled workflow keeps the gate closed. Scores are advisory. A change-risk file marked incomplete or unavailable, for example by a failed api/ source-alias suite, does not close the gate.

@chatgpt-codex-connector

Copy link
Copy Markdown

Codex Review: Didn't find any major issues. Breezy!

Reviewed commit: deafe9d87e

ℹ️ 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".

@dustinhealy
dustinhealy force-pushed the fix/mcp-integration-status branch from deafe9d to 2dc26b5 Compare November 18, 2026 22:40
@dustinhealy
dustinhealy removed this pull request from stack #17572 November 18, 2026 22:41
@dustinhealy
dustinhealy changed the base branch from dev to feat/mcp-connection-observation November 18, 2026 22:42
@dustinhealy
dustinhealy added this pull request to stack #18475 November 18, 2026 22:42
@dustinhealy
dustinhealy force-pushed the fix/mcp-integration-status branch from 2dc26b5 to 1488c72 Compare November 18, 2026 23:18
@dustinhealy
dustinhealy force-pushed the fix/mcp-integration-status branch from 1488c72 to c303962 Compare November 18, 2026 23:54
@dustinhealy

Copy link
Copy Markdown
Collaborator Author

/quality ignore

@dustinhealy

Copy link
Copy Markdown
Collaborator Author

@codex review

@github-actions

github-actions Bot commented Nov 18, 2026 •

Copy link
Copy Markdown
Contributor

Quality report

Outdated: this request is for an earlier PR commit.

Gate: open. Quality checks explicitly ignored for this commit.

  • Commit: c30396267c2e44662eb3566ee751bdf8702f852c
  • Requested by: @dustinhealy
  • Check: ignore

The gate opens only when the workflow, source selection, tooling verification, and every report job succeed. A report job fails on a failed test in its workspace's own Jest run, a tool error, a job timeout, or an incomplete mutation report, including a mutation shard that reaches its execution budget. A cancelled workflow keeps the gate closed. Scores are advisory. A change-risk file marked incomplete or unavailable, for example by a failed api/ source-alias suite, does not close the gate.

@chatgpt-codex-connector

Copy link
Copy Markdown

Codex Review: Didn't find any major issues. 🚀

Reviewed commit: c30396267c

ℹ️ 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".

@dustinhealy dustinhealy changed the title 🔌 fix: Preserve MCP Connect Results Across Replicas 👯 fix: Preserve MCP Connect Results Across Replicas Nov 19, 2026
@dustinhealy

Copy link
Copy Markdown
Collaborator Author

@codex review

@dustinhealy

Copy link
Copy Markdown
Collaborator Author

/quality ignore

@github-actions

Copy link
Copy Markdown
Contributor

Quality report

Gate: open. Quality checks explicitly ignored for this commit.

  • Commit: 3edeccaab9d5cb920f9739dfcd08a021056632de
  • Requested by: @dustinhealy
  • Check: ignore

The gate opens only when the workflow, source selection, tooling verification, and every report job succeed. A report job fails on a failed test in its workspace's own Jest run, a tool error, a job timeout, or an incomplete mutation report, including a mutation shard that reaches its execution budget. A cancelled workflow keeps the gate closed. Scores are advisory. A change-risk file marked incomplete or unavailable, for example by a failed api/ source-alias suite, does not close the gate.

@chatgpt-codex-connector

Copy link
Copy Markdown

Codex Review: Didn't find any major issues. What shall we delve into next?

Reviewed commit: 3edeccaab9

ℹ️ 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".

@dustinhealy
dustinhealy merged commit 459a8aa into dev Nov 19, 2026
67 checks passed
@dustinhealy
dustinhealy deleted the fix/mcp-integration-status branch November 19, 2026 06:42
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

🗺️ Core Platform codegraph: the taxonomy area this belongs to (classifier, confidence ≥ 0.9) 🛡️ security review

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants