Expected: GitHub Spark Retires August 31 After Closing to New Apps
Existing users have a short export window, while deployed apps should continue running and AI-powered projects need a replacement inference provider.
GitHub announced on August 4 that the current Spark experience on github.com no longer accepts new users or the creation of new apps. Existing users can still access Spark to export their projects, with retirement scheduled for August 31.
What is known
The intake closure began on August 4. GitHub says apps that users have already deployed will continue to work after Spark retires, but anyone who wants to keep editing an existing project should export its code before the deadline. The supported route is to open the app's Spark workbench and use the Create repository action.
GitHub frames the change as a shift toward integrated Copilot development in VS Code, Copilot CLI and the GitHub Copilot app. The retirement applies specifically to the current Spark experience hosted on github.com, so the announcement should not be read as a general retirement of every GitHub tool that helps users build with AI.
There is a separate dependency issue for projects that use Spark's `llm()` function. GitHub Models retired on July 30, and GitHub says those calls no longer work. Affected developers need to replace that function with another inference provider, supply their own API key and manage the resulting billing. Spark apps without `llm()` calls are not affected by that inference shutdown.
Why it matters
Spark offered a direct route from an idea to a hosted application. Its retirement moves ongoing development toward repositories and Copilot-enabled development environments, where users have more control over code but also take on more responsibility for setup, model access and costs.
The export window is therefore more than an archival deadline. Developers need to check whether a deployed app only needs its code preserved or also depends on inference that has already stopped working. Teams should inventory projects, export repositories and document replacement providers before the workbench closes.
What would confirm it
The retirement will be confirmed when GitHub removes existing-user access on or after August 31 while previously deployed apps remain reachable as promised. A revised deadline, an export extension or a successor experience on github.com would materially change this expectation.
Status
Expectation. Internal confidence is medium because the timetable and migration instructions come from GitHub's official changelog, but the future shutdown and post-retirement app behaviour have not yet occurred.
Sources
Update note: Last reviewed 2026-08-05. We will revise this post if GitHub changes the August 31 deadline, export process or deployed-app commitment.
Sources
Drafted with AI assistance from source briefs; reviewed for citation completeness and label accuracy.