Skip to content

release: autter 3.14.0 + VS Code extension 0.2.0 — autter findings, autter review, findings in the editor - #110

Merged
sagnik11 merged 4 commits into
mainfrom
claude/focused-sagan-at64y1
Nov 17, 2026
Merged

sagnik11 merged 4 commits into
mainfrom
claude/focused-sagan-at64y1

Conversation

@sagnik11

@sagnik11 sagnik11 commented Nov 17, 2026 •

Copy link
Copy Markdown
Member

CLI and VS Code half of "Findings in the editor": developers had to switch to the dashboard to see findings, and only learned of issues once a PR existed. Needs the backend from Autter-dev/autter-monorepo#774 deployed first.

Release: bumps Cargo.toml/Cargo.lock to 3.14.0 (main already shipped 3.13.0 with autter tests), with a [3.14.0] CHANGELOG section. On merge, tag-release.yml tags v3.14.0 and release.yml publishes. The VS Code extension goes to 0.2.0; publishing it needs a vscode-v0.2.0 tag on the merge commit.

autter findings (Phase 1)

Prints the findings of the current branch's open PR, from GET /api/cli/orgs/:slug/findings, using autter ask's sign-in and org choice. --branch and --pr pick another PR.

Line numbers follow the developer's edits:

  • Findings are tied to the commit Autter reviewed. The command runs git diff -U0 --no-renames <reviewed sha> against the working tree and moves each line by the lines added or removed above it.
  • A finding whose own line changed since the review is reported as changed, with no line, so nothing points at code the review never saw.
  • A missing reviewed commit is fetched from refs/pull/<n>/head, never prompting for credentials and capped at 30 s. --no-fetch skips this. If it's still missing, findings are reported as unverified.

Output:

  • --write keeps .autter/findings.md up to date: a summary, location, next steps and link for each finding. It adds /.autter/ to .git/info/exclude, and the file only changes when the findings do.
  • --json adds local: {status, line} to each finding.

autter review (Phase 2)

Reviews what a PR from this branch would contain before one exists: the diff from the merge base with the default branch, committed or not, untracked files included. Also accepts --uncommitted, --base <ref> or paths.

  • Request: sent to POST /api/cli/orgs/:slug/review, which streams JSON lines. Up to 60 files and 3 MB; files over 200 KB go as a patch only.
  • Snapshot: each reviewed file is saved as a git blob before it's sent. .autter/local-review.json keeps the result and the blob ids.
  • Later reads: autter findings attaches the saved review as localReview for the branch it was made on, and places each finding by diffing the reviewed blob against the file as it is now. Same rule as PR findings.

VS Code extension 0.2.0

  • Findings: shown as diagnostics (squiggles and Problems) with an optional after-line annotation, set by autter.findings.display: inline, problems or off.
  • Quick fixes: copy the fix prompt, open the finding in the dashboard, or dismiss it.
  • Refreshes on startup, on save (debounced), on branch change, on focus, and every 5 minutes.
  • Edits between saves: placements follow them, and editing a finding's line drops it.
  • Status bar: shows the count. When signed out it reads autter: Sign in and runs autter login in a terminal.
  • Autter: Review My Changes saves all files and runs autter review --json --write under a cancellable progress notification. Local findings are labelled "local review".
  • Lockfile: package-lock.json was out of sync with package.json (dependency bumps since 0.1.25), which would fail npm ci in the publish workflow. Refreshed with npm install --package-lock-only.

Testing

  • CLI unit tests (16):
    • option parsing
    • diff and hunk parsing, including a removed -- line and C-quoted paths
    • line mapping against hand-written and real git diff output
    • a real-repo test of local review placement and branch scoping
    • markdown rendering
    • stream parsing
  • CLI checks: help_flag_safety integration tests pass with the new commands, before and after merging main. Clippy with --all-targets -D warnings is clean for these changes; this toolchain (1.97) also reports lints in files this PR doesn't touch. rustfmt --check passes on the changed files.
  • End to end against a mock API with real git repos:
    • placement after edits
    • signed-out and server-down errors
    • .autter/ excluded from git
    • a committed + uncommitted + untracked review request
    • local findings after later edits (moved, changed, file_deleted)
  • Extension: tsc and eslint are clean, and 6 mocha tests cover the model: output parsing, placement, edit tracking and status text.
  • Not tested here: the extension inside a real VS Code (the VS Code download is blocked in this environment), and a run against a live backend.

