THE WORLD IS NOT STANDING STILL.RSS
BIG CHANGE.
BIG CHANGE, one tap away
BIG CHANGE, one tap away

Make room for the big picture.

Add BIG CHANGE to your home screen or desktop. It opens in its own window, with the latest stories when you’re online.

iPhone & iPad
Open bigchange.ai in Safari. Tap Share, then Add to Home Screen. Turn on Open as Web App if shown, then tap Add.
Android
Open bigchange.ai in Chrome. In the browser menu, choose Install app or Add to Home screen.
Desktop
In Chrome or Edge, use the install icon in the address bar or the browser’s app menu. In Safari on Mac, choose File → Add to Dock.
All briefings

Follow the change ·

The day,
in perspective.

What happened in AI and robotics — and the change behind it. A reading path through 22 stories from BIG CHANGE.

Ordered using RADAR attention, story opens and likes. Excerpts from our published reporting; open a story for the full context and sources. Dates in UTC.

analysis

EmArm uses whole-arm touch to adjust a robot's movements

HKUST's EmArm research prototype uses tactile skin and joint sensing to adjust movement. Lab tests cover touch recognition, object balancing and obstacle avoidance; deployment remains untested.

The big change

What changed: EmArm places tactile sensing across much of a rigid arm and feeds contact features together with joint angles into its movement decisions. The researchers report demonstrations of touch classification, object balancing and path replanning when an obstacle is outside the robot's view.

Why it matters: Contact can happen anywhere along an arm, including beyond a gripper. Sensing where and how the arm is touched gives the controller information that vision or a few force sensors may miss in the demonstrated tasks.

What to watch: The published evidence concerns a research platform and bounded experiments. Repeated tests in less controlled settings, independent reproduction and practical access to the implementation would be needed to assess broader use.

Read the full story
—
Back to the briefing
analysis

Anthropic traces NIST curve seeds to an old C random generator

Anthropic says Claude helped reconstruct how several NIST and ANSI curve seeds were generated. Its code matches published values, while some base points and selection choices remain unexplained.

The big change

What changed: Anthropic published a specific generation recipe and code for the seeds of NIST P-192, P-224, P-256, P-384 and P-521, four NIST binary curves, and five ANSI X9.62 example curves. Its separate base-point recipe matches P-192 and five ANSI examples.

How: The team reports that Claude recognized patterns in the published seed bits, recovered generator state, and walked the state backward to clock-shaped initial values. For six base points, it identified a generator used in older long-integer software.

Limit: The code makes the proposed matches inspectable, but a matching recipe does not document every historical selection decision or establish the curves' security. BIG CHANGE reviewed the public post and historical standard; it has not run an independent reproduction.

Read the full story
—
Back to the briefing
analysis

Claude Code's team assigns human review by change risk

Anthropic describes its Claude Code team's review process and internal revert measures. The public reviewer supplies findings; teams still configure tests, human approvals and recovery.

The big change

What changed: AI review can examine a proposed change and its surrounding code, verify suspected bugs and put the surviving findings beside the relevant lines. That gives engineering teams another source of review evidence as agents produce code.

Why it matters: The public reviewer reads code without executing it and grants no permission to ship. Tests and repository approval rules are separate decisions that an engineering lead must configure.

What to watch: Review frequency affects spending, and a budget limit can cause reviews to be skipped. Teams adopting the service need to distinguish a completed clean review from a review that never ran.

Read the full story
—
Back to the briefing
analysis

DeepSeek updates V4.1 Flash and opens Search and Fetch APIs

DeepSeek's October 17 release changes the model behind deepseek-flash and opens separate web Search and Fetch APIs. The benchmark gains remain company-reported.

The big change

What changed: DeepSeek replaced the model behind deepseek-flash without changing that API name or its token prices. It also made Search and Fetch available as standalone JSON APIs.

Why it matters: An application can request search results, retrieve a selected page and provide that material to its own workflow. The documented interfaces make the steps and request charges visible; they do not establish that every retrieved page is accurate or that the new model performs better in a particular user's environment.

What to watch: Independent runs of the new model under disclosed agent settings would test DeepSeek's performance claims. Developers using Search or Fetch also need to track request billing, rate limits and how their applications handle page content that may be unavailable or untrustworthy.

Read the full story
—
Back to the briefing
analysis

Danaher and NVIDIA plan AI links between lab instruments and models

Danaher and NVIDIA plan integrations across scientific instruments, AI models and data analysis. The announcement names computing tools but leaves products, access and measured results unspecified.

The big change

What changed: Danaher is bringing its instruments and workflow software into a joint integration effort with NVIDIA. The proposed feedback loop would make physical measurements part of how AI guides further research.

Why it matters: The proposed loop depends on moving information between computational predictions and physical measurements. For researchers, its usefulness turns on how reliably those stages exchange data and how the experimental result is checked.

What to watch: Instrument specifications would let laboratories assess the integration. Published comparisons of experiment time, failed runs and result quality would then provide evidence of its value.

Read the full story
—
Back to the briefing
guide

Run distributed MLX inference across Mac Studios

Apple's MLX and Thunderbolt RDMA setup can split model inference across Macs. This documentation-based walkthrough shows the prerequisites, benchmark path and limits of Apple's reported speeds.

The big change

What changed: MLX 0.30.1 and macOS 26.2 let compatible Macs use a Thunderbolt 5 RDMA connection through MLX's JACCL backend. A model can be split by layers across two machines or by computation within layers across more machines.

Why it matters: A researcher with several high-memory Mac Studios can run a model whose working memory exceeds one machine's capacity while keeping inference on local hardware. Apple's 816-billion-parameter example needs multiple machines even after quantization.

What to watch: The choice of pipeline or tensor parallelism changes the result. Apple's tests found little decode-speed gain from two-machine pipelining, while its four-machine tensor setup generated faster. Current MLX documentation also warns against a synchronization option used in the published benchmarks.

Read the full story
—
Back to the briefing