Repository navigation
release: v0.3.4 (browser cookies opt-in) - #19
Merged
Merged
Conversation
Browser cookies become opt-in. A browser session is the user's identity on that platform, and an agent-driven tool should not reuse it without being told to. ClawHub's review of the skill said the same thing after v0.3.3 cleared the install finding: "can automatically use local browser login cookies when a site blocks anonymous access". - bin/dl-video: WATCH_BROWSER unset (default) or "none" never touches a browser profile; a login wall fails with tag=download-auth and the error explains how to opt in. WATCH_BROWSER=auto tries Chrome, Firefox, Safari, Edge, Brave, Chromium in order; a browser name tries that one. --cookies <file> is unchanged. - SKILL.md, README, docs/cookies.md, docs/platforms.md, docs/exit-codes.md describe the opt-in and tell agents to ask the user before setting it. - Pinned installer references move to v0.3.4; lib/version.sh 0.3.3 -> 0.3.4. Verified: default run against an unreachable URL prints no "retrying with" line; WATCH_BROWSER=auto walks the chain; WATCH_BROWSER=firefox tries only firefox. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_018Rok2mujdEZ2yGw8wVfbr9
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.
Draft: this changes a default, so it waits for a product decision.
Why
v0.3.3 cleared the "unpinned install" finding on ClawHub. The re-scan of skill 1.0.1 still says: "can automatically use local browser login cookies when a site blocks anonymous access." The reviewer is judging behaviour, not wording: as long as
watchfalls back to a signed-in browser on its own, the listing stayssuspicious.There is also a product argument. A browser session is the user's identity on LinkedIn, X or Facebook. When an agent runs
watchon a URL the user pasted, reusing that session silently is a bigger step than the user asked for.What changes
WATCH_BROWSERunset (default) ornone: no browser profile is read. A login wall fails withtag=download-auth, and the error shows the opt-in.WATCH_BROWSER=auto: the previous chain (Chrome → Firefox → Safari → Edge → Brave → Chromium).WATCH_BROWSER=firefox(any name): that browser only, as before.--cookies <file>: unchanged.lib/version.sh→ 0.3.4.Cost
Users who relied on the silent fallback for LinkedIn/private X/Facebook now add
WATCH_BROWSER=autoonce (or export it in their shell). The error message says exactly that.Verified
bash -n; default run prints no "retrying with" line;autowalks the chain;firefoxtries only firefox.If approved: merge, tag
v0.3.4, then republish the ClawHub skill as 1.0.2 from the tagged commit.🤖 Generated with Claude Code
https://claude.ai/code/session_018Rok2mujdEZ2yGw8wVfbr9