🤖 Generated with Claude Code

https://claude.ai/code/session_01TtUpr8sH39LAcxNTh4QreC

… in VS Code

`autter findings` reads GET /api/cli/orgs/:slug/findings for the current
branch's open pull request (or --branch / --pr) with the sign-in and org
choice of `autter ask`, and prints the findings most severe first.

Findings are anchored to the commit the review ran on. The command runs
`git diff -U0 --no-renames <reviewed sha>` against the working tree and
moves each line by the lines added or removed above it; a finding whose
own line changed since the review is reported as `changed` with no line,
so nothing points at code the review never saw. A missing reviewed commit
is fetched from refs/pull/<n>/head without credential prompts (30 s cap,
--no-fetch skips it); otherwise findings are `unverified`.

--write keeps .autter/findings.md (summary, location, next steps, link,
grouped into in-your-code / changed-since-review / about-the-PR) and adds
/.autter/ to .git/info/exclude. The file carries no run time, so it only
changes when the findings do. --json adds `local: {status, line}` per
finding.

VS Code extension: a FindingsManager runs `autter findings --json --write`
on startup, on save (debounced), on branch change, on focus and every
5 minutes, and shows findings as diagnostics (Problems + squiggles) with
an optional after-line annotation (autter.findings.display). Placements
follow edits until the next save; editing a finding's line drops it.
Quick fixes copy a fix prompt, open the finding in the dashboard or
dismiss it. The status bar shows the count, or "Sign in", which runs
`autter login` in a terminal.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01TtUpr8sH39LAcxNTh4QreC
`autter review [<path>...] [--base <ref> | --uncommitted] [--write] [--json]`
sends what a PR from this branch would contain — the diff from the merge
base with the default branch (origin/HEAD, else main/master) to the working
tree, untracked files included — to POST /api/cli/orgs/:slug/review, and
reads the streamed JSON lines for the result. Up to 60 files / 3 MB; files
over 200 KB go as a patch only.

Each reviewed file is written to the object DB first (`git hash-object -w
--stdin-paths`) and its content read back from that blob, so the review and
later line mapping see the same bytes. The result and the blob ids are kept
in .autter/local-review.json. `autter findings` now attaches it as
`localReview` for the branch it was made on, placing each finding by
diffing the reviewed blob against the file now (moved / changed /
file_deleted), the same rule as PR findings: nothing is shown on a line the
review didn't see.

findings.md now has a "Pull request review" and a "Local review" section;
items are separated by one blank line; a no-PR branch points to
`autter review`.

VS Code: "Autter: Review My Changes" saves all files, runs
`autter review --json --write` under a cancellable progress notification,
then refreshes; local findings are placed with the PR's, labelled "local
review" in the Problems code and the inline annotation.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01TtUpr8sH39LAcxNTh4QreC
Cargo.toml / Cargo.lock 3.12.0 → 3.13.0 so tag-release tags v3.13.0 on
merge. CHANGELOG entry for `autter findings` and `autter review`.

VS Code extension 0.1.25 → 0.2.0 with a CHANGELOG entry. Its
package-lock.json was out of sync with package.json (dependency bumps
since 0.1.25 never reached it), which fails `npm ci` in the publish
workflow; refreshed with `npm install --package-lock-only`.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01TtUpr8sH39LAcxNTh4QreC
… 3.14.0

main released 3.13.0 (autter tests, #111), so this branch's release is
3.14.0: Cargo.toml / Cargo.lock bumped, the findings/review entries moved
into a new [3.14.0] CHANGELOG section, and the VS Code extension 0.2.0
now names autter 3.14.0 as its minimum.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01TtUpr8sH39LAcxNTh4QreC
@sagnik11 sagnik11 changed the title autter findings + autter review: review findings in VS Code, and before the PR release: autter 3.14.0 + VS Code extension 0.2.0 — autter findings, autter review, findings in the editor Nov 17, 2026
@sagnik11
sagnik11 merged commit 8f5c26f into main Nov 17, 2026
7 of 8 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.

2 participants