GitHub Spark in public preview for Copilot Pro+ subscribers

[tuves]

🆕 Community Manager Update: August 4, 2026

Hello everyone,

Beginning August 4, 2026, GitHub Spark no longer accepts new users or allows the creation of new apps. Existing users can continue to access GitHub Spark until August 31, 2026 to export apps they’ve already created. Apps you’ve already deployed will continue to work after GitHub Spark is retired.

We have provided details about the deprecation in this discussion.

If you have further questions or feedback, please comment directly on the discussion linked above.

---

Stuck between idea and implementation? Spending weeks on mock ups or docs that never ship? GitHub Spark takes you from idea to deployed app in minutes.

Build and ship full-stack intelligent apps using natural language with access to the full power of the GitHub platform—no setup, no configuration, and no headaches.

Key features

• Natural language to app: Describe your idea and watch Spark build it, with frontend and backend capabilities included, all powered by Claude Sonnet 4.
• No setup required: Data, LLM inference, hosting, deployments, and GitHub auth all included out-of-the-box.
• Add AI to your apps: Add intelligent features powered by LLMs from OpenAI, Meta, DeepSeek, xAI and more - no API key management needed
• One-click deployments: Publish your app with a single click.
• Build your way: Use natural language, visual editing controls, or code with GitHub Copilot code completions at your fingertips to iterate on your ideas.
• Create a repository: Get a repository with GitHub Actions and Dependabot incorporated in just a click. Everything stays synchronized so you aren't trapped in a sandbox.
• Expand with Copilot agents: Open a codespace directly from Spark to iterate with Copilot agent mode or assign an issue to Copilot coding agent.

Get started

Spark is available in public preview for Copilot Pro+ users, with rollout to additional customers coming soon.

Visit github.com/spark to build your first app.

Copilot Pro+ subscribers receive access as part of their plan. Spark messages use premium requests included in GitHub Copilot plans.

Learn more

• View more details on the Spark product page.
• Read the Spark documentation.

Disclaimer: The UI for features in public preview is subject to change.

[CurationsLA]

Looking forward to testing this out! Just started using GitHub. Great product.

[josekurian]

Great project

[visitoloke3d]

100% Excellent

[Shankar98183235]

GOOD WOOK

[DimitryGarces]

Great project uwu

[DrAldabsa]

Will done... Greet project

[askpt]

I was part of the technical preview but I cannot access the github.com/spark only the old link.

[1999Swarup]

same here, I am also unable to access the spark site. and the spark screen is going on loading.

[kelseyrae]

@1999Swarup Just granted you access as well! We're planning to roll out access to users of the technical preview imminently as model capacity comes online.

[Sandmanmmm]

I'm quite upset as I have a fully fleshed out project that I have been building up with Spark and now all of a sudden 13 days into the month I reached my total premium usage limit and it even let me double it which I am fine paying for but out of no where cut me off this evening telling I need to wait until the end of the month to even upload my Spark to the repository is crazy. I have been a loyal Spark user since day 1 and now my access is terminated right at the final stages in the project...

[JustBrowsingCiao]

same here I have github pro but can't access spark : /

[james-johnso]

same here I have github pro but can't access spark : /

Hi @JustBrowsingCiao I had the same issue. Actually, you need to purchase GitHub Pro+ (plus). The webpage I landed on does not have right URL to purchase Pro+ license. Try going to https://github.com/github-copilot/pro-plus and upgrade to Pro plus. From there, I found Spark available. I hope this works for you.

[McCrossin]

I have seen the email about this as well but the links don't work for me even though I'm a pro+ user.

[kelseyrae]

Can you share what you're seeing? If you are trying to open the links on mobile and you have the GitHub mobile app on your phone you may need to manually open the link in a mobile browser window.

[McCrossin]

Thanks that's probably the issue just tried checking it out on my commute.

[mohamedcherifmo]

I just registered to Pro plus and I'm unable to access the repo

[kelseyrae]

