Repository navigation
feat(cli): add --anchor-area to pin a comment to an area - #428
Merged
Merged
Conversation
`argos comment create` and `argos media comment create` take `--anchor-area <x,y,width,height>`: a rectangle in normalized 0-1 coordinates, with x,y at its top-left corner. Comments print an area anchor as `area 0.1,0.2 0.3x0.25`. The api-client schema gets the `area` anchor variant by hand, until the API serving it is deployed and the file can be regenerated. The argos-cli, argos-pr-review and argos-upload skills say when to mark an area rather than a point. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This was referenced Nov 19, 2026
This branch was successfully 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.
Description
Adds
--anchor-area <x,y,width,height>toargos comment createandargos media comment create, so an agent can pin a comment to a whole region of a screenshot (a component, a section) instead of a single point.areaanchor ({ type: "area", x, y, width, height }, normalized 0-1,x,y= top-left corner) to the REST API and MCP.packages/api-client/src/schema.tsis hand-edited to add the area variant, because the live API doesn't serve it yet. The nextbuild-schema-typesrun will produce the same shape.lib/anchor.ts): four numbers, each 0-1, width and height above 0, andx + width/y + heightat most 1 (1e-9 tolerance, the same as the backend). The three anchor flags can't be combined.--anchor-point 0.5,fails instead of being read as0.5,0.comment create: requires--diff, like the other anchors. The "needs a diff" error now names the flag that was used.media comment create: refused with--reply-to, like--anchor-point.area 0.1,0.2 0.3x0.25, both asDiff: … (area …)and asPinned: area ….formatAnchoris now an exhaustive switch.argos-cli: an<anchor>placeholder in the build and media comment commands, plus when to use an area versus a point.argos-pr-review: the "pin the comment" bullet now covers area, point and lines.argos-upload: reading backPinned: area …and theanchorfield.Type of changes
enhancementChecklist
check-types,lint,check-format,testfor@argos-ci/cliand@argos-ci/api-client: 215 and 28 tests;check-typesandlintfor every package depending on the api-client)anchor.test.ts,format.test.ts)Further comments
Release this after argos-ci/argos#2802 is deployed: until then, the API rejects an
areaanchor. The docs change is in theclaude/area-comment-anchorbranch of argos-ci/docs.🤖 Generated with Claude Code