Codex usage limits have been reached for code reviews. Please check with the admins of this repo to increase the limits by adding credits.
Repo admins can enable using credits for code reviews in their settings.

Confirmed main's unsloth_cli/commands/start.py still resolves only opencode and injects a root --model, so the V2 routing here fills a real gap. Could you keep .github/scripts/agent-guides-install.sh covering the stable opencode-ai install as well instead of replacing it with the beta package?

Confirmed main's unsloth_cli/commands/start.py still resolves only opencode and injects a root --model, so the V2 routing here fills a real gap. Could you keep .github/scripts/agent-guides-install.sh covering the stable opencode-ai install as well instead of replacing it with the beta package?

@danielhanchen done.
Updated in 150324f and d49840c. The install script defaults to stable opencode-ai, and the connection matrix has a separate V2 cell. That V2 cell uses @opencode-ai/cli@beta only while @opencode-ai/cli@latest does not expose the opencode2 binary; it automatically switches to @latest when V2 is released as stable. This preserves V1 coverage without permanently pinning V2 to beta.

Addressed the runtime review findings in 0fdf8da:

• V2 no longer emits an ineffective provider-policy override; global/project policy remains authoritative and the CLI states that unsloth-studio must be allowed. An inherited inline allowlist is still extended at its own level so it does not block the local subagent.
• V2 no longer forces experimental.subagent_depth to 1, preserving global/project depth.
• Server-backed V2 commands (api, models, export, import, mini, run) now receive --standalone so the generated config reaches their server.
• --no-launch now detects opencode2 in the official ~/.opencode/bin location without installing anything.

Validation: 73 targeted OpenCode tests, pre-commit hooks, Python compilation, workflow lint, and a real opencode2 models --standalone smoke.

Thanks — I tested this at 0fdf8dad with a clean Studio/OpenCode V2 install and reproduced two issues:

• with official V2 only in ~/.opencode/bin, normal launch works, but the exact --no-launch recipe fails with opencode2: command not found until PATH is changed;
• the guide path builds opencode2 --standalone run ..., which the beta CLI rejects (it expects run --standalone).

Repros: https://github.com/wasimysaid/unsloth/actions/runs/32264293049 and https://github.com/wasimysaid/unsloth/actions/runs/32264440159. Could you re-check both command-building paths and add coverage? The private-server/models and provider-policy behavior worked for me.

Fixed both paths in b38bf61. The V2 resolver now preserves the absolute ~/.opencode/bin/opencode2 path in --no-launch output, so the printed recipe no longer depends on PATH. Explicit V2 subcommands now place --standalone after the subcommand (opencode2 run --standalone ...), and the guide driver repositions the bare recipe's flag when it appends
un. Added focused CLI and guide-driver coverage; the OpenCode V2 tests and repository pre-commit hooks pass.

@codex review

Codex Review: Didn't find any major issues. 🚀

Reviewed commit: c31aa8d58a