Can you share more about what errors you're seeing? You should be able to access it at github.com/spark if you have a Pro+ account.

[guygregory]

Are there any plans to (eventually) make GitHub Spark available to students?

[kelseyrae]

Yes, no concrete date yet, but we are planning to roll out to additional customer segments in the coming weeks and months.

[CurationsLA]

Remember me! Game changer.

[PYRTUS1997]

[pasinduisuranga]

That's great news about GitHub Spark for students! I'm really looking forward to it.

[luyandadhlamini2]

The concept looks great. I've tested it on a sample app. Agent was able to build a usable MVP, but there are teething issues.

Current issues:

1. App keeps refreshing & can't be interacted with.
2. Clicking on publish shows a loading icon next to the word "publishing" & doesn't publish the app.
3. Attempting to open the app in a codespace failed, returning a NETWORK_ERR.
4. Since the app keeps refreshing, feedback can't be provided to the agent to make changes, I assume because the agent waits for app to load before being able to accept input.

My recommendation:
While in preview phase, assign each Spark a UUID (instead of a 20 character name as is currently done) so that we can provide our spark links for the github team to debug & see issues.

@tuves
@kelseyrae
@ghostinhershell

[kelseyrae]

@luyandadhlamini2 Thanks for flagging these! Are you able to share the link to your spark(s) where you were seeing these issues? We can dig in to see what's up.

Regarding the app refreshing - we do load the last stable state of your spark while agentic iterations are in progress. You should be able to interact with your spark during this time, but you won't be able to make other manual changes (in code, data tab, prompts tab, deploy etc). Once the agent finishes your iteration, all of the editing and deploying etc capabilities reactivate.

[Moose1988]

I'm having this exact same issues. Will this be fixed soon?

[mpommrehn]

What is the privacy policy for Spark? Asking relative to a corporate account that includes Copilot (not sure which level), with strict limits on AI usage, only as managed through Copilot under the MSFT Corporate/Enterprise Privacy Policy.
Need to see whether Spark prompts, code, and any generated artifacts are fully contained within the same corporate privacy data wall as the rest of our Copilot usage.
If not now, is that a future intent?
Thanks!

[kelseyrae]

Hi! You can read the data usage policy for all pre-release products like Spark here: https://docs.github.com/en/site-policy/github-terms/github-pre-release-license-terms#4-data-collection-and-usage

If you have any questions please let me know.

[between-sky-sea]

Does spark allow for custom domain?

[kelseyrae]

Not technically, but the URL for your deployed spark is based in part on the name of your spark, which you can change in the settings view.

We automatically manage routing of old domains to new domains if you change the name of your spark after deploying, so you don't need to worry about sticking to a single name of your spark once you deploy.

[mgyarmathy]

Do you plan to incorporate GitHub Organizations into the Visibility settings for deployed apps? Anyone with the link seems quite limited and insecure for internal enterprise apps. @pgahq would be more likely to adopt this if you would enable the use of other Identity Providers (e.g., Okta) instead of Github authentication.

[kelseyrae]

Yes! It's a feature we are actively working on, coming soon.

[mgyarmathy]

Great! We're eager for it!

[agim]

What coding platforms does spark use to build apps?

I asked it to use rails and it decided to use react.

[kelseyrae]

We only support Typescript and React. This is so we can ensure we get users to a deployable app. If you want to use a specific stack, we recommend using Copilot agent mode in VS Code or Copilot coding agent. We see users sometimes start with a prototype of their idea in Spark, then assign an Issue to Copilot coding agent to migrate it to a different language/framework.

[dahatake]

I really want to attach functional requirement document at the first phase. Today we can attach only image to UX/Data prototype.
After initial app is up, I clone to repo to keep work colleague include GitHub Copilot.

[kelseyrae]

Thanks for the feedback! This is also on our radar - coming soon.

[mhitza]

