LoginSign Up
← Back to all sparks
E

Expo

INFRA · APIS
Velocity6.3

Expo shut down its own agent and is wiring itself into the ones developers already use.

react-nativeeasmcp-connectorsagent-strategymobile-toolingci-cd
◆Current state
Expo wound down the Expo Agent closed beta in July, two months after making its MCP server free on every plan, and has now shipped a way to connect Expo from the Claude desktop app. Everything else in the window is core platform work: SDK 56 and 57, EAS Observe scheduled for general availability on August 20, a Maestro test insights dashboard, and automated iOS device registration in EAS Workflows.
◆Where it's heading
The pattern is conceding the assistant layer and defending the build, test, and deploy pipeline underneath it. Instead of competing for the agent surface, Expo is making project data reachable from whichever assistant a developer already runs — the free MCP server first, now a Claude desktop connection. EAS meanwhile keeps absorbing more of the release pipeline: observability heading to GA, end-to-end test insights, device provisioning automated.
◆Prediction
More connector and MCP surface for other assistant hosts is the likely next step, alongside EAS work around what is already in flight — particularly Observe once it reaches GA on August 20. The entries give no indication of whether the SDK release cadence changes as a result.

◆Recent moves

  1. 5d ago

    Connect Expo in the Claude desktop app

    Expo projects can now be connected from the Claude desktop app, extending the MCP server that went free on all plans in May into a specific assistant host. It is the constructive half of the same decision that ended the Expo Agent: rather than shipping its own assistant, Expo is making itself addressable from the ones developers already use. The feed carries only a headline stub, so the depth of the integration is not visible here.

  2. 29d ago

    Expo Agent: ending the closed beta and winding the project down

    ⚡ SPARK

    Ending the Expo Agent beta is the decision the rest of this window follows from: with no in-house assistant, the free MCP server and the Claude desktop connection become the strategy rather than a hedge. It marks the point where Expo stopped competing at the assistant layer and concentrated on the pipeline beneath it.

  3. 29d ago

    EAS Observe moves to general availability on August 20

    EAS Observe gets a general availability date of August 20, moving Expo's observability layer out of preview. It fits the pattern of EAS taking on more of the post-build lifecycle rather than stopping at compilation and distribution.

  4. 1mo ago

    Expo SDK 57

    SDK 57 lands roughly six weeks after SDK 56, holding the regular release cadence that anchors the platform. The feed entry is a headline stub, so the contents are not visible from this source.

  5. 1mo ago

    Maestro testing: insights, clearer results, and faster retries

    A Maestro insights dashboard tracks how end-to-end test runs performed over time across a team, aimed at identifying flaky tests and pinpointing when regressions entered. Together with faster retries, it is EAS deepening the testing stage rather than widening into a new one.

  6. 2mo ago

    Automate iOS device registration for internal builds in EAS Workflows

    iOS device registration for internal builds can now be automated inside EAS Workflows, removing a manual provisioning step from the internal distribution path. Small in scope, and consistent with EAS steadily automating the operational chores around shipping a build.