Urgent.News

What's breaking now, across thousands of outlets.

Tech

Before You Blame the Model, Check the Stack

Why AI models seem to get dumber overnight, and what to check before blaming the weights. Lessons from Claude Code, GPT-5.6 Sol, and GPT-6 Astra.

Before You Blame the Model, Check the Stack

On September 3, 2026, OpenAI launched GPT-6 Astra to mixed reactions. Some developers complained about the model's performance, describing it as having a "post-launch lobotomy" with turns ending after roughly 30 seconds and completion reports for work that had not been completed. Others reverted to the previous model, GPT-5.6 Sol, to avoid the issues.

Two months earlier, similar complaints had been made about GPT-5.6 Sol, and OpenAI issued a post explaining that they had run experiments altering the model's reasoning effort, which refers to the amount of computation the model dedicates to generating a response. However, users remained frustrated as they struggled to pinpoint the source of the problem.

The issue highlights the complexity of deploying machine learning models. A model's performance can be influenced by various factors beyond its weights, such as the inference stack, system prompts, SDK parameters, and the application using the model. These components can change independently of the model itself, leading to unexpected results. Therefore, diagnosing model performance issues requires a comprehensive examination of all the layers involved in the model deployment process.

Written by urgent.news from HackerNoon's reporting — not their text. Machine-written — may contain errors; check the original before relying on it.

Read the original at hackernoon.com →

More in Tech

NetBird: 12,226 title matches, 3 application matches, 1,234 certificate hits

NetBird: 12,226 title matches, 3 application matches, 1,234 certificate hits Overlay networks are the modern answer to remote access: instead of publishing services, you join machines to a private…

  • NetBird detected through 12,226 title matches, indicating web dashboard presence
  • 3 application matches suggest API component presence
  • 1,234 certificate hits confirm self-signed certificate in TLS handshakes

When cert-manager's Ready Condition Runs Past Expiry Until a Reconcile

On cert-manager v1.21.2, a renewal-blocked Certificate kept Ready=True ("Certificate is up to date and has not expired") past notAfter through our 30-minute window, until a restart reconciled it.

  • Cert-manager v1.21.2 failed to update Ready condition after certificate expiration
  • Certificate remained Ready=True for 30 minutes despite 1-hour expiry
  • Issue resolved by restarting controller, not by certificate renewal

More from Saturday 24 October →