Needs a bit more time in the oven. Gave it initial prompt (asked react native, generated some kind of plain react application), didn't implement all the features requested. Asked it to fix a bug, then to implement a separate feature and I got hit with a too many requests error (429). These where 3 requests over the span of what I would call an hour (prompted and went afk for a while each time).

[kelseyrae]

We don't support React Native currently. Only Typescript and React.

Unfortunately it looks like you were trying your request when we were experiencing some overall system capacity constraints (more users were trying to build in Spark than we had available model capacity to support), so some users including you ended up getting rate limited. We've expanded model capacity, so if you'd like to give it another shot you shouldn't run into the same issues.

[himanshu2s]

🔧 Feedback on GitHub Copilot Spark Completion

📌 Subject:

Inaccurate and incomplete completions despite clear and structured prompts

---

🧠 Context:

The backend API is fully operational at [http://localhost:59756/swagger/index.html] and MongoDB is running at [mongodb://localhost:27017]. The frontend (React) was instructed to:

1. Remove all mock data and use the working backend endpoints.
2. Fix the subscription button visibility and interaction bugs.

However, Spark repeatedly responded with messages like:

"All tasks are complete", "Everything is resolved", or "System is working perfectly" — despite nothing being fixed or functional.

---

❌ Core Issues Observed:

• 🔁 False Completion Loops
  Spark asserts success even though the UI remains broken, mock data persists, and real API is not being called.

• 🧩 Lack of Real Integration
  It failed to replace mock logic or wire API calls into the existing UI components.

• 🧪 No Functional Validation
  There was no change in behavior — backend calls were not triggered, nor were frontend bugs fixed.

---

💡 Suggested Improvements:

1. Stateful Prompt Awareness
   Spark should evolve the code based on past prompts and the working system context (like functioning backend endpoints).

2. Backend–Frontend Integration Logic
   When both parts are present, Spark should intelligently connect them, using fetch/axios properly and handling responses.

3. Accurate Task Completion Messaging
   Avoid confirming completion unless issues are demonstrably fixed (e.g., API hits succeed, buttons render properly).

---

✅ Desired Outcome:

A more reliable Spark experience that:

• Replaces mock data with actual API usage,
• Fixes UI rendering bugs (like the disappearing button),
• Connects frontend components to backend endpoints seamlessly,
• Aligns environment configs correctly (CORS, ports, base URLs),
• And avoids misleading "success" messages.

---

Please let me know if code snippets, repo access, or error screenshots are needed for deeper review.

[kelseyrae]

Thank you! Super helpful feedback. If you're able to share any screenshots, link to your repo etc we can take a deeper look.

[KnightNiwrem]

I frequently get the error

Failed to commit AI iteration: Git commit failed: Command failed with code 128: fatal: ambiguous argument 'HEAD': unknown revision or path not in the working tree. Use '--' to separate paths from revisions, like this: 'git <command> [<revision>...] -- [<file>...]'

When creating a new Spark. This prevents further iterations, as the Spark will throw

Failed to submit prompt: Error: Request timeout

when given an iteration prompt.

If I tried to create a repository when it is in this error state, it would simply throw

Failed to fetch

[alexagillman]

@KnightNiwrem Hey! Mind clicking open in codespace and running git commit -m "test" and letting us know what the failure message is?

Any chance you have gpg signing on your commits?

[KnightNiwrem]

@alexagillman The error message is:

@KnightNiwrem ➜ /workspaces/spark-template (main) $ git commit -m "test"
error: gpg failed to sign the data:
[GNUPG:] BEGIN_SIGNING
2025/08/02 01:39:14 error signing commit: error signing commit: error making request: 403 | Current user User does not have push access to this repository, error making request: 403 | Current user User does not have push access to this repository
fatal: failed to write commit object

---

I usually sign my commits and have GPG keys in my account settings.

[alexagillman]

This should be fixed now! Let us know 😄

[KnightNiwrem]

@alexagillman I can confirm that running a couple fresh Sparks (to test) no longer produces the git error.

Will need to wait till they are stale-r to see if they run into the other CORS error.

[pescerosso]

After a bunch of prompts I am facing the same issue: Failed to submit prompt: Error: Request timeout

[hiarun02]

amazing project

[askpt]

I have been testing it in Edge but it seems it is not working in Safari. Tried to look into the release notes and cannot find any report stating it is not supported in Safari on macOS. Is that expected?

[eljog]

Due to some browser limitations in most Safari versions the in-app preview functionality may not work. I believe you might have presented a banner on the first load as in the screenshot below. This Banner will not pop up again if you have once acknowledged that the cookie access is enabled.

[MasayukiOzawa]

It appears that the GitHub Spark limit has been reached, and the following message is now displayed.

I couldn't find any information about rate limits. How much usage will result in restrictions?

[james-johnso]

Yesterday, I signed up for Copilot Pro+ and I am not able to access Spark. See screen shot below.

Can you check into this? Thank you.

[devantler]

Hi there, I’m also experiencing access issues with Spark. I’ve enabled access at the enterprise level for my GitHub Enterprise (DevantlerTech) but I’m still unable to access it. I’m subscribed to the Copilot enterprise plan.

I’ve had Spark access enabled since the option appeared in the enterprise policy settings, hoping it was just a delay. However, it seems there’s a bug here.

I tried contacting support but they referred me to this discussion where I found this related thread.

Could you please help me?

[jasonrclark]

Hi @devantler. I took a look at your record and found that this is tripping over one part of our logic being overly restrictive. I'm looking into getting that fixed and will let you know when it lands.

[jasonrclark]

@devantler Fix has landed for this. The cause was because you're a member of multiple enterprises, but we're now allowing folks in if at least one enterprise enables Spark. Let us know if that doesn't work for you.

[ANT0071]

:-×

[devantler]

@jasonrclark thanks Im in wohoo 🎉

[lshen8]

I have noticed that the GitHub repo the spark created and committed to is not always up-to-date with latest change? am I missing something?

[eljog]

The changes are only pushed up to the repo when it is committed. We do commit them at certain checkpoints such as before/after performing a prompt based iteration.
You can always perform a manual commit from inside the codespace if necessary - but changes are never lost regardless if you commit or not

[grze87]

Can you share roadmap for Spark?

[Sandmanmmm]

I'm upset as I have a fully created a robust project up with Spark and now all of a sudden 13 days into the month I reached my total premium usage limit and it even let me double it which I am fine paying for but out of no where cut me off this evening telling I need to wait until the end of the month to even upload my Spark to the repository is crazy. I have been a loyal Spark user since day 1 and now my access is terminated right at the final stages in the project... I have put dozens of hours into this already and you just pull the plug on me.

[eljog]

Hi @Sandmanmmm thanks for reporting this.
Let me double check the limits and get back to you

[eljog]

The compute limits issues are adjusted.
Thanks again for trying Spark - since you often run into Compute limits; just curious to understand how you typically work with Spark. Do you work on multiple of them side by side? Each spark workbench instance is served by it's own backing compute, and can accumulate into the compute usage quota.

[vs2explore]

I’ve been using Spark and it’s been working well so far, but I noticed there isn’t an option to deploy to the cloud, such as Azure/aws. Has anyone managed to set up an app created with Spark on Azure?

[justinmcbride]

Hey there!

I noticed there isn’t an option to deploy to the cloud, such as Azure/aws

We do have the ability for you to "Publish" your application directly from the Spark UI. It will automatically be published to globally-distributed infrastructure and available depending to different users depending on the visibility settings you choose in the publishing dialog (all of GitHub, to a specific GitHub organization, or to only yourself). More options for sharing and collaborating will be coming.

Has anyone managed to set up an app created with Spark on Azure

I haven't tried this myself, but you should be able to export your Spark to a repository, and then add the necessary infrastructure to publish your spark using the Azure instructions (such as Azure's Container Apps).

