Supported Coding Agents

Ranger Feature Review works with any coding agent that can run bash commands. The table below shows what’s supported out of the box and links to the setup instructions for each agent.

Agent	Plugin	Skills	Setup Command
Claude Code	Yes (`ranger@trailhead`)	`.claude/skills/`	`ranger setup`
OpenCode	Yes (`@ranger-testing/opencode-plugin`)	`.opencode/skills/`	`ranger setup --opencode`
Cursor	No	`.cursor/skills/` (via sym link)	`ranger setup`
Codex	No	`.codex/skills/` (via sym link)	`ranger setup`
Other agents	No	directory of choice (via sym link)	`ranger setup`

In the setup instructions below, we provide commands to sym link the skills into the appropriate directory. It will also work to copy or move them, but the ranger update command will automatically update the skills to match new CLI versions and sym linking allows those updates to be immediately picked up by your coding agent.

Claude Code

Claude Code is Ranger’s primary integration. The ranger setup command installs a Claude Code plugin and skills automatically.

Quickstart: Follow the full Quickstart guide.

What you get:

Plugin — Connects Ranger to Claude’s hook system. Ranger can automatically activate at the right moments in your workflow.
Skills — Markdown files installed to .claude/skills/ that teach Claude how to create feature reviews, run verifications, and address feedback.
Slash commands — /ranger:enable, /ranger:disable, and /ranger:resume for quick control.

OpenCode

OpenCode has its own plugin and skill paths. Use the --opencode flag during setup.

Quickstart: Follow the OpenCode Quickstart guide.

What you get:

Plugin — The @ranger-testing/opencode-plugin package, configured in your opencode.json.
Skills — Markdown files installed to .opencode/skills/.
Natural language activation — Tell your agent to “enable ranger” instead of slash commands.

Cursor

Cursor 2.4+ reads .claude/skills/ for compatibility, so Ranger default setup installation should be picked up automatically. On earlier versions, or for consistency with other skills, it can be linked into the .cursor/skills directory:

ln -s ~/.claude/skills/ranger ~/.cursor/skills/ranger

The skills work without a plugin, but you may have to remind the agent to use it after compaction or later in the context window.

Invoke the skill with /ranger or @ranger in Cursor’s Agent chat (e.g. “Use @ranger to create a feature review and verify it”).

Codex

Codex reads .claude/skills/ (and .codex/skills/), so Ranger default setup installation should be picked up automatically. On earlier versions, or for consistency with other skills, it can be linked into the Codex skills directory:

ln -s ~/.claude/skills/ranger ~/.codex/skills/ranger

Codex’s default permissions mode blocks most network access, so Ranger will fail until permissions are adjusted. For an individual session, the slash command /permissions will allow you to update to Full Access.

For a more enduring fix, you can add Ranger and network permissions by default:

echo 'prefix_rule(pattern=["ranger"], decision="allow")' >> ~/.codex/rules/default.rules

and update ~/.codex/config.toml with:

sandbox_mode = "workspace-write"

[sandbox_workspace_write]
network_access = true

Other Agents

Any coding agent that can execute bash commands can use Ranger. The core workflow is:

Install CLI and authenticate: npm install -g @ranger-testing/ranger-cli && ranger setup
Install skills: Say yes when prompted, or run ranger skillup separately. Skills are installed to .claude/skills/ranger/ by default.
(optional) Link skills: if your agent looks for skills in a specific directory, sym link the ranger skill into that directory.
Use the CLI: Your agent runs ranger create, ranger go, ranger show, etc.

The skill files are plain markdown — they work as instructions for any LLM-based agent.