Repository navigation
Remove a real person's phone number and full name from the open_chat example and three tests - #15
Merged
Merged
Conversation
The parameter description and the refusal gave a real person's Danish mobile number as the format example - and open_chat builds whatsapp://send?phone=<digits> from what the model passes, so a model copying the example would open a chat with a real person. Now the format is described in words, with no number to copy: "a plus sign, the country code and the number, digits only. Use the number the user gave you; never make one up." These two lines are taken verbatim from PR #14 (9eeabff), so that PR merges on top without a conflict and the npm tarball it was fingerprinted on (0.4.1, sha512-5vnxkavd41DC...nJ3eA==) is unchanged by this hotfix. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…, not a real person's test/doer.mjs and test/laering.mjs used the same real number as their input; test/sende-port.mjs used a real person's first and last name as the WhatsApp recipient read from the screen. Now +45 01 23 45 67 (no Danish number starts with 0) and "Alex" / "Alex Hansen". laering's check 2f searched the share link for the real number; with a fictional input it could no longer fail. It now searches for the fictional one (01%2023%2045%2067|01234567): an encoded "+45 01 23 45 67" is caught, a redacted link passes. Tests are not in the npm package, so the 0.4.1 tarball's fingerprint is untouched. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
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
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.
The
open_chatparameter description and its refusal gave a real person's Danish mobile number as the format example, and three tests used the same number and that person's full name.open_chatbuildswhatsapp://send?phone=<digits>from what the model passes, so a model copying the example would open a chat with a real person.mcp-server/index.js,mcp-server/tools.js: the format is described in words, with no number to copy. These two lines are verbatim from 0.4.1: describe the phone format without a real number, and correct a README claim #14, so 0.4.1: describe the phone format without a real number, and correct a README claim #14 merges on top without a conflict and the npm tarball it was fingerprinted on is unchanged.test/doer.mjs,test/laering.mjs,test/sende-port.mjs: a made-up number (+45 01 23 45 67 - no Danish number starts with 0) and name. laering's share-link check searched for the real number and could no longer fail; it searches for the fictional one now.Checked locally: claims-offline, readme-log, audit-chain, pakke-filer, usynlige-navne, bundet-maal, plugin-manifest, doer, laering, sende-port - all green.
🤖 Generated with Claude Code