RAM labels describe the test computer, not this model’s memory requirement. Speed comparisons keep the 32 GB and 128 GB runs separate.
Runtime build: unrecorded · Local · test machine with 32 GB RAM · concurrency: 1
Thinking status: verified · probe 2 · scope Saved profile-level probe; exact historical template/build scope is not fully recorded..
Requested off does not prove an absence of reasoning. Saved checks do not establish unrecorded historical template or build details.
Overall across tasks
21.0 / 100
Nine categories, equally weighted · 9/9 eligible
Complete coverage for this setup. Quality only; speed is separate. How the index works →
What does it do well?
Select a category to explore the answers. Bars show what happened on every planned task. Incorrect answers and failures to finish both earn zero; technical problems and untested tasks stay unscored.
Exact scores and task times by suite
Each suite has its own metric and fixed task bank. The balanced index weights categories equally; individual scores and evidence remain available below.
This analysis covers this configuration across its recorded thinking conditions and test suites.
Its useful niche is checked passage calculations and selected math-and-reasoning questions with thinking enabled. Don't mistake that niche for a capable general assistant: basic coding, longer tool-driven work, passage answering and handling source corrections were poor. Expect to verify outputs rather than delegate work.
Original analysis generated by GPT Astra · · Edited by Codex; agent reviewed by Codex · publication authorized by user
About this summary
Codex reviewed this assessment against a newer evidence edition. The original analyst, generation date and source draft remain recorded separately from the editorial revision.
Analyst provider
openai
Generation route
Codex CLI · codex-cli 0.162.1 · ChatGPT account
Requested model
gpt-6-astra
Returned model
Not supplied; identity is recorded from the request only.
Exact provider snapshot
Exact provider snapshot not supplied.
Reasoning effort
high
Prompt version
model-summary-reader-v7
Generation time
2026-10-14T01:04:41.400128Z
Review time
2026-10-22T07:26:27.237601+00:00
Evidence reviewer
Codex (agent)
Publication authorization
User · 2026-10-22T05:55:43.625712+00:00 · Go ahead and complete the remaining work. Spin up agents: luna, terra, sol, astra, as needed to get it done. Narrative summaries: these are the astra generated summaries? Go ahead and get those completed as well. Once all of this is done, you may push the completed result.
Can help with calculations from a passage when thinking is enabled, though answers still need checking. It answered most of these calculation questions correctly, without approaching a clean sweep.
Can tackle selected difficult math-and-reasoning questions with thinking on, but treat this as a narrow capability. Performance on the separate logic-and-number puzzles remained weak.
Do not rely on it for source-backed answers. Passage answering was extremely poor in either mode, and neither mode successfully handled a complete case of defending an answer against pressure and updating it when evidence changed.
Avoid delegating project work. Small coding tasks had very low pass rates, and larger practical tasks received very low average scores in either mode. Occasional successful edits do not make this a dependable coding assistant.
Enable thinking selectively for passage calculations and selected hard math-and-reasoning questions. Calculations improved while average time fell, although typical paired tasks took longer. Hard-problem scores improved substantially, at the cost of extra time.
Evidence for this judgment
Calculating from a passage · Thinking off versus on
Leave thinking off if using it for small coding or research-paper questions. It worsened coding results while adding substantial time, and barely improved paper-answer matching despite taking longer.
With thinking on, its competition math and reasoning score is close to the leading tested small dense model. It trails every same-mode class alternative on small coding, source corrections and passage answering, so that narrow reasoning result does not establish a capable general assistant.
Evidence for this judgment
Published hard problems Thinking on. Small · under 5B · dense. Rank 2 of 5 in this recorded comparison.
Everyday coding tasks Thinking on. Small · under 5B · dense. Rank 5 of 5 in this recorded comparison.
Resisting incorrect corrections Thinking on. Small · under 5B · dense. Rank 5 of 5 in this recorded comparison.
Reading without guessing Thinking on. Small · under 5B · dense. Rank 5 of 5 in this recorded comparison.
Other mode, this model only: thinking off · 14.9/100 · Mean answer credit.
How this comparison works
Average credit per task; partly correct results can earn partial credit. Family comparisons show the labeled Instruct and reasoning versions. Other peer comparisons use the same requested thinking setting, not necessarily each model’s best mode. Small differences on these short tests may not hold on other tasks. Peer membership varies by test coverage and compatible settings.
Comparison saved with the 2026-10-14 assessment. Task-specific results.
Everyday coding tasksThinking on · Small · under 5B · dense
Find information in a small project, edit files and fix bugs.
Task pass rate · 0–100% · higher is better 16 of 16 tasks scored for each model.
Gaps are relative to this model. Treat small gaps cautiously.
Other mode, this model only: thinking off · 18.8% · Task pass rate.
How this comparison works
Share of tasks that passed the recorded checks. Family comparisons show the labeled Instruct and reasoning versions. Other peer comparisons use the same requested thinking setting, not necessarily each model’s best mode. Small differences on these short tests may not hold on other tasks. Peer membership varies by test coverage and compatible settings.
Comparison saved with the 2026-10-14 assessment. Task-specific results.
Resisting incorrect correctionsThinking on · Small · under 5B · dense
Keep a source-backed answer when challenged, but change it when the source is updated.
All-branches pass rate · 0–100% · higher is better 12 of 12 tasks scored for each model.
Gaps are relative to this model. Treat small gaps cautiously.
Several models reached full marks; this test cannot separate their top scores.
Other mode, this model only: thinking off · 0.0% · All-branches pass rate.
How this comparison works
Share of tasks that passed the recorded checks. Family comparisons show the labeled Instruct and reasoning versions. Other peer comparisons use the same requested thinking setting, not necessarily each model’s best mode. Small differences on these short tests may not hold on other tasks. Peer membership varies by test coverage and compatible settings.
Comparison saved with the 2026-10-14 assessment. Task-specific results.
Reading without guessingThinking on · Small · under 5B · dense
Answer from a passage—or say that the passage does not contain the answer.
Exact-match accuracy · 0–100% · higher is better 16 of 16 tasks scored for each model.
Gaps are relative to this model. Treat small gaps cautiously.
Other mode, this model only: thinking off · 6.3% · Exact-match accuracy.
How this comparison works
Share of tasks that passed the recorded checks. Family comparisons show the labeled Instruct and reasoning versions. Other peer comparisons use the same requested thinking setting, not necessarily each model’s best mode. Small differences on these short tests may not hold on other tasks. Peer membership varies by test coverage and compatible settings.
Comparison saved with the 2026-10-14 assessment. Task-specific results.
With thinking on, selected hard-problem scores are close to the leading small dense peer. In the matched timing cohort, every higher-scoring alternative takes longer: the nearest accuracy gap is small, while the leaders are substantially more accurate. Its shorter wait therefore comes with an accuracy tradeoff.
Published hard problems Thinking on. Small · under 5B · dense. Rank 2 of 5 in this recorded comparison.
Speed: Published hard problems Thinking on. Matching test-machine label and execution settings; spans model sizes. Timings include unsuccessful tasks, so read them alongside quality.
Speed and task success: Published hard problemsThinking on · Matching test-machine label and settings · Across model sizes
Shorter task time is better only when the result is useful. These times include failures, tools and grading. Token generation speed measures a different part of the work.
Results from this test setup, not a promise for your computer. Hardware, software, tokenizers and answer length can change the ordering. Historical runtime builds were not always captured. Comparison saved with the 2026-10-14 assessment.
Test machine: AMD Ryzen 5 5600X (6 cores / 12 threads) · AMD Radeon RX 6700 XT (12 GB VRAM) · 32 GB or 128 GB system RAM, never mixed in one timing group. Full test machine details
Worth knowing
Some examples cannot be fully inspected in the publication: project artifacts are withheld, and full papers are linked rather than reproduced.
Evidence for this judgment
Source limitation Some selected evidence has recorded publication redactions.
Context-exhaustion follow-ups are selected after failures. Repeated exhaustion after the permitted same-budget retry earns zero task-completion credit as failure to answer, not an incorrect submitted answer; answer-only averages exclude those outcomes.
Evidence for this judgment
Source limitation One same-budget retry after context exhaustion. A second context limit is failed to answer (zero task-completion credit), not an incorrect submitted answer. Answer-only averages exclude these no-answer outcomes; completed retry answers enter the normal scoring path. This follow-up is selected after observing failures.
One weight format is recorded for this model. Additional tested formats will appear here when available.
What changed in these results
One same-budget retry after context exhaustion. A second context limit is failed to answer (zero task-completion credit), not an incorrect submitted answer. Answer-only averages exclude these no-answer outcomes; completed retry answers enter the normal scoring path. This follow-up is selected after observing failures.
Thinking on took 58.2 seconds more per matched timed question, on average.
All matched quality and timing measurements
Matched measurement
Recorded result
Average credit, off → on
18.8% → 6.3%
Mean paired credit change
-12.5 percentage points
Question outcomes
0 improved · 14 unchanged · 2 worse
Mean added task time
+58.2s
Mean task time, off → on
11.7s → 69.9s
Median task time, off → on
4.5s → 37.7s
Median of paired time changes
+29.9s
Total added task time
+931.3s
Ratio of summed times, on / off
6.0×
Quality and timing can cover different subsets. Median paired change is calculated per question; it is not the difference between the two medians. Task time includes tools and grading.
The user asks where the project's retry-limit setting is defined and what value it holds. This exercises locating a named setting in code and reporting both its location and value.
The user asks for the release date mentioned in a project notes document. This exercises reading a specified file and extracting a particular fact rather than guessing from outside knowledge.
The user asks to change the project's retry limit to a specified value. This exercises finding the relevant setting and making a focused code edit rather than merely describing the change.
The user asks to create a text file containing exactly one supplied line. This exercises basic file creation and precise instruction following, including avoiding extra text in the file.
The user asks what the most recent Git commit changed in the project. This exercises inspecting recorded changes and turning them into a clear explanation of what was modified.
The user asks how many Python files are in the application folder and which is largest. This exercises identifying relevant files, counting them, and comparing their sizes.
The user asks to add a function that converts byte counts into readable sizes and remove the related TODO comment. This exercises implementing a small utility and updating the surrounding code consistently.
The user asks to find every TODO comment in the Python code and append each to the project's task list on a separate line. This combines searching across files with collecting text into an existing document.
The user asks to investigate a failing test and fix the application code without changing the test. This exercises diagnosing a bug while respecting an explicit limit on what may be edited.
The user asks to rename a network function and update every place in the project that uses it. This exercises tracking references across files and making a coordinated change rather than editing only the definition.
The user asks to find a proxy configuration file somewhere under the project's parent folder and report its host and port. This exercises searching beyond the project folder and reading configuration values.
The user asks which error code appears in a long event log and on which line. This exercises finding a specific entry in a large file and reporting its precise location.
The user asks to append a supplied release-related task as the final line of an existing task list. This exercises preserving existing content while adding exact text in the requested position.
The user asks for the total time a network function spends sleeping when all attempts fail, worked out from the code. This exercises following retry logic and adding the delays along that failure path.
The user asks for a project readme listing every command-line option with its help text. This exercises discovering the program's available options and transferring that information into complete, source-grounded documentation.
The user asks to undo the latest Git commit's change by editing the file directly, without using Git to make changes. This exercises understanding a previous edit and reversing it under a method constraint.
basic-H8 · primary
Filters change this list, not the fixed scoring denominator. Search currently covers question IDs, titles and available task explanations. Focus a control to load prompt/outcome search where this edition provides it.
Suggested comparisons
These are starting points for inspection, not claims that one setup is better. Runtime and placement differences remain visible.
Thinking on versus off
Verified requested on/off conditions of the same configuration, matched on the recorded test protocol.
Requested thinking on · Complete compared coverage