guren-harnesslisted

# Guren Harness Guren ships its agent harness inside the app's own `@guren/cli`, installed by `guren agent:init` and refreshed by `guren agent:sync`. This skill gets that installed and tells you how to use it. The installed harness — the rules directory, the entry document, the hooks — is authoritative once present; this skill is the on-ramp to it, not a replacement. ## Detect a Guren app Positive evidence only: a `package.json` here (or in a parent) whose `dependencies` or `devDependencies` include `@guren/core`. If there is none, stop and use the `guren-new-app` skill. If the dependencies are declared but `node_modules/@guren/cli` is missing, run `bun install` first — nothing below works without it. ## Probe the CLI version before installing Run: ```bash bunx guren --version ``` Multi-agent targets need `@guren/cli` __MIN_CLI__ or newer. Older CLIs **silently ignore** an unrecognized `--target` flag: `agent:init --target codex,cursor` on such a CLI installs a Claude-only harness, prints "AI agent harness is ready", and exits 0. A fallback keyed on a non-zero exit would report multi-agent success that never happened, so decide from the version first: - Version parses and is ≥ __MIN_CLI__ → proceed with `--target`. - Version is older, **or `--version` itself fails or prints no version** (a CLI older still) → treat as older than __MIN_CLI__: run plain `bunx guren agent:init` (Claude-only), and tell the user that multi-agent targets need `@guren/cli` ≥ __MIN_CLI__