---
title: openplanr 1.5.0
description: "Published 2026-04-29. Multi-runtime rules: extend openplanr rules generate with a --scope flag for cross-runtime pipeline support."
url: https://openplanr.dev/docs/changelog/1.5.0
updated: 2026-04-29
related:
  - https://openplanr.dev/docs/changelog/1.5.2.md
  - https://openplanr.dev/docs/changelog/1.5.1.md
  - https://openplanr.dev/docs/changelog/1.4.3.md
---

# openplanr 1.5.0

Published 2026-04-29.

[Release on GitHub](https://github.com/openplanr/OpenPlanr/releases/tag/v1.5.0)

## Minor Changes

Multi-runtime rules: extend `openplanr rules generate` with a `--scope` flag for cross-runtime pipeline support.

`openplanr rules generate` now accepts `--scope <agile|pipeline|all>` (default: `agile` — preserves existing behaviour byte-for-byte). The new `pipeline` scope generates rule files that drive the openplanr-pipeline two-phase spec-driven flow on the chosen runtime, giving Cursor and Codex first-class parity with the Claude Code plugin.

**Cursor (`--target cursor --scope pipeline`):**

- `.cursor/rules/openplanr-pipeline.mdc` — master rule (mode detection, R1 human gate, runtime parity notes)
- `.cursor/rules/openplanr-pipeline-plan.mdc` — PO Phase orchestration (Composer subagent dispatch)
- `.cursor/rules/openplanr-pipeline-ship.mdc` — DEV Phase orchestration (parallel subagents, qa gate, snapshot, marker)
- `.cursor/rules/agents/{db,designer,specification,frontend,backend,qa,devops,doc-gen}-agent.md` — 8 role bodies vendored verbatim from `openplanr-pipeline/agents/` (frontmatter stripped; Cursor uses different permission model)

**Codex (`--target codex --scope pipeline`):**

- `AGENTS.md` extended with a `## OpenPlanr Pipeline Orchestration` section. Roles modelled as personas (Codex doesn't have separate subagent processes); R1, R2, R5, R6, R8, R9 declared at prompt level with conformance-test enforcement.

**Claude (`--target claude --scope pipeline`):**

- `CLAUDE.md` gets a conditional `## OpenPlanr Pipeline (Path A)` block under `{{#if pipelineScope}}`
- Sibling `openplanr-pipeline.md` reference card with install commands, slash command list, and cross-runtime pointer

`--scope all` produces both agile and pipeline rules side-by-side.

**Compatibility matrix and OpenPlanr Protocol v1.0.0** documented in `openplanr-pipeline/docs/protocol/` and `openplanr-pipeline/docs/compatibility-matrix.md` (pipeline plugin v0.6.0+).

**`openplanr init` now auto-generates pipeline rules by default.** The init flow asks "Generate openplanr-pipeline rules?" with default `Yes` — meaning a single `openplanr init` produces a complete, ready-to-use cross-runtime project (Cursor + Codex pipeline rules pre-installed; Claude Code skill activates the same workflow via the plugin). Opt out with `openplanr init --no-pipeline-rules` to preserve the previous agile-only behaviour. This closes the cross-runtime DX gap so each tool (Cursor, Codex, Claude Code) is self-sufficient after a single command — no manual `openplanr rules generate --scope pipeline` step required for the common case.

**Migration:** none. Existing projects can either re-run `openplanr init` (it auto-detects existing config and asks to overwrite) or run `openplanr rules generate --scope all` to add pipeline rules without touching config. `--scope agile` (the previous default for `openplanr rules generate`) keeps producing the existing 6 Cursor `.mdc` files, single CLAUDE.md, single AGENTS.md outputs unchanged.
