Model recommendations: add GPT-6 Sol/Luna tiers to codex-owned call routing
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 1/5
- Estimated time
- Under an hour
- Newbie friendliness
- 85/100
- Issue type
- Documentation
- Clarity
- Clearly specified
- Activity status
- Active
- Tech stack
- typescript
- Domain
- documentation
Research direction
The issue specifies updating README.md around line 140-150 and docs/skills.md around line 1065. Start by locating these files in the repository. Replace mentions of gpt-5.6-sol with gpt-6-sol and add gpt-6-luna as the micro tier. Ensure detection logic is noted to accept new slugs. Verify changes by checking the documentation locally.
Written by the indexing model from the issue text.
Description
What
README.md (~L140-150) and docs/skills.md (~L1065) currently describe codex-owned calls defaulting to gpt-6-astra, with gpt-5.6-sol receiving bounded-scope instructions and gpt-5.6-sol-2026-08-01 named for detection.
GPT-6 Sol and Luna are now served (verified via codex CLI 0.156.0, codex debug models lists gpt-6-sol/gpt-6-luna; codex exec -m gpt-6-sol works on a ChatGPT account). Per OpenAI, Sol is ~50% cheaper than 5.6 Sol at higher capability, and Luna sits at the micro tier.
Suggestion
Extend the documented tiering: keep gpt-6-astra as the frontier/adversarial default, but refresh the bounded-scope and cost-sensitive tiers to gpt-6-sol (medium effort works well) and gpt-6-luna, replacing the 5.6 pins. Detection should accept the new slugs (gpt-6-sol-* datestamps) alongside the 5.6 ones for a transition period.
Happy to send a small docs PR if useful.
- Dominant language
- TypeScript
- Stars
- 138k
- Forks
- 20.5k
- Avg merge
- 8h 32m
- Merged PRs (30d)
- 292
Getting set up
- No Dockerfile or Docker Compose file
- Has a pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from garrytan/gstack
-
Difficulty 2/5 1-3 hours Newbie friendliness 66/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
Maintainers usually reply within 1 day
-
pregate: a missing pytest is PREGATE_LANE_FAILED (blames the diff), not PREGATE_ENVIRONMENTPossibly taken @vilano93 claimed this today. Open
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 1 day
Similar issues
-
area:cli bug P4
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
Maintainers usually reply within 1 day
-
bug from-studio
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
esengine/DeepSeek-Reasonix#14868 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
linxiv-dev/linXiv#384 · 1 comment ·
Maintainers usually reply within 1 day
-
scope:core type:security
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 66/100
mailgun/mailgun.js#544 ·