Model Setup Guide
GPT-6 Astra on OpenClaw and Hermes: Setup, Pricing, and Rollout
GPT-6 Astra is OpenAI's new top model for difficult reasoning, coding, research, and computer use. It is live, but the September 3 rollout is staged. This guide separates what is confirmed from what is still arriving, then shows the verified direct-API path and current support status for both OpenClaw and Hermes Agent.
What OpenAI launched
OpenAI positions GPT-6 Astra as its most capable model for complex reasoning, coding, computer use, research, and document creation. The official model page lists a 1,050,000-token context window, up to 128,000 output tokens, and an April 30, 2026 knowledge cutoff. It accepts text and images and produces text; audio and video are not supported model inputs.
The rollout starts with Trusted Access enterprise customers on September 3, followed by API, Plus, Pro, Business, and Enterprise access in the coming days. That distinction matters: publication of the model does not guarantee that every API organization can call it on day one.
GPT-6 Astra specifications and price
| Item | GPT-6 Astra |
|---|---|
| Model ID | gpt-6-astra |
| Context window | 1,050,000 tokens |
| Maximum output | 128,000 tokens |
| Input / 1M tokens | $10.00 |
| Cached input / 1M tokens | $1.00 |
| Cache write / 1M tokens | $12.50 |
| Output / 1M tokens | $50.00 |
| Reasoning levels | low, medium, high, xhigh, max |
The headline context limit needs a cost warning. Once an input exceeds 272,000 tokens, OpenAI applies 2× input and cache pricing and 1.5× output pricing to the full request. Batch and Flex processing are 50% of standard rates; Fast processing is 2×. Start with a modest context budget and only pay for the million-token window when the task genuinely needs it.
Use GPT-6 Astra on OpenClaw Launch
The verified managed path at publication time is Hermes Agent. Add your OpenAI key as a user credential, then use Hermes's custom model field. The key is not shared with other customers.
- Open API Keys and add your OpenAI API key.
- Open the model picker for your running Hermes Agent instance.
- In the custom model fields, choose platform
openaiand enter model IDgpt-6-astra. - Apply the change. For Hermes Agent, begin a new session so the new default is used.
Managed OpenClaw is not ready for this custom selection yet. OpenClaw Launch declares each direct OpenAI model in the instance provider catalog, and Astra is not in that catalog at publication time. Do not type the ID into a managed OpenClaw instance and assume it is supported; wait until Astra appears in the OpenAI section of the model picker.
If OpenAI returns a model-not-found, permission, or organization-access error, do not keep changing the spelling. Confirm Astra is visible to the same API organization that issued the key. During rollout, waiting for account enablement may be the only fix.
Self-hosted OpenClaw setup
OpenClaw uses provider-prefixed model references. Its built-in OpenAI provider reads OPENAI_API_KEY and uses OpenAI's Responses API, so the Astra reference is openai/gpt-6-astra.
export OPENAI_API_KEY="sk-..."
openclaw onboard --auth-choice openai-api-key
openclaw models list --provider openai
openclaw models set openai/gpt-6-astraThe equivalent default in openclaw.json is:
{
"agents": {
"defaults": {
"model": {
"primary": "openai/gpt-6-astra"
}
}
}
}Run the model-list command before switching. OpenClaw's published catalog may trail a same-day OpenAI release, and your OpenAI organization must have access even when the local client accepts the model string.
Self-hosted Hermes Agent setup
Hermes Agent uses a provider name and a bare model name in separate fields. Put the key in ~/.hermes/.env:
OPENAI_API_KEY=sk-...Then set the model in ~/.hermes/config.yaml:
model:
provider: "openai-api"
default: "gpt-6-astra"You can also run hermes model to configure the direct OpenAI provider. The old LLM_MODEL environment variable is no longer the source of truth. Existing chats keep their current model, so start a new Hermes session after the change.
Model IDs: do not mix the two formats
| Framework | Provider | Model value |
|---|---|---|
| OpenClaw | Built-in OpenAI provider | openai/gpt-6-astra |
| Hermes Agent | openai-api | gpt-6-astra |
| OpenClaw Launch — Hermes Agent | openai | gpt-6-astra |
| OpenClaw Launch — OpenClaw | Pending catalog support | Wait for the OpenAI picker entry |
Agent features and migration caveats
Astra supports streaming, function calling, and structured outputs. OpenAI's model guidance says agent tools are available through the Responses API, including web and file search, code interpreter, hosted shell, computer use, MCP, skills, and tool search. A Chat Completions request may generate text, but tool use requires Responses.
- There is no
nonereasoning mode. Migratenoneorminimalworkloads tolow. - Remove sampling parameters when reasoning is enabled. OpenAI tells migrating clients to remove
temperature,top_p, andtop_logprobs; Chat Completions clients should also removelogprobs. - Review skills and agent instructions. Astra follows repository and skill instructions closely and can operate powerful tools. Keep permissions narrow, use approval gates for consequential actions, and test workflows before granting unattended access.
- Expect mid-run interaction. Astra adds asynchronous tool calling, mid-turn steering, configuration updates, and monitoring. Older wrappers may need an update before they expose all of those capabilities.
Troubleshooting the launch window
- Model not found or access denied: verify the API key's organization and wait for OpenAI's rollout. The spelling is
gpt-6-astra. - Model absent from a framework picker: update the framework, inspect its provider model list, or use the custom model field when available.
- Tools do not run: make sure the integration uses the Responses API. Tool support is not available through Astra's Chat Completions path.
- OpenRouter route fails: no public Astra slug was listed there at publication time. Use the direct OpenAI provider instead of guessing a route.
- Unexpectedly high bill: inspect input size. Crossing 272,000 tokens reprices the whole request at the long-context multipliers.
Primary sources
- OpenAI GPT-6 Astra model reference
- OpenAI GPT-6 Astra usage and migration guide
- OpenAI GPT-6 Astra safety overview
- OpenClaw model provider documentation
- Hermes Agent provider documentation
GPT-6 Astra FAQ
Is GPT-6 Astra live?
Yes. OpenAI published GPT-6 Astra on September 3, 2026, but access is being enabled in stages. The first wave is Trusted Access enterprise customers, with API and ChatGPT plan access following. A valid model name can therefore still return an access error until your account is enabled.
What model ID should I use?
Use openai/gpt-6-astra in OpenClaw. In Hermes Agent, set provider openai-api and model gpt-6-astra. The provider prefix belongs in the OpenClaw reference, but not in Hermes's model field.
Does GPT-6 Astra work on Hermes Agent?
Yes, through Hermes Agent's direct OpenAI provider. Put OPENAI_API_KEY in ~/.hermes/.env, set model.provider to openai-api, and set model.default to gpt-6-astra. Start a new session after the change, and remember that OpenAI still has to enable Astra for that API account.
Can I run GPT-6 Astra with a ChatGPT subscription?
Do not assume that route is active yet. OpenAI says ChatGPT Plus, Pro, Business, and Enterprise access is coming during the staged rollout, but neither OpenClaw nor Hermes currently documents Astra in its subscription-backed model catalog. The direct OpenAI API key is the confirmed external-agent path; check the live model picker before relying on a subscription route.
Is GPT-6 Astra available through OpenRouter?
It was not listed in OpenRouter's public model catalog when this guide was published on September 3, 2026. Do not invent an openrouter/openai/... ID. Use the direct OpenAI route until OpenRouter publishes an official slug.
How much does GPT-6 Astra cost?
Standard API pricing is $10 per million input tokens, $1 per million cached input tokens, $12.50 per million cache-write tokens, and $50 per million output tokens. Requests above 272,000 input tokens use higher long-context multipliers for the entire request.