This repository was archived by the owner on Jul 19, 2026. It is now read-only.
chore: re-stage local proxy bundle without Google sample-data fallback - #188
Merged
Merged
Conversation
Regenerates vendor/local-proxy-server.js from the updated multicorn-proxy build. The built-in MCP Google tools no longer return fabricated emails, events, files or fake write confirmations when Google is not connected; they return a clear "Google is not connected" error instead. Slack tools return a "not available yet" error rather than sample content. Companion to multicorn-proxy#38.
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 subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
What
Regenerates the vendored local proxy bundle (
vendor/local-proxy-server.js) from the updatedmulticorn-proxybuild, so the local proxy behaves the same as the hosted proxy.Companion to Multicorn-AI/multicorn-proxy#38.
Why
The built-in MCP Google tools used to return sample data on a success response when Google was not connected: fabricated emails/events/files from read tools, and fake success from write tools (
gmail_send_emailreported "Email sent", deletes and Drive writes returned fake confirmations). That behaviour shipped in the vendored bundle too, so a locally connected agent (e.g. Cursor) got the same fabricated data.The proxy PR removes the fallback and returns a clear error instead:
Slack tools (no OAuth path) now return a "not available yet" error rather than sample content.
How it was regenerated
pnpm buildwith themulticorn-proxysibling checked out re-bundles../multicorn-proxy/src/server.tsintodist/server.jsandscripts/stage-local-proxy-server.mjscopies it tovendor/local-proxy-server.js. Only the vendored file changed.Test plan
pnpm buildregenerates the vendored bundle (no moreSAMPLE_NOTE/Alex Chen/thread_sample; addsGOOGLE_NOT_CONNECTED/SLACK_NOT_AVAILABLE)vitest run src/commands/local-proxy-start.test.ts src/commands/local-proxy-server-entry.test.ts(7 passing)Made with Cursor