Skip to content

remora v0.1.7

Choose a tag to compare

@github-actions github-actions released this 13 Jul 15:12
bfb335c

Codex runtime-catalog hot update resilience

remora v0.1.7 is a focused context hotfix. CLIProxyAPI and the bundled Codex catalog can temporarily keep an older 372K value after the ChatGPT-authenticated Codex runtime catalog changes GPT-5.6 Sol, Terra, and Luna to 272K. Previous Calico sessions trusted the gateway value alone and could exceed the backend's actual context window.

This release keeps the two authorities visible and uses the smaller per-model value for the Calico client:

provider_window=372000
codex_window=272000
client_window=272000
effective_window=258400
auto_compact_window=272000
compact_policy=exact:244800

Included changes

  • Read fresh context metadata from the local Codex models_cache.json; no Codex auth files are opened.
  • Keep CLIProxyAPI's catalog as a separate gateway diagnostic ceiling.
  • Fall back conservatively to 272K when the Codex cache is missing, older than its 300-second TTL, or incomplete.
  • Restore a later fresh 372K runtime value automatically; 272K is not a permanent model pin.
  • Cap explicit Calico compact-window overrides to the resolved client ceiling.
  • Report gateway, Codex runtime, and final Calico model windows separately in remora doctor --online.
  • Update the bilingual context, gateway, architecture, installer, and security documentation.

This release does not include the draft Baton-inspired orchestration work in PR #1. That work remains independently gated for v0.1.8.

Verification

make check passed 29 Python tests, including 372K → 272K capping and a later fresh 372K rollback, plus installer isolation, bootstrap/package, Python and shell syntax, and dry-run checks. make package completed and the archive contents were inspected.

A real non-persistent Calico/gateway request completed successfully on gpt-5.6-sol, returned REMORA_CONTEXT_SMOKE_OK, and reported contextWindow: 272000. The live doctor also confirmed the Codex active-turn bridge remained protocol v1 ready.

The GitHub release workflow rebuilt the archive, published checksums.txt, and attached build-provenance attestation.

Upgrade

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

Read and follow this installation runbook:
https://raw.githubusercontent.com/Nanako0129/remora-cc/v0.1.7/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. A resumed session may retain its previous context and agent definitions.

Full Changelog: v0.1.6...v0.1.7