Skip to content

Comments

cli: only warn about --annotate when explicitly passed via CLI#531

Merged
ctate merged 1 commit intovercel-labs:mainfrom
lukasmalkmus:fix-annotate-config-warning
Feb 23, 2026
Merged

cli: only warn about --annotate when explicitly passed via CLI#531
ctate merged 1 commit intovercel-labs:mainfrom
lukasmalkmus:fix-annotate-config-warning

Conversation

@lukasmalkmus
Copy link
Contributor

The --annotate warning fires on every non-screenshot command when annotate is set in the user-level config file (~/.agent-browser/config.json). This is noisy for users who set it as a persistent default — the whole point of a config file.

Adds cli_annotate tracking to the Flags struct, matching the existing cli_* pattern used for executable_path, extensions, profile, etc. The warning now only fires when --annotate is explicitly passed as a CLI flag.

Fixes #530

@vercel
Copy link
Contributor

vercel bot commented Feb 23, 2026

@lukasmalkmus is attempting to deploy a commit to the Vercel Labs Team on Vercel.

A member of the Team first needs to authorize it.

The warning "⚠ --annotate only applies to the screenshot command" fires
on every non-screenshot command when annotate is set in config. This is
noisy for users who set it as a persistent default.

Add cli_annotate tracking (matching the existing cli_* pattern) so the
warning only fires when --annotate is passed as a CLI flag.
@lukasmalkmus lukasmalkmus force-pushed the fix-annotate-config-warning branch from b208643 to 1e8ac37 Compare February 23, 2026 14:57
@ctate
Copy link
Collaborator

ctate commented Feb 23, 2026

LGTM - thanks @lukasmalkmus

@ctate ctate merged commit f10f3f6 into vercel-labs:main Feb 23, 2026
3 of 4 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Config-sourced --annotate warns on every non-screenshot command

2 participants