[CurationsLA]

Hi @eljog, can you kindly look into my limits, etc.? Spark has hung up on me, close to deployment for a project. Kindly let me know if you have any questions. Thank you!

[alexagillman]

Hi @CurationsLA, are you still seeing issues?

[Firstmeridian]

https://docs.github.com/en/billing/concepts/product-billing/github-spark#billing-and-limits-for-spark-app-deployment
According to the billing and limits for Spark app deployment, what are the specific deployment quotas?

[Firstmeridian]

Why can't I publish, and how soon can I republish?

[eljog]

Screenshot indicates that All changes are published. That is the reason why the Publish button is disabled.

However if your case is that you have newer changes that are not detected in the publish dialog, it is likely related to a known edge case that we are working on. We will update you once that bug is resolved.

Thank you for reporting

[Firstmeridian]

I did have new changes earlier that were not detected in the publish dialog, but that issue has already been resolved — thank you for the fix!

However, I’ve now encountered another problem that has persisted for over a week:

GitHub Spark is consistently stuck on the “Loading…” state. This issue occurs even after refreshing the page multiple times. The Spark editor becomes unusable because the preview never loads, and some actions (such as switching iterations) become unavailable.

[Firstmeridian]

GitHub Spark is consistently stuck on the “Loading…” state. This issue occurs even after refreshing the page multiple times. The Spark editor becomes unusable because the preview never loads, and some actions (such as switching iterations) become unavailable.

