Hey, great breakdown of your workflow, a lot of it sounds solid. A couple thoughts on your questions.
About auto Agent Review after a commit. You’re on Cursor 3.1.17, which is a pretty old build. There was an issue where Agent Review wouldn’t trigger with an error like “commit not found” in workspaces with multiple repos, and it’s already fixed in newer versions. Update Cursor to the latest version and try again: Cursor Settings > Agents > enable auto-run after task or commit. If it’s still silent after the update, share the Request ID and a screenshot of your settings and we can look into it.
While you’re updating, you can run review manually:
/agent-reviewright in the agent panel- from the Source Control tab, it compares all local changes against main
- you can pick depth: Quick for small diffs, Deep for complex logic and refactors
About the code review workflow overall. Besides /code-review, it helps to connect two levels:
- Agent Review runs locally before push, catches issues early
- Bugbot runs on the PR stage, integrates with GitHub or GitLab, leaves inline comments, and can autofix
There’s a good write-up on the difference and when to use each here: Difference between Bugbot and Agent review Difference between Bugbot and Agent review?. Also, Agent Review reads rules from BUGBOT.md in the repo, so you can set your own review criteria for your Qt/C++ style to reduce that “noise”.
About the subagent pattern. Delegating to a subagent to keep the main context clean is a solid idea. For a code-reviewer subagent, you can set model: inherit so you’re not tied to a specific model. Docs: subagents Subagents | Cursor Docs, agent review Agent Review | Cursor Docs.
Update your version and let me know if auto-review starts working.