auto">Codex review: keeping this open for maintainer follow-up; there is still a little grit to resolve. Reviewed July 5, 2026, 5:38 AM ET / 09:38 UTC.

Summary
Keep open: current main and v0.32.0 still lack a Sheets basic-filter command, and #902 is now the open closing implementation candidate. The issue should remain the canonical request until that PR lands or is closed.

Reproducibility: not applicable. as a bug reproduction; this is a feature gap. Source and generated docs on current main confirm no Sheets filter/basic-filter command exists, while the linked PR is the candidate implementation.

Root-cause cluster
Relationship: canonical
Canonical: #899
Summary: This issue is the canonical request; #902 is the open candidate fix that closes it.

Members:

fixed_by_candidate: feat(sheets): add basic filter creation command #902 - The PR body closes this issue and adds the requested Sheets basic filter creation command.

Proposal only: this assessment does not dispatch repair, suppress jobs, mutate sibling items, close, or merge anything.

Ways to help us reproduce this

Add a screenshot or short recording showing the behavior.
Add expected vs actual behavior.
Include redacted logs or terminal output.

Next step
No separate repair lane is needed because #902 is already the open closing implementation candidate.

Review details

Best possible solution:

Review and land #902 if it remains acceptable, then let that PR close this issue; otherwise keep this issue as the canonical feature request.

Do we have a high-confidence way to reproduce the issue?

Not applicable as a bug reproduction; this is a feature gap. Source and generated docs on current main confirm no Sheets filter/basic-filter command exists, while the linked PR is the candidate implementation.

Is this the best way to solve the issue?

Yes: keeping this issue open while the linked closing PR is reviewed is the narrowest maintainable path. Opening another repair job now would duplicate the existing implementation candidate.

AGENTS.md: found and applied where relevant.

Remaining risk / open question:

Until feat(sheets): add basic filter creation command #902 merges, users on current main and v0.32.0 still cannot create Sheets basic filters through gog.

Codex review notes: model internal, reasoning high; reviewed against c0aac99f6be6.

Label changes

Label changes:

add clawsweeper:linked-pr-open: Current issue advisory state selects this label.
add clawsweeper:no-new-fix-pr: Current issue advisory state selects this label.
remove clawsweeper:fix-shape-clear: Current issue advisory state no longer selects this label.
remove clawsweeper:queueable-fix: Current issue advisory state no longer selects this label.

Label justifications:

P2: This is a bounded Sheets automation feature gap with a linked implementation PR and limited blast radius.
impact:other: The issue concerns Sheets command coverage, which is meaningful product capability outside the owned impact taxonomy.

Evidence reviewed

What I checked:

Repository policy read: AGENTS.md was read fully; its read-only PR-review guidance applied while inspecting the linked implementation PR without changing branches or files. (AGENTS.md:37, c0aac99f6be6)
Current main lacks the command: The current Sheets command registry lists existing Sheets subcommands but has no filter/basic-filter command. (internal/cmd/sheets.go:33, c0aac99f6be6)
Generated docs lack the command: The generated gog sheets command page lists all Sheets subcommands and does not include filter or setBasicFilter support. (docs/commands/gog-sheets.md:17, c0aac99f6be6)
Latest release lacks the command: The v0.32.0 release tree has no matches for setBasicFilter/basic filter/sheets filter terms, and its generated Sheets command page also lacks a filter entry. (docs/commands/gog-sheets.md:17, f20a26cd9e26)
Open implementation candidate: The linked PR is open, cleanly mergeable, and its body closes this issue while adding gog sheets filter set <spreadsheetId> <range>. (dba7ddbdf86d)
Vision fit: VISION.md says small useful primitives and incremental Google Workspace capabilities in supported areas fit the project, which matches a bounded Sheets filter creation command. (VISION.md:9, c0aac99f6be6)

Likely related people:

Peter Steinberger: Blame and adjacent commits show current ownership of the Sheets command registry and recent BatchUpdate-backed Sheets mutation surfaces. (role: recent area contributor; confidence: high; commits: f20a26cd9e26, b83649577597, e1be268f70a6; files: internal/cmd/sheets.go, internal/cmd/sheets_mutation_helpers.go, internal/cmd/sheets_range_resolve.go)
Tsopic: Authored the adjacent gog sheets batch-update command and tests in the same Sheets command registry area. (role: adjacent contributor; confidence: medium; commits: f911d6b21835; files: internal/cmd/sheets.go, internal/cmd/sheets_batch_update_test.go, docs/commands/gog-sheets-batch-update.md)
Shehryar: Credited on the commit adding several BatchUpdate-backed Sheets mutation commands closest to the requested filter command style. (role: credited adjacent contributor; confidence: medium; commits: 004b68cc703f; files: internal/cmd/sheets.go, internal/cmd/sheets_freeze.go, internal/cmd/sheets_merge.go)

How this review workflow works

ClawSweeper keeps one durable marker-backed review comment per issue or PR.
Re-runs edit this comment so the latest verdict, findings, and automation markers stay together instead of adding duplicate bot comments.
A fresh review can be triggered by eligible @clawsweeper re-review comments, exact-item GitHub events, scheduled/background review runs, or manual workflow dispatch.
PR/issue authors and users with repository write access can comment @clawsweeper re-review or @clawsweeper re-run on an open PR or issue to request a fresh review only.
Maintainers can also comment @clawsweeper review to request a fresh review only.
Fresh-review commands do not start repair, autofix, rebase, CI repair, or automerge.
Maintainer-only repair and merge flows require explicit commands such as @clawsweeper autofix, @clawsweeper automerge, @clawsweeper fix ci, or @clawsweeper address review.
Maintainers can comment @clawsweeper explain to ask for more context, or @clawsweeper stop to stop active automation.

Uh oh!

gog sheets should support creating filters (setBasicFilter) #899

Description

Metadata

Metadata

Assignees

Labels

Type

Fields

Projects

Milestone

Relationships

Development

Issue actions

gog sheets should support creating filters (`setBasicFilter`) #899