oy-cli 0.14.1

Focused coding agent integrations with repeatable audits, reviews, and one-finding fixes
Documentation 
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81

# Compatibility

## Platforms

| Environment | Support |
|---|---|
| Linux x86_64 with glibc | Full CI and release archive |
| Linux aarch64 with glibc | Release archive; full suite not run on target |
| macOS Apple Silicon | Release archive; full suite not run on target |
| Other Linux/macOS targets | Source build; not release-tested |
| Windows | Use WSL2; native Windows is unsupported |
| Other operating systems | Unsupported at build time |

The installer requires a POSIX shell plus `curl` or `wget`. Its prebuilt oy release supports the three release-archive targets above; other Linux/macOS targets require a source build. Building from source requires Rust 1.96+. The npm plugin declares Linux and macOS support.

## OpenCode

oy 0.14.1 accepts:

| OpenCode host | Status |
|---|---|
| Current `0.0.0-next-*` channel | Installer default during the V2 beta |
| Tagged OpenCode 2.x | Accepted |
| Other prerelease channels | Rejected |
| OpenCode 1, major versions above 2, or unknown versions | Rejected |

The default executable is `opencode2`. `OY_OPENCODE` can select another executable, but it must report a supported version.

During the V2 beta, installation runs the upstream-documented `npm install -g @opencode-ai/cli@next` under mise's latest Node.js. The `@oy-cli/opencode` plugin is dependency-free and uses only the documented plugin context, so it does not track a moving SDK channel. This keeps new installs current but means an upstream beta change can break compatibility between oy releases. Restart OpenCode after either package changes.

Once OpenCode 2 is stable, oy will switch these references to the stable `latest` channel and remove the beta-specific compatibility path in a follow-up release.

## Cursor

`oy setup --cursor` uses Cursor's native rule, subagent, and Agent Skill file formats. The integration does not install a Cursor extension or MCP server. Skills invoke the local `oy audit|review prepare` and `finalize` commands through Cursor's existing terminal tools and permissions.

Cursor does not support a file-defined replacement for its primary Agent. Oy therefore installs an always-applied `oy` rule for primary behavior and a separate `oy` subagent for explicit delegation.

`install.sh --cursor` installs the standalone `agent` CLI with Cursor's supported `https://cursor.com/install` installer on Linux, macOS, and WSL. Cursor has no official mise registry entry, npm package, documented release index, or stable artifact URL suitable for a maintained mise backend. Oy deliberately does not use the unversioned third-party asdf/mise plugin.

## What `doctor --check` covers

```bash
oy doctor --check
```

This checks the effective service version, API, location, plugin, `oy` agent, three skills, three commands, models, and providers. It does not validate your permission choices or make a paid/provider-backed model request.

## Setup locations

- OpenCode global: `OPENCODE_CONFIG_DIR`, or the platform OpenCode config directory
- OpenCode workspace: `OY_ROOT/.opencode/`
- OpenCode preferred config file: existing `opencode.jsonc`, otherwise `opencode.json`
- Cursor global: `~/.cursor/`
- Cursor workspace: `OY_ROOT/.cursor/`

Setup preserves unrelated configuration and backs up changed oy-owned entries. See [Setup ownership and backups](reference.md#setup-ownership-and-backups).

## Optional tools

`tokei` and Universal Ctags are optional context helpers. Missing them does not block setup, audit, review, or remediation. Install them with:

```bash
oy doctor --install-missing
```

The helper installs prebuilt artifacts only: tokei 12.1.2 through mise's Aqua backend and Universal Ctags release archives from the official nightly-build repository.

On a Cursor-only workstation, install these optional binaries separately if wanted; `doctor --install-missing` also provisions the supported OpenCode runtime.

## Reporting a compatibility problem

Include:

- `oy --version`;
- the selected OpenCode executable and its `--version` output;
- operating system and architecture;
- install method and setup scope;
- reviewed and redacted `oy doctor --json` output.

Use [OpenCode troubleshooting](https://v2.opencode.ai/troubleshooting) for service/provider issues. Do not include credentials, prompts, or sensitive source text.