Skip to main content
GPT-6 Astra (OpenAI) is the most capable OpenAI model in Tess — built for the hardest end-to-end work: complex reasoning, software engineering, computer use, research, and document creation.

​
What changed vs GPT-5.6 Sol

Native reasoning, tools (function calling / MCP, search, computer use), and image input. One Tess key — gpt-6-astra — not a fourth GPT-5.6 SKU.

​
Pricing (Tess credits)

Values follow Models and Costs (credits per 100 tokens): Captura De Tela 2026 09 09 Às 10 19 53

​
How to apply GPT-6 Astra in Tess

The gain appears when the agent gets more than a question: an objective, company context, the right tools, and a clear definition of done. Astra can then carry the work across files, systems, and decisions until it reaches the deliverable.
1

Start with the final outcome

Describe what must exist at the end: an updated CRM, a memo in the company template, a finished presentation, or a code change that passes its tests.
2

Provide context and access

Attach reference files and make the required tools or connectors available. Without access to the system, the model can guide the action but cannot perform it there.
3

Set boundaries and criteria

State what it may change, when it must request confirmation, and which conditions it must verify before finishing.
4

Match effort to risk

Use medium for known workflows, high for complex analysis and execution, and xhigh/max when depth and verification justify more time and tokens.

​
Three playbooks to get started

​
1. A sales follow-up that ends in the CRM

Input: meeting transcript, account data, and qualification rules.
Tools: CRM and calendar connected to the agent.
Suggested setup: medium or high effort; confirmation before sending messages or changing an opportunity.
Done when: the record is updated, every action has an owner and deadline, and the follow-up is ready. This is not meeting notes; it is the sales operation ready to move. Input: contracts, amendments, emails, internal policy, and the memo template.
Tools: company-file search and document generation.
Suggested setup: high or xhigh effort; mandatory citations and human review before legal use.
Done when: every conclusion traces back to a source, gaps are explicit, and the team receives the memo and summary in the format it actually uses.

​
3. A software change through passing tests

Input: repository, expected behavior, project standards, and test commands.
Tools: access to code, terminal, and test suite.
Suggested setup: high effort; xhigh/max for broad investigation or highly dependent changes.
Done when: the change is in the repository, the behavior is covered, and the relevant tests pass. This is not a suggested snippet; it is a verifiable change.
Astra can only perform actions allowed by the tools, connectors, and credentials available to the agent. Keep explicit human confirmation for irreversible or high-impact operations.
Best practices
  • Reserve GPT-6 Astra for work that still fails on GPT-5.6 Sol or Terra — it is about 2× Sol in Tess credits.
  • Keep GPT-5.6 Terra / Luna for volume. Don’t use Astra as a cheap extractor.
  • Effort goes up to max. Cap response length in the prompt when you don’t need a long deliverable.
See also: Models and Costs · GPT-6 Astra (OpenAI).