A second look before posting
Every finding is checked again against the code around it, where it is used, the commit messages and what the author said on the pull request. Findings that context contradicts are dropped instead of posted.
What shipped in Grapim, newest first.
Every finding is checked again against the code around it, where it is used, the commit messages and what the author said on the pull request. Findings that context contradicts are dropped instead of posted.
Cloud review no longer posts a finding again when it already commented on it earlier in the same pull request. The summary says how many are still there, and a blocker that is still there still fails the check.
Write @grapim in a comment to ask about a finding or the change, and the answer appears in the thread. @grapim review runs a fresh review.
Thumbs up and down on Grapim’s comments, and your team’s replies to them, now guide the next reviews in the repository. Nothing extra is stored.
Install the GitHub App on a public repository and every pull request gets a cloud review, free, with no account to create. Teams with cloud review on no longer spend credit on their public repositories. Pull requests opened by bots are skipped.
Turn on Cloud review in Settings, GitHub and Grapim reviews every pull request on its own model account, with nothing to set up in CI. A review takes about a minute and posts comments and a Grapim Review (cloud) check. Each plan includes a monthly review credit.
Each finding now carries a confidence. Sure ones are posted on the line, doubtful ones are listed once in the summary under Worth a look. A repository without Grapim notes gets every changed line reviewed.
Files a Cursor agent changes with a shell command (a migration, an rm, a codegen script) now belong to its run, so grapim undo can take them back like any other edit. Run grapim init again to add the hook.
For Claude Code, Codex and Gemini CLI, Grapim compares the worktree before and after each shell command, records every file it created, changed or deleted, and names the command in the run.
A run that only touches tests or docs can pass on its own, with the rule and the person who set it on record. Runs that touch payments, auth or migrations still wait for the reviewer you named. New teams can start from a starter set.
Turn it on and the hub keeps run records, line counts and hashes, never file contents. When someone opens a run, the diff is read from GitHub for that view and not saved.
See which coding agents, versions, models and MCP servers your team’s machines run, and which appeared this week. Only names, transports and hosts are collected.
An assistant in the hub that answers questions about your team’s runs, reviews and reports, and prepares an approval or an invite for you to confirm. It can read what you can read and changes nothing on its own.
Every coding-agent run recorded on the machine: the agent, each prompt, the files and lines it changed. grapim undo takes one run back out and keeps everyone else’s work.
Each pull request gets a comment listing its agent runs, and a check that blocks merging until every run is approved.
Agents that write documents or data, not code, get a shared folder on the hub. Every write is recorded, reviewable and undoable.