Report Cloud MCP failures to Sentry - #3370
Closed
reachjalil wants to merge 1 commit into
Closed
Conversation
Contributor
|
The latest updates on your projects. Learn more about Vercel for GitHub.
1 Skipped Deployment
|
Contributor
|
@reachjalil is attempting to deploy a commit to the Different AI Team on Vercel. A member of the Team first needs to authorize it. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
openwork-cloudMCP reconciliation failures through the existing authenticated Den telemetry pathRoot cause
The app showed a blocking Cloud MCP failure but retained the evidence only in the local UI and diagnostics. The desktop does not have its own Sentry SDK, so the terminal reconciliation failure never reached production error monitoring.
Privacy and scope
The event includes only allowlisted classification/status fields and component versions. Both the client and server map unknown or content-like values to safe fallbacks. It never sends messages, raw errors, URLs, paths, IDs, tokens, labels, metadata, or raw diagnostic payloads.
This does not change UI or recovery behavior. It is separate from #3198's Cloud MCP repair work and from #3073/#3074's explicit opt-in diagnostics relay.
Verification
corepack pnpm --filter @openwork/app exec bun test --isolate tests/cloud-mcp-diagnostics.test.ts tests/session-mcp-maintenance.test.ts— 17 passedcorepack pnpm --filter @openwork-ee/den-api exec bun test test/telemetry-sentry.test.ts— 3 passedcorepack pnpm --filter @openwork/app typecheck— passedcorepack pnpm --filter @openwork-ee/den-api exec tsc -p tsconfig.json --noEmit— passedgit diff --check— passedNo Fraimz/browser proof is included because this is an observability-only change with no user-visible UI behavior.