Skip to content

Default model 'claude-opus-5' is stale and scattered; setup offers no Codex backend despite README support #1936

Closed as not planned

Description

@jiejingzhangamd

Target release

Unsure

How were you running Hyperloom?

Local

Optimization domain

Inference

Issue type

Environment / setup

Which phase failed?

Setup / baseline

Summary

  1. The default Claude model is hard-coded as claude-opus-5, which is not a current model, in several places: src/hyperloom/common/llm_config.py:166 (DEFAULT_CLAUDE_MODEL), agents/quantization/driver/runner.py (DEFAULT_MODEL), inference_optimizer/breakdown/reporters/llm_client.py (three literals), and the setup skill's default option.
  2. The README lists "LLM backend: Claude, Codex" and the CLI has --codex-model / OPENAI_BASE_URL / OPENAI_API_KEY support, but hyperloom-setup only asks for ANTHROPIC_BASE_URL, ANTHROPIC_API_KEY and CLAUDE_MODEL. A Codex-only user has no setup path.

Expected

  1. One owner for the default model id (the other call sites derive from it), updated to a current model.
  2. Setup first asks which backend (Claude or Codex), then collects that side's base URL, credential and model.

Activity

  1. chaojhou commented on Oct 17, 2026

    @chaojhou
    Collaborator

    Triage against main 7e57b1e8f.

    • Default model: resolved by fix(llm): default to claude-opus-5-5 from one owner; keep claude-opus-5 on the ladder #1941. The default now derives from llm_config.DEFAULT_CLAUDE_MODEL (claude-opus-5-5). claude-opus-5 remains a valid fallback. Leftover literals: install_kernel_tools.sh:182, skills/hyperloom-setup/SKILL.md:136, examples/README.md:80, and slurm/proxy.env.template (still claude-opus-5). A small separate PR should derive them or pin them with a test.
    • Codex in setup: the gap goes deeper than the skill text. When .env is authoritative and has no HYPERLOOM_LLM_MODE, inference_optimizer/assets/install_baremetal.sh infers anthropic-only from the Anthropic side alone (:2448-2452). It then unsets and deletes the OpenAI side whenever the hosts differ (:2491-2496, :2585-2593). So a user who picks Both, or who switches an existing Claude setup to Codex, gets OPENAI_BASE_URL / OPENAI_API_KEY / OPENAI_CUSTOM_HEADERS wiped (leaving CODEX_MODEL orphaned) after the skill's read-back check has already passed.

    Needed for #1942: rebase onto main, dropping the already-merged #1940 commits and resolving the SKILL.md:136 conflict. Fix the inference in the backend: derive the mode from which sides of .env actually carry a URL and key, rather than adding new HYPERLOOM_LLM_MODE values that would have to be kept in sync with .env. Add a contract test: with .env holding both sides on different hosts, run the setup backend and assert OPENAI_BASE_URL and OPENAI_API_KEY survive alongside CODEX_MODEL.

    Re-labelled type:feature. Priority: P2. Assigning @jiejingzhangamd (author of #1942).

  2. added
    type:featureNew capability or improvement
    and removed
    type:bugSomething is broken or not working as expected
    on Oct 17, 2026
  3. github-actions commented on Oct 19, 2026

    @github-actions

    This issue has been quiet for about 2 days since our last reply.

    It will be closed automatically in 1 day if there is no further activity.
    If you are still working on this, please leave a comment with any update — that will reset the timer.

  4. github-actions commented on Oct 20, 2026

    @github-actions

    This issue has been automatically closed because there was no response for about 3 days after our last comment.

    If you would like to continue the discussion, please feel free to reopen this issue or leave a new comment — we will be happy to take another look.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Labels

awaiting-author-responseWaiting for issue author to reply (auto-managed)domain:inferenceRelated to inference optimizationstaleNo activity, scheduled for auto-closetype:featureNew capability or improvement

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions