Skip to content

0.6.0 — Automatic flagship escalation

Pre-release
Pre-release

Choose a tag to compare

@qadanm qadanm released this 07 Nov 02:38
· 6 commits to main since this release

Do not install this release. It was never published to npm, and it is not
safe to build from this tag. Version 0.6.0 could refuse every prompt, in every
mode including manual mode, until the plugin was removed by hand.

Two defects compounded. It adopted a shared core inherited from an older
version, whose ledger had no planPoolSpent(), and routing.failClosed
defaulted to true, so that internal TypeError became a refusal to serve
any prompt. 0.4.0, the version before it, is self-consistent and does not hit
this; the failure needed the 0.4.0 to 0.6.0 upgrade path.

0.6.1
fixes both defects and is on npm.
Use that instead. The full account is in
docs/INCIDENT-2026-11-06-prompt-lockout.md.

The notes below are preserved as they were published, as a record of what
0.6.0 claimed and what it actually did.


Tier-3 work escalates by itself, paid from the plan-model pool.

Added

  • Automatic flagship escalation (premium.mode: "auto", now the default):
    a tier-3 task routes to the plan-model pool (Claude Sonnet 5.5, GPT-6.1 Sol)
    without a per-task approval prompt while the pool has budget. When the pool
    is spent, escalation degrades to an approval gate and the router serves the
    task with the strongest ordinary model - a routing refusal never fails a
    serviceable task. Tier-1 and tier-2 work always stays on the ordinary pool.
  • Plan-model pool ledger: monthly buckets tracking spend against the
    OpenDesign plan-model allowance (Pro: $120/month), persisted across
    restarts, separate from Design Plan credits and from other providers'
    premium spend. The cap is read from the resolved plan catalog.
  • Per-kind capability evidence: ModelRecord.capabilities (coding,
    debugging, agentic, architecture) from named benchmarks with provenance,
    moving expected success by at most 4 points - enough to break a close
    ranking, never enough to overrule a gate. Unscored models stay neutral:
    absent evidence is unknown, not zero.
  • Context probes (scripts/probe-plan-model-context.py): end-to-end
    800K-token verification with memorization sentinels and truncation checks.

Changed

  • GPT-6.1 Sol is scored (intelligence 55, Artificial Analysis v5.0.1) and
    auto-approved for tier-3 escalation along with Sonnet 5.5, both by owner
    instruction 2026-11-06. DeepSeek's observed 39.5 is untouched.
  • Catalog context windows raised from measured (328K/400K) to probed-verified
    800K for both flagships after passed end-to-end probes on 2026-11-06; the
    advertised 1M is deliberately NOT claimed, and Sol's long-context surcharge
    above 272K was confirmed by the billed amounts.
  • MiniMax M3.1 Flash is classified as a Design Plan model. The gateway serves
    it both inside and outside the Design Plan group and OpenDesign has not
    published which applies, so the conservative choice is made: treating an
    ordinary tier-2 workhorse as a plan model keeps routine work from draining
    the escalation pool. Before this, a tier-3 task could land on it as a
    premium model that a tier-2 flag itself made eligible.

Fixed

  • A partial settings file no longer produces a warning for every key it leaves
    out. Absent and invalid are now distinct: a key you did not write takes its
    default silently, while a key you did write with the wrong type still reports
    the problem. Before this, a config that only set providers.opendesign.plan
    emitted around fifty warnings and hid the ones that mattered.