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 42 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.

news

Chrome adds a suspicious-site warning for Enhanced Protection users

Chrome now separates lower-confidence suspicious sites from known dangerous ones in Enhanced Protection. Google's Gemini scam analysis and ClickFix clipboard checks add detection, with server processing and privacy conditions users should understand.

The big change

What changed: Enhanced Protection now warns about lower-confidence suspicious sites as well as dangerous ones, using a different presentation. After Chrome finds high-confidence scam indicators, a server-side Gemini model examines page text; Safe Browsing weighs its analysis with domain reputation and other signals. A separate check examines copied commands.

Why it matters: Chrome can alert people to possible harm while reserving its full-page red interstitial for sites it judges dangerous. Google says the new tier allows more warnings. Users and administrators weighing Enhanced Protection must also consider the broader browsing data it sends to Google.

What to watch: The value of additional warnings turns on whether they help people avoid scams without repeatedly flagging legitimate pages or developer commands. Google has not published an independent evaluation of the warnings’ accuracy, false alarms or effect on scam losses.

Read the full story
—
Back to the briefing
news

Salesforce agrees to acquire Braze for $5.66 billion

The proposed acquisition would bring Braze's real-time customer engagement and AI decisioning into Salesforce's platform. The $5.66 billion agreement still needs Braze shareholder and regulatory approval.

The big change

What changed: Salesforce has a signed agreement to acquire Braze's existing real-time messaging and AI decisioning capabilities. A combined product would require the deal to close and the companies to integrate their systems.

Why it matters: Marketing teams evaluating the platforms can assess Braze's current tools today. The agreement provides no combined Salesforce service yet, so its proposed benefits cannot be judged from a shipped integration.

What to watch: Braze's board approved the agreement, but a majority Class A shareholder vote, antitrust clearance and other conditions remain. The companies expect a close in fiscal 2028, beginning February 1, 2027; that timetable is conditional.

Read the full story
—
Back to the briefing
guide

Build a checked Claude Code report from GitHub records

Use three Claude Code skills to collect GitHub commits and open issues, draft from saved evidence, check claims, then verify a manual run before scheduling.

The big change

What changed: The documented Action can invoke a project skill after checkout and expose structured JSON output. The template uses three separate invocations in one job, with a validated file between them.

Why it matters: The checker sees the collector's retained fields and the draft's exact input hash. A later invocation has no assumed memory of the earlier one.

What to watch: A passing schema and a model verdict cannot prove the report's facts. The maintainer must compare one manual run with real linked commits and issues before approving a recurring schedule.

Read the full story
—
Back to the briefing
guide

Build a source-backed LLM wiki and check its first update

Build linked Markdown pages from two permitted sources, check an AI answer and a knowledge gap against originals, then audit and repair the wiki.

The big change

What changed: Karpathy proposed a persistent Markdown wiki that an agent updates source by source, then queries and audits.

Why it matters: A reader can inspect the path from original passage to linked note to answer, and keep later source updates in the same record.

What to watch: The agent can still misread a passage, invent a link or miss an absent fact. The original files and reviewed changes decide what belongs in the wiki.

Read the full story
—
Back to the briefing
guide

Correct Claude Code project memory and check a fresh session

Inspect and correct one owned Claude Code project memory note and its index, then check a fresh local session against the project's authoritative source.

The big change

What changed: Claude Code gives a project two durable channels: shared instructions people maintain and machine-local memory that Claude writes from corrections and preferences. The latter has a short startup index, with detailed notes fetched only when needed.

Why it matters: A developer correcting a stale project preference can inspect the actual note, repair its index pointer and check what the next local session can access. That makes the stored artifact and its scope visible, while an answer alone cannot establish which source the model used.

What to watch: The next session's effective settings and file reads decide whether this correction is available. A different machine, a disabled memory setting or a topic file that was never opened changes the result even when the old session sounded certain.

Read the full story
—
Back to the briefing
guide

Move a retired Claude Sonnet 4 API application to Sonnet 5.5 and check the result

Migrate one owned, nonstreaming Claude Messages API application from retired Sonnet 4 to Sonnet 5.5, then check its real task, tools, effects, usage and release decision.

The big change

What changed: Sonnet 4's Claude API ID is retired, while the recommended Sonnet 5.5 path has a different request and response contract. A model-name edit leaves old samplers, thinking budgets, forced tool selection or parser assumptions in place.

Why it matters: An application can receive a successful HTTP response yet fail its real task or mishandle a tool that changes another system. The owner needs to check the complete request, all model turns, the resulting effects and the billable usage against cases approved for that application.

What to watch: The release decision depends on the same exact code, prompt, request and API-version revision that passed those cases, followed by observed cost and latency. The retired ID cannot serve as a fresh rollback or a new comparison baseline.

Read the full story
—
Back to the briefing
guide

Build a local AI product copy review app and check every claim

Build a single-user Python app that reviews product copy against approved facts, shows quoted issues, and saves the human-edited version in local SQLite.

The big change

What changed: A product owner can run a model review on each draft inside a local app, using an approved fact sheet as the reference. The complete code below requests structured issues and checks that each quoted phrase actually appears in the submitted draft.

Why it matters: The product owner can see where to inspect a claim, edit the final wording and keep a local record of what was reviewed. Quoting the draft establishes where an issue came from; it does not prove a claim true. The human reviewer must check flagged and unflagged claims against real evidence.

What to watch: The owner still decides whether the final wording is supported and whether the account's data terms and charges are acceptable. The saved row documents the reviewed text; using that text in a shop or campaign needs a separate human decision.

Read the full story
—
Back to the briefing
guide

Run and review an AI-assisted Playwright QA loop on your web app

Use your existing Playwright Test suite to establish a web-app baseline, inspect a real flow with Playwright CLI, then review any warranted fix and rerun the tests.

The big change

What changed: Microsoft's Playwright CLI skills describe a route from a Playwright Test run paused with --debug=cli into a browser session the agent can inspect.

Why it matters: A maintainer can compare a real test result with browser evidence before deciding whether the app, test or setup needs work.

What to watch: The attach route depends on the installed runner and CLI versions. A passing test, a flaky test and an untested flow call for different conclusions.

Read the full story
—
Back to the briefing