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

guide

Connect Perplexity to your financial account and check one answer

Check the Plaid consent, connect one authorized financial account to Perplexity, reconcile one answer with your institution, and review access and prior data.

The big change

What changed: Perplexity's April 2026 web update added Plaid-backed bank, credit-card and loan connections to its Personal CFO experience in the US and Canada. A May 10 update raised its stated limit to 30 accounts and 500 assets per account. Individual access still depends on the actual account and institution.

Why it matters: A conversational answer can draw on personal financial records across connected accounts. The permission screen and the answer's account and date scope therefore matter as much as the wording of the question. Checking one value against an institution record can reveal a stale or incomplete answer before you use it.

What to watch: A Plaid disconnect stops future sharing through that connection, while Perplexity may still hold previously received data. Review the connection and any recipient-held data request separately, and keep the final provider response with your private record.

Read the full story
—
Back to the briefing
guide

Make an original Seedance 2.0 video under face and IP restrictions

Create one original Seedance 2.0 clip in Dreamina with a bounded credit attempt, then check the full download, rights, provenance and intended use or record a precise hold.

The big change

What changed: Dreamina documents a Seedance 2.0 text-to-video route with model, setting, generation and download controls.

Why it matters: A text-only original brief avoids uploading a face or protected reference; the creator still checks the prompt and generated result.

What to watch: CapCut's rollout statement describes restrictions on certain real-face references and unauthorized IP. The current account controls and applicable terms determine the actual attempt.

Read the full story
—
Back to the briefing
guide

Pilot Claude's Opus adviser with Sonnet or Haiku and check quality and cost

Run an approved real task with the same Claude executor alone and with an Opus adviser, verify both answers, and compare complete usage and billed cost.

The big change

What changed: The beta API can run an Opus adviser sub-inference inside a Sonnet or Haiku executor turn, including a paused turn that needs a continuation request.

Why it matters: One controlled task pair can show whether the advised result passes your own quality checks and what the whole attempt costs.

What to watch: An adviser call costs extra, can fail or stop at its token cap, and may return encrypted advice. A tool-use attempt is not proof of successful advice.

Read the full story
—
Back to the briefing
guide

Direct a local Cursor Agent from iPhone and verify the result

Hand a local Cursor Agent session to iPhone Remote Control, inspect its permissions, then check the local diff and tests before a commit or PR decision.

The big change

What changed: Cursor's Remote Control hands an Agents Window session to a cloud agent loop that you can direct in the iOS app. Terminal commands, edits, tests and Git tool calls still execute on your available computer.

Why it matters: You can follow the same local task away from the desk without changing its execution location, then return to the repository to judge the actual code and test output.

What to watch: Cloud storage, plan and device access, the computer's availability, local tool permissions and usage charges all affect whether the handoff is appropriate. Cursor's current manual does not say that desktop approval behavior stays identical after handoff.

Read the full story
—
Back to the briefing
guide

Schedule a checked Claude Code repository review on Linux

A bounded Python runner pins tracked Git files, saves a private Claude Code review receipt, and gives maintainers a manual and first scheduled run check.

The big change

What changed: Claude Code's programmatic -p mode and current CLI controls let a script request a noninteractive review with a restricted built-in tool list, denied MCP tools, turn limit, and estimated spending limit. The runner adds a pinned Git blob snapshot and a private JSON receipt.

Why it matters: A scheduled model answer by itself gives the maintainer little evidence about what was examined. This route records the commit and per-file identities, then requires a person to check the report before the schedule and again after its first due run.

What to watch: The tool and prompt controls do not establish host isolation or prove that a finding is correct. The CLI budget is an estimate, cron can miss a run, and the checkout may advance between runs. Each report must be judged against its own recorded revision and the account's actual usage.

Read the full story
—
Back to the briefing
guide

Build one artifact with a Claude Code builder and separate validator

Set up a Claude Code builder and read-only validator for one authorized artifact, run the real checks, allow one scoped repair, and make a documented human accept-or-hold decision.

The big change

What changed: Claude Code lets a project define a builder with editing tools and a separate validator with read tools. That gives one file task a deliberate second inspection from a fresh context, while the main session keeps the original requirement and evidence together.

Why it matters: A validator can compare the actual artifact, diff and check output with each acceptance criterion instead of accepting the builder's completion claim. The person responsible can see which requirement passed, failed or still lacks proof.

What to watch: The boundary depends on the effective tool and permission settings, not the agent names. The validator in this guide cannot run tests, so the owner or main session must capture their real output and make the final decision.

Read the full story
—
Back to the briefing
guide

Use Claude Code's Opus plan and Sonnet execution route, then check the work and usage

Use Claude Code's opusplan route on a bounded repository issue, review the plan and code change, and compare whole-session usage only when the baseline and result qualify.

The big change

What changed: One Claude Code session can route planning to Opus and implementation to Sonnet at the Plan Mode boundary. The user still decides whether the proposed plan is sound before editing starts.

Why it matters: A developer can test a division of work between two model families on an actual issue while keeping the code change and acceptance checks in one reviewable task. The route alone says nothing about correctness or total cost.

What to watch: The decisive evidence is the approved plan, actual model and fallback observations, complete diff and checks, and usage from the entire session. Only a quality-matched, attributable baseline supports a saving for that task.

Read the full story
—
Back to the briefing
news

Claude Duet preview works in the background, with approval gates

Anthropic's Claude Duet preview can work through connected accounts after users close the app. US Pro and Max access is by waitlist; background use and approvals set limits.

The big change

What changed: Claude Duet moves an agent's work from an open chat session to a continuing cloud task with periodic account checks.

Why it matters: For people admitted to the US Pro and Max preview, work can be prepared while they are away. Background activity spends a shared usage budget, and consequential actions return to the user for approval.

What to watch: Users cannot observe or take over Duet's browser. Anthropic warns it may misread a thread or misjudge urgency; broader availability and real-world reliability remain unresolved.

Read the full story
—
Back to the briefing