GPT-5.4: A Four-Model Comparison of Atomic Clock Applications

One-sentence takeaway

Under the same one-shot creative-coding prompt with no follow-up, GPT-5.4 produced the best-looking visuals and layout, but its atomic time synchronization drifted; Claude prioritized correctness, while Gemini was more complete, showing that no single model can cover both design and technical validation at once.

Use cases

• Suitable tasks: Comparing frontend generation, visual hierarchy, integration correctness, and the failure modes of different models.

• Unsuitable tasks: Treating a single atomic world clock prompt as a general coding ranking, or treating code artifacts not disclosed in the article as a formal benchmark.

• Applicable model versions: GPT-5.4, Claude (the article's context refers to Opus 4.6), Gemini, and MiniMax M2.5.

• Applicable clients, agents, or APIs: The article does not disclose a standardized client or harness; the author also used GPT-5.4 on everyday projects for two weeks.

• Recommended reasoning tier and parameters: Not disclosed / cannot be verified; the article is not a parameter-controlled experiment.

Test environment and input/configuration

• Task: Build an atomic world clock app from a single prompt, requiring an analog clock, digital time, a world map/time zones, and real atomic time synchronization.

• Constraints: The same prompt for all four models, one shot, no follow-up, and no hand-holding.

• Subsequent observation: The author then used GPT-5.4 on real projects for two consecutive weeks, but did not disclose complete project logs or a standardized scoring sheet.

• Checkpoints: Layout/aesthetics, NTP/atomic synchronization, analog-hand angles, map completeness, and runtime usability.

Results data

• GPT-5.4: Best-looking and clearly laid out, making it suitable for presentation; however, atomic sync drifted after taking the time only once, and the analog clock hands were slightly off.

• Claude: Synchronized correctly via NTP and updated at intervals; its visuals were more functional than polished.

• Gemini: Had import errors in the first pass; after fixes, it produced a relatively complete world map with real geographic projection. Time synchronization also drifted, and the hands were misaligned.

• MiniMax M2.5: Produced a non-functional result for this creative integration task; the author notes that targeted code fixes might produce a different outcome.

• All four models made errors in the simulated clock-hand positions, exposing an apparently simple angle-mapping problem.

The article's accompanying public data table (sourced from Vals.ai/Artificial Analysis) lists GPT-5.4 at SWE-Bench Pro 57.7%, Terminal-Bench 2.0 75.1%, and OSWorld 75.0%; however, the author emphasizes that different scaffolds can significantly change the results.

Conclusion

The test separates “good-looking,” “complete,” and “correct”: GPT-5.4 is suited to visual design and targeted-fix candidates, but any time-, finance-, or synchronization-related feature must include validation against real protocols or data. The author's routing recommendation is to assign models by task rather than search for a single all-purpose model.

Limitations

• A single prompt, four models, and no public repository, code diff, or automated test report cannot establish statistical significance.

• Model parameters, temperature, tools, context, and runtime were not fully disclosed, making strict reproduction difficult.

• The article's benchmark table mixes official and third-party data, and its sections on long context, model pricing, and other models rely on secondary sources; they should not be conflated with this creative test.

Reproduction steps

1. Keep the original atomic world clock requirements, and give each model the same initial file state, API mock, and runtime environment.

2. Write automated checks in advance for the NTP/atomic sync update interval, hour/minute/second-hand angles, time-zone conversion, map data, and offline fallback.

3. Run each model multiple times, recording time to first runnable result, test failures, visual score, functional pass rate, and manual revisions.

4. Score GPT-5.4's design quality and protocol correctness separately so an attractive interface does not conceal synchronization errors.

5. Validate the results with a second real project before deciding whether to use GPT-5.4 for design, fixes, or review.

Original evidence and data

The original article publicly discloses the complete task description, the one-shot/no-follow-up constraints, and itemized results for all four models, along with observations that GPT-5.4 looked good but its atomic sync drifted, Claude's NTP was correct, Gemini's map was complete, and MiniMax was non-functional.

Source excerpt or observation (short quote for compliance only)

The author's summary is “Design? GPT 5.4. Correctness? Claude. Completeness? Gemini,” a single-task observation that should not be generalized into a universal ranking.