AI Weekly Malaysia

Summaries

Short AI and tech summaries with source links, signal scores, and why each update matters for builders, founders, and Malaysian tech workers.

Reset

Showing 1-5 of 5 results

DateProviderScoreSummary
18 Nov 2026, 6:19 PMLatent Space7.5 [AINews] GPT-6.2 Astra, the #2 Frontier Model is better and 20%-600% cheaper, but has mixed reviews; 6.2 Sol likely main workhorse

OpenAI shipped GPT-6.2 Astra and Sol on Nov 17, two days before Anthropic’s expected first trading day. Artificial Analysis found Sol ties September’s Astra at about 15% of the cost per task, while new Astra scores 62 on the Intelligence Index versus Fable 5.2’s 65. Early tester feedback was strongly negative in places, with Latent Space calling some complaints valid—noticeable RL artefacts and a poor launch video—while still using the model to automate work.

Why: For high-volume agent or coding workloads, Sol’s ~15%-of-cost result is the actionable number: test it as the cheaper workhorse before defaulting to Astra. Astra’s 62 vs Fable 5.2’s 65 means the top-end gap is small on the index, but tester complaints about RL artefacts make your own evals the deciding factor, not the headline benchmark.

18 Nov 2026, 1:46 AMHacker News7.0 GPT‑6.2 Astra and Sol

OpenAI announced GPT-6.2 Astra (frontier model for hard, long-horizon work) and GPT-6.2 Sol (cheaper everyday/agentic model), claiming both need fewer output tokens per task. Astra's API pricing drops 20% versus GPT-6 Astra to $8 per million input tokens, $40 per million output, and $0.40 per million cached input — a 60% cached-input discount — while Sol keeps GPT-6.1 Sol's prices. OpenAI reports Astra beating Claude Fable 5.2 by 5.5 points on Agents' Last Exam at 5% of the cost, and Sol landing within 0.5 points of Astra on Cognition's FrontierCode 2.0 at roughly one-fifth the cost; the HN thread drew 623 points and 359 comments.

Why: The cached-input price ($0.40/M, 60% off) is the number to check against your own agent loops: retrieval-heavy or repeated-system-prompt workloads get materially cheaper, while output at $40/M stays the cost driver, so token-efficient prompting and output caps still matter more than the headline 20% cut. Treat the Agents' Last Exam and FrontierCode 2.0 gaps as vendor-reported until you rerun your own eval set — the Fable 5.2 comparison already excludes nine tasks that used a fallback model, which is a concrete reason to distrust the ratio.

19 Nov 2026, 3:54 AMHugging Face Blog6.5 DaisyRose-27B: Pushing the Frontier of Post-Training Efficiency

RadixArk released DaisyRose-27B, its first model, built on Qwen3.8-27B and trained with reinforcement learning using Miles on 1,200 curated long-horizon agent tasks over 18 days on 144 H200 GPUs, with sessions up to 1M tokens. It keeps Qwen3.8-27B's architecture, tokenizer, chat template, image understanding and 256K context window, and ships Apache 2.0 checkpoints in BF16, FP8 and NVFP4. Reported gains over the base model include Terminal-Bench 4.1 pass@1 rising from 5.6% to 12.0%, DeepSWE v1.1 from 42.2 to 46.2, and SWE Bench Pro v2 from 91.3 to 94.7, though the team notes scores use the higher of the BF16 and FP8 runs wherever both were evaluated.

Why: The interesting number is the training recipe, not the leaderboard: 1,200 tasks and 18 days on 144 H200s is a post-training budget a funded startup could plausibly attempt, and Apache 2.0 weights in FP8/NVFP4 mean you can self-host and benchmark it against your own agent workloads instead of trusting the card. But treat the Terminal-Bench 5.6% to 12.0% jump carefully — doubling a very low pass rate still leaves it failing roughly seven in eight Terminal-Bench 4.1 tasks, and the 'higher of BF16 and FP8' reporting convention means you should re-run the eval on the exact checkpoint and quantisation you plan to deploy before swapping it into an agent pipeline.

18 Nov 2026, 2:00 PMOpenAI News4.0 Managing frontier AI risk: From training to deployment

OpenAI published a process post describing how it gates frontier models across three stages (sandboxed research, internal deployment, external deployment) with four defensive layers, and says it has paused internal training and held back models including "GPT‑6.1 Astra" to meet its safety standards. Since a July "Hugging Face incident," OpenAI says it now monitors frontier models across most internal and external deployment settings, including all internal deployments that use tools, and it evaluates "monitorability" — how reliably a model's chain-of-thought reveals unsafe intent. The post introduces safety cases as a required gate between stages; the text is cut off mid-sentence before detailing the fourth layer or any developer-facing requirements.

Why: The only concrete builder-relevant fact is that a named frontier model, GPT‑6.1 Astra, is being held back and that training has been paused — so any roadmap assuming access to OpenAI's next flagship on a fixed timeline is now unhedged. Everything else describes internal process with no API, pricing, deprecation, or policy change you can act on. Notably, the July Hugging Face incident is referenced but never explained, so you cannot assess whether it touches anything you run.

17 Nov 2026, 8:00 AMOpenAI News3.5 Astra for Law leads in legal intelligence

OpenAI released an updated "Astra for Law" configuration — GPT-6.2 Astra paired with an expanded legal search index and research instructions — claiming first place on Harvey LAB-AA with full credit on 20.8% of 120 assignments across 24 areas of law, ahead of GPT-6.2 Astra at 15.0% and Muse Wonder Full at 13.1%. On Vals AI's Legal Research Bench, the share of answers passing every check rose from about 46% to 53.8% in under two months, and the legal search index grew by over a third. Access is now request-only for all ChatGPT Enterprise customers via the Trusted Access Program, including through the API; the post names Cooley, Ropes & Gray and Sullivan & Cromwell as earlier testers.

Why: The number worth stealing is the scoring rule, not the model: LAB-AA gives credit only when an answer meets every requirement without a material unsupported claim, and the leader still fails roughly 4 in 5 assignments — a reminder that 'passes every check' is the right bar for document/agent evals, not partial-credit vibes. For product decisions, note access is gated behind Enterprise + Trusted Access request with no published pricing, rate limits, or regional availability, so you cannot commit a roadmap or quote a customer on it yet.

Top