mirror of
https://github.com/garrytan/gstack.git
synced 2026-11-16 05:17:24 +01:00
v1.93.37.0 Price Claude Haiku 5.5, GPT-6 Luna and Gemini 4 Argon for eval planning, and name the GPT-6 tiers in the Codex docs (#3732)
* pricing: rows for claude-haiku-5-5, gpt-6-luna and gemini-4-argon (#3640) Co-authored-by: capy-ai[bot] <230910855+capy-ai[bot]@users.noreply.github.com> * docs: name gpt-6.1-sol and gpt-6-luna as the current Codex tiers (#2943) Co-authored-by: capy-ai[bot] <230910855+capy-ai[bot]@users.noreply.github.com> * docs(hosts): gpt-6.1-sol is the default eval tier, not the outside-voice default Co-authored-by: capy-ai[bot] <230910855+capy-ai[bot]@users.noreply.github.com> * test(autoplan): use a model id with no price row for the unpriced-spend-cap case (claude-haiku-5-5 is priced now) Co-authored-by: capy-ai[bot] <230910855+capy-ai[bot]@users.noreply.github.com> --------- Co-authored-by: capy-ai[bot] <230910855+capy-ai[bot]@users.noreply.github.com>
This commit is contained in:
1 parent
5192908de4
commit
6f1dfd5b7c
10 files changed
+51
-11
No files matched your search
+8
-5
@@ -188,11 +188,14 @@ digest's first line shows its gstack version; re-copy it after upgrading.
|
||||
For Codex, setup reads the top-level `model` from
|
||||
`${CODEX_HOME:-~/.codex}/config.toml` and generates the matching behavioral
|
||||
profile, falling back to `gpt-6-astra` when no usable model is configured.
|
||||
`gpt-5.6-sol` automatically receives bounded-scope instructions that
|
||||
finish the requested lake without expanding into adjacent cleanup or speculative
|
||||
hardening. The Sol profile is exact-match only: dated snapshots and other 5.6
|
||||
variants get the generic GPT profile, and setup warns on near-misses like
|
||||
`gpt-5.6-sol-2026-08-01`. Override detection with `./setup --host codex --model <id>` — the
|
||||
The current OpenAI tiers are `gpt-6-astra` (frontier), `gpt-6.1-sol` (smart, the
|
||||
default eval tier) and `gpt-6-luna` (lowest cost); `gpt-6.1-sol`
|
||||
and `gpt-6-luna` get the generic GPT profile. Only `gpt-5.6-sol` receives the
|
||||
bounded-scope instructions that finish the requested lake without expanding into
|
||||
adjacent cleanup or speculative hardening, because that patch was measured on 5.6
|
||||
Sol; extending it to `gpt-6.1-sol` waits for its own scope eval. The Sol profile is
|
||||
exact-match only: dated snapshots and other 5.6 variants get the generic GPT
|
||||
profile, and setup warns on near-misses like `gpt-5.6-sol-2026-08-01`. Override detection with `./setup --host codex --model <id>` — the
|
||||
override applies to that run only; set `model` in your Codex `config.toml` to
|
||||
make it stick across upgrades. After changing your Codex model, rerun
|
||||
`./setup --host codex` to regenerate the skills.
|
||||
|
||||
Reference in new issue
Block a user