[radu985]

Thanks for the update, @Firstmeridian!
Sorry to hear it’s still not working let’s try a few deeper checks.
First, please confirm that GitHub Copilot Labs and Copilot Chat are both updated to the latest versions.
Try signing out and back into GitHub in your browser or editor.
If you’re using VS Code, check under View → Output → GitHub Copilot for any visible error messages.
If possible, navigate to Settings → Copilot → Reset configuration (in VS Code) to clear the local settings cache.
Lastly, if none of this helps, could you share which browser/editor and OS you’re on? That’ll help me narrow it down.
Thanks for your patience I’ll figure this out together.

[Firstmeridian]

My browser is Edge, and my OS is Windows 11 25H2.
I use GitHub Spark in the browser.

[radu985]

Thanks, @Firstmeridian!
Since you’re on Edge with Windows 11, please try opening Spark in a new InPrivate window.
If it still shows “Copilot is working…”, clear site data for github.com and disable extensions (like ad blockers).
Also, check githubstatus.com for any ongoing issues.
Let me know if it happens on all repos or just some that’ll help us narrow it down.

[Firstmeridian]

I cleared site data for github.com and disable extensions. But it still shows “Copilot is working…”. The “Restore” button and the “Send” button (in the input area) are also not working.
In fact, I only have this one GitHub Spark repo, so I’m not sure whether it happens on all repos. Should I create a new GitHub Spark project to test it?

[Firstmeridian]

My GitHub Spark started working normally again today, and I didn’t even do anything. It’s strange, but thanks for fixing it. :)

[ToxiKejtor]

Hey, Spark stopped working for me. It doesn't work on new or existing projects. Here is the error I get in the network tab: "Cannot read properties of undefined (reading 'canEdit')". I work on Mac, and I tried both Chrome and Safari. There is nothing on githubstatus about it

[justinmcbride]

👋from Spark: Sorry about that -- a small error was introduced over the weekend but as of about an hour ago, this should be resolved.

[radu985]

👋from Spark: Sorry about that -- a small error was introduced over the weekend but as of about an hour ago, this should be resolved.

Really???????????????

[ebndev]

🆕 Community Manager Update: August 4, 2026

Hello everyone,

Beginning August 4, 2026, GitHub Spark no longer accepts new users or allows the creation of new apps. Existing users can continue to access GitHub Spark until August 31, 2026 to export apps they’ve already created. Apps you’ve already deployed will continue to work after GitHub Spark is retired.

We have provided details about the deprecation in this discussion.

If you have further questions or feedback, please comment directly on the discussion linked above.

Thank you!