Skip to content

Choose Ultra eligibility and visibility rules #36

Description

@iam-brain

Question

Under exactly which conditions should the plugin expose an ultra variant, and when should it be hidden or disabled?

Choose the rule after the upstream, catalog, and OpenCode capability facts are available. Cover:

  • catalog supported_reasoning_levels alone versus requiring multi_agent_version: "v2" and other metadata;
  • explicit Sol/Terra allowlisting versus a model-agnostic eligibility predicate;
  • behavior with live catalogs, GitHub fallback snapshots, stale caches, and account-scope switches;
  • custom-model aliases, suffix aliases, and user-configured overrides;
  • native versus codex runtime mode;
  • collaboration/subagent features disabled by configuration or unavailable in the host;
  • whether an ineligible selection is hidden, rendered disabled, rejected, or degraded;
  • how catalog ordering and future unknown reasoning efforts remain source-faithful.

The resolution must produce one deterministic predicate and a compatibility policy for every represented state.

Metadata

Metadata

Assignees

No one assigned

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions