Model Setup Guide
GPT-6.1 Sol on Hermes Agent and OpenClaw
OpenAI released GPT-6.1 Sol at DevDay on September 29, 2026: near-Astra coding and agent work at a fifth of the Astra price. Here is how to run it on Hermes Agent and OpenClaw, and the two changes from GPT-6 Sol that can break an existing setup.
gpt-6.1-sol) runs on Hermes Agent through your ChatGPT subscription, with no per-token bill; we confirmed a real Hermes Agent turn on a paid ChatGPT account on launch day. It also works on Hermes Agent and OpenClaw with an OpenAI API key or through OpenRouter, at $2 input and $10 output per 1M tokens, the same as GPT-6 Sol, with cached input down to $0.10. Two things changed from GPT-6 Sol: reasoning cannot be turned off, and tool calls work only over the Responses API.What GPT-6.1 Sol is
OpenAI released gpt-6.1-sol on September 29, one week after GPT-6 Sol. OpenAI describes it as "near-Astra performance for complex work at a lower cost" and recommends it for complex coding, computer use, and professional work, such as building a website from a product brief or turning financial results into a board presentation.
At the DevDay launch, OpenAI said it matches GPT-6 Astra on the DeepSWE v1.1 software-engineering test, beats Claude Opus 5.5 on AutomationBench and Terminal-Bench Science, and lands 2.1 points behind Astra on OSWorld 2.0 computer use at about a seventh of the cost. These are vendor results. OpenAI's own guidance is to compare it with Astra on your tasks before choosing.
It also supports multi-agent delegation in beta on the Responses API, where the model hands parts of a request to subagents.
Use GPT-6.1 Sol with your ChatGPT subscription
If you already pay for ChatGPT Plus, Pro, or a business plan, this is the cheapest way to give an always-on agent GPT-6.1 Sol. Turns count against your ChatGPT plan's own limits instead of an API bill.
- Deploy a Hermes Agent on OpenClaw Launch, or open an existing one from your Dashboard.
- Click Terminal on the instance and run
hermes auth add openai-codex --type oauth. - Open
https://auth.openai.com/codex/devicein your own browser, enter the code the terminal shows, and sign in with your ChatGPT account. - Open the instance card's model menu and pick GPT-6.1 Sol under the OpenAI row badged Subscription, or switch from any chat with your bot:
/model gpt-6.1-sol --provider openai-codex --global
Hermes and the instance card read the model list live from your ChatGPT account, so GPT-6.1 Sol appears as soon as your plan serves it. If you also use the Codex CLI directly, update it to the latest release first. In our test, Codex CLI 0.155.1 did not list GPT-6.1 Sol and rejected it with "not supported when using Codex with a ChatGPT account", on an account whose catalogue did include it for newer clients. This route is Hermes-only for now; OpenClaw offers only the subscription models its own release already knows. The full walkthrough is in the Hermes ChatGPT subscription guide.
Pick GPT-6.1 Sol with an API key on a managed instance
With an API key or OpenRouter credits, the steps are the same on Hermes Agent and OpenClaw, and you do not need a new instance.
- Open the Dashboard and find your running instance.
- Click the current model in the Text or Model row of the instance card.
- Choose the provider row that should pay:
- OpenAI with the Your key badge, if you have saved an OpenAI API key on the API Keys page. Tokens are billed to your OpenAI account.
- OpenRouter, to use your plan's included credits or your own OpenRouter key. The model appears as
openai/gpt-6.1-sol.
- Search for 6.1 sol and select it. The OpenAI list picks up new OpenAI models automatically, so GPT-6.1 Sol is there even though the featured shortlist still ends at GPT-6 Sol.
- Wait for the instance to return to ready, then start a fresh conversation.
Full-catalogue access applies to eligible paid instances; trial accounts use a restricted model list. On OpenClaw, a pick from the OpenAI row is registered with the Responses API automatically, which GPT-6.1 Sol needs for tool calls. Hermes talks to api.openai.com over Responses already.
Pricing compared with GPT-6 Sol and Astra
| Standard API, per 1M tokens | GPT-6 Astra | GPT-6 Sol | GPT-6.1 Sol |
|---|---|---|---|
| Model ID | gpt-6-astra | gpt-6-sol | gpt-6.1-sol |
| Input | $10.00 | $2.00 | $2.00 |
| Cached input | $1.00 | $0.20 | $0.10 |
| Cache writes | $12.50 | $2.50 | $2.50 |
| Output | $50.00 | $10.00 | $10.00 |
Reasoning none | Not supported | Supported | Not supported |
| Tool calls in Chat Completions | No, Responses only | Only with reasoning none | No, Responses only |
| Knowledge cutoff | April 30, 2026 | April 20, 2026 | April 30, 2026 |
All three have a 1,050,000-token context window and 128,000 maximum output tokens. GPT-6.1 Sol accepts up to 922,000 input tokens. Prompts above 272,000 input tokens are billed at 2x input and cache rates and 1.5x output for the whole request. Batch and Flex cost half of Standard, and Fast mode costs 2x. Prices are from the GPT-6.1 Sol model page, checked September 29, 2026.
The cached-input price matters most for agents. A long-running agent resends the same system prompt, tools, and history on every turn. At $0.10 instead of $0.20, those repeated tokens cost half as much as on GPT-6 Sol. OpenRouter lists openai/gpt-6.1-sol at the same $2, $10, and $0.10.
Two changes that can break an existing setup
Reasoning cannot be turned off
GPT-6.1 Sol accepts low, medium (the default), high, xhigh, and max. GPT-6 Sol also accepted none, which turned reasoning off; GPT-6.1 Sol rejects it, and it rejects minimal too. OpenRouter's catalogue still lists none for this model, but OpenAI rejects it there as well. Current Hermes omits an unsupported none, so the request succeeds but the model reasons at its default medium rather than the fast, no-thinking turn you asked for; older Hermes builds may send it and fail. Either way, if you had set agent.reasoning_effort to "none" for speed, change it to "low", the lightest setting this model has. Managed OpenClaw Launch instances leave reasoning effort at the default and are not affected unless you changed it.
Tool calls need the Responses API
Chat Completions works only for requests without tools. An agent is all tool calls, so a custom integration that sends tools to /v1/chat/completions fails on GPT-6.1 Sol even though the same call worked on GPT-6 Sol with reasoning none. Hermes and OpenClaw handle this on their direct OpenAI routes, as described below. It matters mainly if you point either one at an OpenAI-compatible relay that only speaks Chat Completions.
Self-hosted Hermes Agent
Put the key in ~/.hermes/.env, then set the provider and the bare model ID in ~/.hermes/config.yaml:
# ~/.hermes/.env
OPENAI_API_KEY=sk-...
# ~/.hermes/config.yaml
model:
provider: "openai-api"
default: "gpt-6.1-sol"
agent:
reasoning_effort: "medium" # low is the lightest; "none" is not acceptedHermes' openai-api provider uses the Responses API, so tools work. Through OpenRouter instead, use OpenRouter's slug:
model:
provider: "openrouter"
default: "openai/gpt-6.1-sol"You can also run hermes model and pick it from the list, since current upstream Hermes lists gpt-6.1-sol for both providers. On an older build that does not list it, type the ID in the custom model field. A model change applies to new sessions. To restart the gateway, run hermes gateway restart. Field names follow the upstream configuration example.
Self-hosted OpenClaw
No OpenClaw release so far, up to 2026.9.6, includes gpt-6.1-sol in its built-in OpenAI catalogue. The model is on OpenClaw's unreleased main branch, so a coming release should pick it up. Until then, set up an OpenAI API-key profile and register the model yourself:
openclaw onboard --auth-choice openai-api-key
openclaw models list --provider openaiAdd this entry to your existing models.providers.openai.models array. Setting api to openai-responses makes tool calls go over the Responses API, which GPT-6.1 Sol requires. reasoning: true tells OpenClaw it is a reasoning model, so it defaults to medium and accepts /think low:
{
"models": {
"providers": {
"openai": {
"models": [
{
"id": "gpt-6.1-sol",
"name": "GPT-6.1 Sol",
"api": "openai-responses",
"reasoning": true,
"input": ["text", "image"],
"contextWindow": 1050000,
"maxTokens": 128000
}
]
}
}
},
"agents": {
"defaults": {
"model": { "primary": "openai/gpt-6.1-sol" }
}
}
}Merge this into your configuration rather than replacing the file. Avoid /think off on this model: a release that does not know GPT-6.1 Sol cannot know that it rejects a reasoning disable. Use /think low for the lightest setting. Through OpenRouter, the reference is openrouter/openai/gpt-6.1-sol after openclaw onboard --auth-choice openrouter-api-key. See the upstream OpenAI models guide for your installed version.
GPT-6.1 Sol, GPT-6 Sol, or Astra?
For a coding or research agent that plans and uses tools across many steps, start with GPT-6.1 Sol. It costs the same per token as GPT-6 Sol and is cheaper on cached context. Keep GPT-6 Sol or Luna for setups that depend on reasoning none, and Luna for high-volume, narrow tasks. Use Astra when a wrong answer costs more than the 5x price difference. Run the same real tasks on each and compare cost per finished task, not per token.
GPT-6.1 Sol FAQ
What is the GPT-6.1 Sol model ID?
The OpenAI API ID is gpt-6.1-sol, with a dot. Hermes Agent keeps it bare in model.default with the openai-api provider. OpenClaw uses openai/gpt-6.1-sol. On OpenRouter the slug is openai/gpt-6.1-sol, which OpenClaw writes as openrouter/openai/gpt-6.1-sol.
Does GPT-6.1 Sol work on Hermes Agent?
Yes, three ways. With a ChatGPT subscription, pick it under the OpenAI row badged Subscription on the instance card, or send /model gpt-6.1-sol --provider openai-codex --global. With an API key, pick it under the OpenAI row with your own key, or under OpenRouter. On a self-hosted install, set model.provider: openai-api and model.default: gpt-6.1-sol. Set agent.reasoning_effort to low or higher. The model does not accept none; current Hermes drops it and lets the model reason at its default, while older builds may pass it through and fail.
Does GPT-6.1 Sol work on OpenClaw?
Yes, with one extra step when self-hosting. No OpenClaw release so far, up to 2026.9.6, includes gpt-6.1-sol in its built-in OpenAI catalogue; only the unreleased main branch has it. Register it under models.providers.openai.models with "api": "openai-responses", or route through OpenRouter as openrouter/openai/gpt-6.1-sol. On OpenClaw Launch, the instance card registers it for you. The ChatGPT subscription route is not available on OpenClaw yet, because OpenClaw only offers subscription models its release already knows; use Hermes Agent for that.
Can I use GPT-6.1 Sol with my ChatGPT subscription?
Yes, on Hermes Agent. We confirmed on September 29, 2026 that a paid ChatGPT account lists gpt-6.1-sol in its Codex catalogue and that it answers a real Hermes Agent turn through the openai-codex provider. Connect ChatGPT with hermes auth add openai-codex --type oauth, then pick it under the card's OpenAI row badged Subscription or send /model gpt-6.1-sol --provider openai-codex --global. OpenAI's launch rollout covers Plus, Pro, Business, Enterprise, and Edu; Free and Go are not included, and Enterprise and Edu admins must turn it on. See the Hermes ChatGPT subscription guide for the full connect steps.
Should I switch from GPT-6 Sol to GPT-6.1 Sol?
For coding and multi-step agent work, try it: the per-token price is the same, cached input is half as expensive, and OpenAI positions it close to Astra. Stay on GPT-6 Sol if your setup relies on reasoning none, or on function calling through Chat Completions. GPT-6.1 Sol supports neither.
Does GPT-6.1 Sol support Ultrafast mode?
Not yet. At launch, Ultrafast is available for GPT-6 Astra only. OpenAI says Ultrafast support for GPT-6.1 Sol is coming later. Standard and Fast modes are available now; Fast costs 2x Standard.