Harness Recursive Command

Syntax

Invoke this command in runtimes that support markdown-backed command entrypoints, for example /hforge-recursive followed by the investigation goal, task id, or the specific recursive structured-analysis step you want to run.

Expected workflow

1. resolve command execution through .hforge/generated/bin/hforge(.cmd|.ps1) first, bare hforge second, and npx @harness-forge/cli last
2. run hforge recursive capabilities --root . --json before claiming language support
3. run hforge recursive runtimes --root . --json before assuming Python or PowerShell code-cell availability
4. use hforge recursive provision-runtime <python|powershell> --root . --json only when a workspace-managed runtime alias is genuinely needed
5. create or inspect a session with hforge recursive plan ... --root . --json or hforge recursive inspect <sessionId> --root . --json
6. submit typed recursive action bundles with hforge recursive execute <sessionId> --file <bundle.json> or --stdin when the task fits Typed RLM
7. submit structured analysis with hforge recursive run <sessionId> --file <snippet> or --stdin when a bounded snippet is the right tool
8. inspect durable results with hforge recursive iterations <sessionId> --root . --json, hforge recursive subcalls <sessionId> --root . --json, hforge recursive cells <sessionId> --root . --json, hforge recursive promotions <sessionId> --root . --json, hforge recursive meta-ops <sessionId> --root . --json, hforge recursive score <sessionId> --root . --json, and hforge recursive replay <sessionId> --root . --json

Failure behavior

• if the current language is not supported, say so explicitly and fall back to non-recursive investigation
• do not imply recursive-native parity on partial targets; keep support claims aligned with the capability map
• treat Cursor and OpenCode recursive RLM posture as translated shared-runtime support rather than native target parity