oy
Focused OpenCode and Cursor integrations with repeatable audits, code reviews, and one-finding fixes.
oy helps OpenCode or Cursor review a repository without quietly choosing a small sample. It prepares an ordered, reviewable set of files, lets the model analyze them under the host's existing permissions, and verifies the report before writing it.
What you get
oy auditfor security-focused repository audits (ISSUES.mdor SARIF)oy reviewfor whole-workspace or target-diff code reviews (REVIEW.md)oy enhancefor fixing one reported finding at a time- one concise
oycoding agent plus/oy-audit,/oy-review, and/oy-enhanceinside OpenCode or Cursor
OpenCode or Cursor still owns models, credentials, permissions, sessions, edits, shell commands, and web access. oy adds the evidence and report workflow; it is not a second agent runtime or permission system.
Quick start
Requirements: Linux or macOS (WSL2 on Windows), oy on PATH, and either a supported OpenCode 2 or Cursor installation with a configured model provider.
# OpenCode 2 (default)
|
# Restart your shell if the installer asks you to.
# Cursor CLI plus the global oy Cursor integration
|
# Or install both hosts and integrations
|
The installer uses mise for prebuilt oy and context helpers. The OpenCode target provisions Node.js and OpenCode's documented npm package; the Cursor target uses Cursor's official CLI installer because Cursor has no official mise package. Review the installer before piping it to a shell.
Prefer a manual install or project-local setup? See Getting started.
Common workflows
Audit a repository
A single argument that exactly matches a workspace path narrows collection. Other text is treated as review guidance.
Review code
A branch, commit, tag, or ref selects target-diff review. Without a target, oy reviews the workspace.
Fix one finding
# Confirm the result by rerunning the originating workflow.
Reports include stable finding IDs. oy enhance confirms the cited source, makes one focused fix, and runs the narrowest available verification.
You can run the same workflows inside OpenCode or Cursor with /oy-audit, /oy-review, and /oy-enhance.
How repeatable review works
- Prepare: oy collects eligible repository text or a Git diff into ordered files under
.oy/runs/. - Review: the selected agent host reads every prepared chunk and writes a candidate report.
- Verify: oy rejects changed inputs, modified evidence, concurrent report changes, or malformed findings.
- Finalize: oy writes normalized Markdown or SARIF with stable finding metadata.
The inputs are deterministic; the conclusions are not. Model choice and prompt quality still affect findings.
“Every chunk” means every chunk collected by oy, not every byte in the repository. The collector excludes ignored/hidden paths, dependencies and build output, lockfiles, likely secrets, binary or unreadable files, and files larger than 512 KiB. See Coverage and limits before using a report for high-assurance work.
Safety
oy is not a sandbox. Prepared source may be sent to your configured model provider, and the oy agent uses your effective host permissions. Use a disposable environment for untrusted repositories and read SECURITY.md.
Documentation
- Getting started — install, configure, and create a first report
- Workflow guide — scopes, findings, remediation, and limits
- Examples and CI — report examples and SARIF upload
- CLI reference — commands, environment variables, and setup ownership
- Compatibility — supported platforms and agent hosts
- Architecture and contributing — maintainer documentation
Run oy <command> --help for the installed version's exact flags.