Skip to content

remora v0.1.6

Choose a tag to compare

View all tags
@github-actions github-actions released this 13 Jul 10:00
v0.1.6
d2ad6e5

Role-owned model routing

remora now makes the Agent invocation boundary explicit: every existing named role must be invoked without a model argument. Its session-scoped --agents definition is the sole model source.

This fixes the precedence failure where a per-call alias such as sonnet could override the configured role map—for example, turning a Luna executor into Terra despite remora agents showing Luna. Only a truly ad-hoc agent with no named role definition receives an explicit invocation model.

Included changes

  • Named Explore, scout, mech-executor, executor, verifier, and security-executor calls omit invocation-level model.
  • The same rule applies to any other existing named role definition; its definition remains authoritative.
  • Truly ad-hoc agents still set model explicitly so they do not inherit Sol accidentally.
  • The contract is child-session-only and does not modify native Claude settings, CLIProxyAPI, or Calico.
  • English and Traditional Chinese model-routing documentation now explains Claude Code's invocation-over-frontmatter precedence.
  • The approval-gated installer reports the model-ownership contract before installation.
  • Regression tests verify both named-role ownership and the ad-hoc exception alongside the existing model allowlist, session isolation, background scheduling, context, and active-turn checks.

Verification

make package passed 24 unit tests, clean-room installer isolation, checksum and archive-safety bootstrap tests, Python and shell syntax checks, dry-run secret redaction, and release packaging. The GitHub release workflow rebuilt the archive, published checksums.txt, and attached build-provenance attestation successfully.

The maintainer installation was also updated to remora 0.1.6; the existing config.toml and native ~/.claude path manifest were preserved.

Upgrade

Use the pinned, approval-gated v0.1.6 runbook:

Read and follow this installation runbook:
https://raw.githubusercontent.com/Nanako0129/remora-cc/v0.1.6/install/AGENT-INSTALL.md

Perform only the read-only preflight first. Show every proposed filesystem
change, trust boundary, download source, and verification step. Do not write
anything until I explicitly approve.

After upgrading, start a fresh remora session so it receives the new orchestration policy. A resumed old session may retain its previously recorded session definitions and instructions.

Full Changelog: v0.1.5...v0.1.6

Assets 4
Loading