Repository navigation
Conversation
The parameter description and the refusal both gave a full Danish mobile number as the example. A model that has no number and follows the example opens a WhatsApp chat with it: open_chat builds whatsapp://send?phone=<digits> and computer_open is not on the always-ask list, so in the default background mode nothing asks first. Any digits used as an example could belong to someone, so the fix is to describe the format instead of showing one. 0.1.0 had no open_chat (it arrived in c063058, 29/9), so without this 0.4.1 would have introduced the path rather than kept it. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…very one
The README said a password manager "can never be photographed on its own". The
helper leaves deny-listed apps out of the capture only when redacting
(Capture.swift: the exclusion sits inside `if redact {`). Redaction is the
default, and an unredacted screenshot is the person's decision, never the
model's - but in that case the window is captured like any other, so "never"
was not true.
An npm README is frozen per version, so the wording is fixed before 0.4.1 rather
than after. The npm README is derived from this file by sync-tal.py.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This branch has not been deployed
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.
Two things a pre-release review found, which should not ship to npm in 0.4.1.
The phone example in
open_chatcould open a real chat. The parameter description and the refusal both gave a full Danish mobile number as the format example.open_chatbuildswhatsapp://send?phone=<digits>and opens it, andcomputer_openis not on the always-ask list, so a model that has no number and follows the example opens a WhatsApp chat with it, in the default background mode, without asking first. Any digits used as an example could belong to someone, so this describes the format instead of showing one. 0.1.0 had noopen_chat(it arrived in c063058), so without this change 0.4.1 would introduce the path rather than keep it.The README promised more than the helper does. It said a password manager "can never be photographed on its own". The helper leaves deny-listed apps out of the capture only when redacting (
Capture.swift, insideif redact {). Redaction is the default and an unredacted screenshot is the person's decision, so the wording now says that. An npm README is frozen per version, so this is fixed before 0.4.1 rather than after. The npm README is derived from the root README bysync-tal.py.Not touched:
policy.jsandtest/failclosed.mjs, so the dialog receipt for the consent gate (c5efa0b6) still holds.Checked locally: CI's screen-free tests plus
doer.mjs(which exercisesopen_chat) all pass. The packed tarball after the release script's step 0 has 19 files, the receipted helper and icon, and no digit example.🤖 Generated with Claude Code