Grok Assistant
I have enough to explain the difference. Gathering a bit more detail on Pro vs non-Pro and coding use.
Short answer
I can’t see the pixels of attachment 16886 from here, so I can’t OCR your exact Hermes table. From current public product info, though,
Luna vs Luna-Pro are not two different ChatGPT subscription plans (like Plus vs Pro). They are two ways of running the same GPT-5.6 Luna model tier inside Hermes / Codex-style access.
What Luna and Luna-Pro actually are
In the GPT-5.6 lineup Hermes exposes, you typically get families like:
- Sol — strongest / most expensive tier
- Terra — balanced mid tier
- Luna — fastest / cheapest efficiency tier (high-volume and lighter agent work)
Each often has a plain slug and a
-pro slug, e.g.
gpt-5.6-luna and
gpt-5.6-luna-pro.
Luna-Pro is not a bigger separate model. Public model cards describe it as the
same underlying Luna model served with
reasoning.mode = pro: more reasoning budget / higher quality on harder tasks, usually slower and more usage-heavy than plain Luna.
So they are
related, not cardinally different architectures. Difference is mainly reasoning intensity and cost/latency tradeoff, not “Luna = chat, Luna-Pro = coding product.”
Are “pro” options for writing code?
No — not exclusively.
- Pro ≈ deeper reasoning on complex work (hard debugging, multi-step logic, messy specs, tougher agent workflows).
- Coding is a common use of that deeper mode, but Pro is not a “code-only” SKU.
- Plain Luna is already used a lot for coding and agent tasks when the job is well-specified; many people reserve higher effort / Pro (or Terra/Sol) for the hard slices and keep Luna for volume.
- For the absolute hardest coding/architecture work, people often move up the family (Terra/Sol), not only flip Luna → Luna-Pro.
Practical take for Hermes
- Luna — daily driver / high volume / cheaper agent loops / straightforward implementation
- Luna-Pro — when plain Luna is under-thinking the problem and you want more reasoning quality from the same tier
- Expect Pro to feel smarter on hard prompts but cost more quota and run slower
- If your screenshot is a feature matrix (limits, tools, price), that’s Hermes UI packaging of those model slugs—not OpenAI renaming ChatGPT Plus/Pro to “Luna / Luna-Pro”
Separate confusion to avoid
ChatGPT
Plus / Pro subscriptions are account tiers (limits, access, Codex pool, etc.).
Luna / Luna-Pro are
model choices inside that world. Mixing “Pro plan” with “Luna-Pro model” is the usual source of confusion.
If you paste the table rows from the screenshot (feature | Luna | Luna-Pro), I can map each line in plain language against this.