Problem Statement
Currently OCR only supports Claude Code and a skills registry (npx skills add) for agent integrations. There is no native Cursor plugin, which makes day-to-day adoption harder for developers who primarily use Cursor or any other vibe-coding platforms as their IDE. To trigger a review, users have to switch to a terminal and run ocr review manually — breaking the development flow. Tools like compound-engineering have shown that a native Cursor plugin (installable via /add-plugin or the Cursor marketplace) significantly lowers the friction for daily use.
Proposed Solution
A Cursor plugin that exposes OCR as a slash command directly inside Cursor Agent chat, similar to how Claude Code integration works today. Ideally:
- Installable via Cursor's plugin marketplace or
/add-plugin open-code-review
- Slash command like
/ocr:review triggering a diff review of current changes
- Reads existing
.opencodereview/rule.json project rules automatically
- Works with any configured LLM backend (Anthropic, OpenAI, or local Ollama/LM Studio)
What I tested
Tested OCR with qwen2.5-coder-7b-instruct via LM Studio on a FastAPI project. Review quality and the ocr viewer browser output were genuinely impressive — line-level comments, cross-file reasoning, structured findings. The core tool is solid. The missing piece is editor integration for daily workflow.
Workaround I'm currently using
Copying the Claude Code command file into .cursor/rules/ as an .mdc file. It partially works but is not as seamless as a native plugin.
Additional context
Would be happy to test a beta plugin if one is in development. This would make OCR a strong choice for Cursor users over alternatives that have weaker review depth but better editor integration.
Affected Area
Configuration
Additional Context
No response
Problem Statement
Currently OCR only supports Claude Code and a skills registry (
npx skills add) for agent integrations. There is no native Cursor plugin, which makes day-to-day adoption harder for developers who primarily use Cursor or any other vibe-coding platforms as their IDE. To trigger a review, users have to switch to a terminal and runocr reviewmanually — breaking the development flow. Tools like compound-engineering have shown that a native Cursor plugin (installable via/add-pluginor the Cursor marketplace) significantly lowers the friction for daily use.Proposed Solution
A Cursor plugin that exposes OCR as a slash command directly inside Cursor Agent chat, similar to how Claude Code integration works today. Ideally:
/add-plugin open-code-review/ocr:reviewtriggering a diff review of current changes.opencodereview/rule.jsonproject rules automaticallyWhat I tested
Tested OCR with
qwen2.5-coder-7b-instructvia LM Studio on a FastAPI project. Review quality and theocr viewerbrowser output were genuinely impressive — line-level comments, cross-file reasoning, structured findings. The core tool is solid. The missing piece is editor integration for daily workflow.Workaround I'm currently using
Copying the Claude Code command file into
.cursor/rules/as an.mdcfile. It partially works but is not as seamless as a native plugin.Additional context
Would be happy to test a beta plugin if one is in development. This would make OCR a strong choice for Cursor users over alternatives that have weaker review depth but better editor integration.
Affected Area
Configuration
Additional Context
No response