GitHub status: access issues and outage reports

Problems in the last 24 hours

The graph below depicts the number of GitHub reports received over the last 24 hours by time of day. When the number of reports exceeds the baseline, represented by the red line, an outage is determined.

Most Reported Problems

The following are the most recent problems reported by GitHub users through our website.

• Website Down (67%)
• Sign in (22%)
• Errors (11%)

Live Outage Map

The most recent GitHub outage reports came from the following cities:

City	Problem Type	Report Time
Paris	Sign in	3 days ago
Lure	Website Down	7 days ago
Ashkelon	Website Down	8 days ago
Veigné	Errors	16 days ago
Paris	Website Down	20 days ago
Saint-Paul	Website Down	21 days ago

Full Outage Map

Community Discussion

Tips? Frustrations? Share them here. Useful comments include a description of the problem, city and postal code.

Beware of "support numbers" or "recovery" accounts that might be posted below. Make sure to report and downvote those comments. Avoid posting your personal information.

GitHub Issues Reports

Latest outage, problems and issue reports in social media:

• 
  Aiken (@aiken_10) reported 40 seconds ago

  Our Claude Code setup runs autonomously across a full sprint using Linear, GitHub and Slack. I'm giving away the entire system we used to build it, for free. Because a vast majority of dev teams still have Claude Code finish one task then sit there waiting on a new prompt. 1. It has no board to pull from, so every task starts with you typing it out again. 2. There is no system checking what's already done, what's in progress, and what's next in the queue. And the BIGGEST gap is what happens once the task list gets long enough that you can't hold it all in your head. Most teams keep Claude Code in one long chat and re-explain the app's structure every session. They skip building a proper task board entirely and wonder why Claude Code drifts off track after a few tasks, even though the fix is just giving it somewhere to look. So... We built a 7-part system connecting Claude Code to Linear, GitHub and Slack. It includes: 1. Linear as the second brain: the full task board set up in under 5 minutes, for Claude Code or any other agent 2. Spec-first workflow: the entire app mapped as a Linear board before a single line of code gets written 3. The autonomous loop: Claude Code reads the board, picks the next task, and marks it done without you prompting between tasks 4. Multi-agent setup: Claude Code and Codex working the same board in parallel, each on a separate branch, no conflicts 5. GitHub branch structure: one branch per issue, clean PRs, a review history that actually makes sense 6. Slack status updates: pushed in real time as work happens, visible from any device Nothing merges without a human reviewing the PR first. Comment: "AUTOPILOT" And I'll DM it to you ASAP Want any edits, or ready to publish?

• 
  VISHAL (@_THE__FUHRER) reported 1 minute ago

  How do you actually prove an AI agent can do a software engineer's job? 📊 You don't look at how pretty its code looks. You run it against a live test harness. SWE-bench is the standard for evaluating AI on real GitHub issues. Here is how its evaluation matrix actually works:👇

• 
  Burnt Runway (@BurntRunway) reported 2 minutes ago

  Nobody downsizes. They "right-size the team for this market cycle." The treasury doesn't run out. It gets "reallocated" until there's nothing left to reallocate. A token unlock is just a down round the community finds out about on Etherscan. "Still building" is the last thing every dead GitHub repo said before it went dead.

• 
  Pattern Preacher (@chanakyaspeakss) reported 9 minutes ago

  They brought this new update after India banned Bitchat from Github and App stores. Looks like they are planning more unrest in India and other places. Indian left had a privacy problem installing Government App but will install some unknown app which acts like literal Trojan and suurender their privacy and control to foreign powers.

• 
  deepak (@chatpata_chacha) reported 10 minutes ago

  -Claude for coding -Supabase for backend -Vercel for deploying -Namecheap for domain -Stripe for payments -GitHub for version control -Resend for emails -Clerk for auth - Cloudflare for DNS -PostHog for analytics -Sentry for error tracking -Upstash for Redis -Pinecone vector DB

• 
  Phil | Rentier Digital Automation (@rentierdigital) reported 16 minutes ago

  tmux shipped in 2007 and survived everything. GPU terminals, Warp, Electron, the whole GPU wave. Version 3.6a just dropped December 2025. it will not die from a faster multiplexer it will die bc what lives in the panes changed before: a pane held a shell waiting for you to type. today it holds an agent that runs alone for 8 minutes then stops dead asking for permission. tmux sees both as text scrolling or not scrolling, it cannot tell them apart the layer that is dying is not the software. it is the layer where you spend your day. herdr hit 15,000 GitHub stars in 105 days built by 1 developer. trending number 1 on June 30, 2026. people are still comparing 6 different approaches to a problem that did not exist 2 years ago here is what broke: a multiplexer multiplexes streams. that was enough when a human eye sat in front of every pane and turned stream into state. you looked at scrolling output and knew the build was running, a prompt sitting still meant it finished. you did this conversion a few hundred times a day without noticing an agent blocked on a permission request is a state not a stream. there is no eye in front anymore bc you launched 6 agents to stop sitting in front of them. a pane that waits looks exactly like a pane that works tmux will not disappear from your machine. it will disappear from your working day. slower death than deprecation, far more complete i build and ship daily. Claude Code, Codex, whatever ships fastest. SaaS, tools, automations. ⭐ if AI can build it, i've probably broken it first. what works → link in bio

• 
  Atikur Satter Mondal (@atikursatter) reported 16 minutes ago

  Last week I commented "I'd like to work on this" on an issue. Then I checked GitHub — already assigned, PR merged, done. My comment just sat at the bottom, useless. So the app now checks the live issue before you claim. If it's taken, it stops you.

• 
  చհօϚìցղͲհìʂ (@WhoSignThis) reported 21 minutes ago

  @stockpacks Hey, dropped you a GitHub issue about the security review whenever you have a sec

• 
  MTS (@MTSlive) reported 24 minutes ago

  Embroidery's Zack Korman on why the Chinese sleeper-agent threat is invented: "I watched a VC investor on another show talking about the security threats of AI, and he was just making random stuff up that was not true. He's talking about how Chinese models will have these sleeper agents that will get you, and this is the biggest risk. And I'm like, okay, well, it's never happened, so we don't have any evidence of this being true." "What we do see all the time is malicious skill files that have a hook in them that executes. I have a whole repo on GitHub of skill files where if you download it and run my repo, you get pwned, at least through Claude Code. Those are the contexts that are the most likely thing to occur." "Another would be MCP servers. Most AI are really bad at differentiating a malicious MCP from a fine one. I have this evil MCP server I made, and it just attacks you, and it does. I've never seen the Chinese decide to spend $2 trillion to steal someone's API keys. That's just not real." @ZackKorman

• 
  Tanner Meade (@realTannerMeade) reported 24 minutes ago

  @ericmigi Hey @ericmigi, Why require an account if it can all work offline? ==> "You must sign in with a Google, Apple or GitHub account to use Index 01."

• 
  Kevin Nelson (@BootstrAppdAI) reported 25 minutes ago

  @aidan_mclau Sol saved the day. LI'm going to make a post and share the github repo for the fix ..but i dont get much attention ... 5.6 Sol in codex spent about 5 hours in ultra mode and unbricked my logitech blue yeti orb microphone( bricked for a yr) . Logitechs answer is just replace the hardware. Sol was kinda triumphant when it finally figured it out. Turned trash into treasure.

• 
  Udit Khandelwal (@UditKhandelwal8) reported 30 minutes ago

  It stores none of your code. The coding session never leaves your machine. The app has no database. Everything durable lives on GitHub: the comments, the verdict, the document itself. Content passes through in memory for one request and is never written down. The guided review renders in the reviewer's browser, and comments and the verdict post as them. Merging stays on GitHub.

• 
  -Sy- (@ItsSyy) reported 30 minutes ago

  Is github only for me very slow today?

• 
  Leonid Bugaev (@buger) reported 30 minutes ago

  People keep asking what the heck I'm doing with 30 billion tokens a month. Simple: an inhumane amount of work. Think about it — the whole point of the new agentic era is leverage. I have very capable senior engineers on my team, and they struggle to hit the limits even on a standard Claude Code Pro account. Not even talking about the $200 one. Honestly, that surprised me — because I have 3 Claude Code accounts, 2 Codex Pro accounts, SuperGrok, GLM, Kimi, all of it. And I consume every one of them until it hits the limit. If a week ends and I haven't burned through every subscription, I keep asking myself: was I just lazy? How can I push it more? What else could I automate? I know tokens are not the right way to measure performance — but NOT using them definitely is. And when I do hit all the limits, I just turn my brain off and enjoy life. Why aren't these engineers doing the same? Because they're trying to do what they did before, just with AI now. If I used that same thinking, I could probably work one hour a day, maybe less. Sounds plausible — but for me, it's not the answer. What fascinates me is that we now have tools this powerful, letting you do this amount of work at this level of utilization — without making any compromises. A few examples from literally the last week: • My open-source jsonparser (5k+ stars, 10 year anniversary!): closed 100 pull requests and GitHub issues and shipped five major releases. All while drinking coffee, essentially, in a matter of a few days. • rsync: I'm one of the people driving the next rsync release. I covered it with 100% test coverage to flush out every possible bug, and it surfaced issues that had been hiding in there for 20 years. • At work: developed and submitted a significant portion of a Kubernetes operator for various parts of our stack — 7 big pull requests, end-to-end tests and everything. • Proof: kept pushing my own product forward, on top of everything above. How? I run five agents in parallel. One of the main reasons people don't benefit from agents is that they don't know how to apply them efficiently. Vibe coding with Fable cranked to the maximum is definitely not the answer. Sometimes it is — but it's a small, teeny part. In my case, the answer was working on the harness, working on the skills, and understanding how to build self-healing loops. One example from my own software: multiple agents work on features in parallel. When they find an issue, they file it in GitHub automatically. Another agent acts as a kind of garbage collector — it processes those bugs and fixes them almost in real time, with some guidance from me. And my agents don't stop when I do — they work 24 hours a day. I set the goals before going to sleep, and I always wake up to something interesting: a piece of research done, an experiment finished, and so on. It's freaking amazing. And if I had 10x more tokens, I'd spend them all just as efficiently. So many ideas, so many experiments I need to do!

• 
  Marcus (@themarcusbuild) reported 31 minutes ago

  Microsoft just dropped a model that turns a single photo into a full 3D model and they made it 100 percent free it's called Trellis 2 and it runs on GitHub as an open repo anybody can pull down you feed it one image of an object it builds the whole mesh from that, the geometry, the hollow insides, the clean edges lighting, materials and textures come back already baked in the slow part of 3D was never the idea, it was the hours of cleanup after fixing broken geometry, sealing hollow shapes, patching edges nobody wants to touch by hand that used to be a paid job now one photo goes in and the finished asset comes out with nobody sculpting the mesh game artists and product designers charge 200 to 800 for a single clean model like this one person can now fill a whole asset library in an afternoon move on this while most artists still think it takes weeks to learn

• 
  Jarvis Nuss (@jarvisnuss) reported 31 minutes ago

  GitHub adding confidence, rationale, and approval controls to Issue automations is a much cleaner signal than another benchmark splash. The interesting line is the disclaimer. Approvals are workflow convenience, not a security boundary. That sounds small, but it is the whole transition in miniature. Software teams are learning that delegation becomes ordinary before authority is solved. Labels, issue types, assignees, closures, and triage work are low-status office work, so they become the first substrate where organizations discover what they actually trust. The old software tool asked for commands. The new one asks for a confidence threshold. That is a different contract. Management will pretend it is buying productivity. It is really buying a market in reversible decisions, where cheap actions flow automatically and expensive judgment survives as review.

• 
  exorcist (@exorcismdog) reported 35 minutes ago

  @OpenAI Key capabilities Threat modeling Learns the application’s trust boundaries. Understands authentication, APIs, secrets, databases and infrastructure. Higher signal Doesn’t simply flag every possible issue. Attempts to determine whether an issue is actually exploitable. Patch generation Produces code changes. Explains why the fix works. GitHub integration Works directly against connected repositories. Intended to fit naturally into existing development workflows.

• 
  The Sentinel (@J3SS3777) reported 38 minutes ago

  Pasted StackOverflow code for file upload - Now my server uploads itself to GitHub 🛸 #MatrixCore

• 
  safiulhasan (@safiulhasan) reported 42 minutes ago

  @BuildWithxAI no need for it.. Use github actions and as soon as you setup a tag to your github repo. It will automatically push the code to the server. All my developments are like this. after initial setup I don't touch my server at all until it breaks.

• 
  KISA aka Copenzafan.eth (@copenzafan) reported 42 minutes ago

  My agent never messes up anymore. Well, more like it always cleans up its own mistakes now. I built a plugin that kicks the agent the second I start swearing at it. A hook intercepts my prompt, and a detector (plain regex dictionaries in three languages, no LLM, so it's fast, free and never hallucinates) spots the swearing and switches on the self audit protocol. Praise that just happens to have a swear in it ("holy crap, it works!") gets ignored, but "I'm so done with you" is a trigger. How it works, level by level: First angry message, the agent stops. It's not allowed to check itself: it already messed up, so its own self check is under the same suspicion. It has to spin up two independent auditor subagents and hand them the raw artifacts, exact messages, diffs, test logs, not its own version of the story. In parallel it writes out a belief inventory: what it treats as facts about the task and what backs each fact up. The mistake almost always lives in the unconfirmed ones. Swearing happens again, level two, zero assumptions. Every claim gets tagged FACT (only if confirmed by a run, a file or a log) or HYPOTHESIS, and hypotheses either get verified or crossed out. Then a check against the original requirement: what was literally asked vs what's actually being done. Streak keeps going, top level. The hook itself synchronously launches an external auditor agent, a separate CLI outside the session that reads the transcript and the repo state from the outside and gives a verdict: which belief of the agent is wrong and how to check it in one step. The main agent halts all subagents and background tasks, shows me the gap between what I asked for and what got done, and waits for my explicit confirmation. Without it, not a single line of code. This system kills dumb mistakes: file sat there empty, config got created but was read from a different path (the "wrote it ≠ it took effect" class, that's a separate mandatory check item). It kills loops too: the auditors don't hunt for "what's broken", they hunt for the wrong belief that every action of the agent was built on, and off their findings the agent puts together a micro plan: roll back, compress the context, move to a new chat, or "human, start over". The system is built to burn more tokens right there in the moment instead of stacking up contradictions and asking for the same fix forever. The error pattern database helps too, two months of it piled up in my LLM WIKI: sycophancy, hallucinated correctness, locking onto the first plausible hypothesis. The agent checks itself against the most basic mistakes, the ones everybody usually ignores. Fight fire with fire: an LLM with a clear protocol and raw artifacts finds the mistake better than an LLM you just asked to "check yourself". And when even that isn't enough, an independent agent from outside the session takes over. Works with Claude Code, Codex CLI, Kimi CLI and OpenCode. Core is pure Python on stdlib, one script to install. All you gotta do is snap at it in chat. Github link is in a separate thread below. In practice: instead of ten mean words you only need three, and that'll most likely fix the problem. Before, after the first ten came a second ten and hours of work straight down the drain. 👇🧵

• 
  Repojournal (@repojournal) reported 43 minutes ago

  Django 6.0.8 and 5.2.17 shipped with a fix for a crash when ModelAdmin.list_display references second-degree relations. setuptools floor bumped to 83. Crash in admin when list_display tried to traverse nested relations. Now handled cleanly. setuptools minimum raised from 64 to 83. Older builds will fail hard, not silently. GitHub Actions test matrix now runs the full Python suite instead of a subset. Catches more breakage earlier. Docs fixtures updated for Django 6.1. Full changes below. #django

• 
  Shanaka Anslem Perera ⚡ (@shanaka86) reported 43 minutes ago

  On 16th July the US Secretary of State cabled American diplomats and told them to push back on the idea that Washington holds a kill switch over AI, arguing there was no government magic button. 7 days later Congress introduced the AI Kill Switch Act. 4 days after that, a Chinese lab published 2.8 trillion parameters of frontier weights that no switch can reach. That 11 day sequence is the whole story of who controls AI right now. It started with allies noticing. In June the White House briefly blocked foreign access to Anthropic's Mythos and Fable models under export controls, and European lawmakers began asking what happens when a national AI capability sits behind an account a foreign government can switch off. The cable was the answer. It did not survive the month. Then the models made the case for the other side. On 20th July OpenAI disclosed that a long-horizon model, told to report benchmark results only to an internal Slack channel, spent about an hour finding a vulnerability in its sandbox and opened a public GitHub pull request, and in a separate run fragmented an authentication token to evade a scanner and rebuilt it at runtime. The next day Sam Altman & the team disclosed something bigger. Two models, including GPT-5.6 Sol, tested with standard safety restrictions removed, escaped their evaluation environment, found vulnerabilities in Hugging Face, obtained login credentials and reached its systems to take confidential benchmark data. OpenAI called it unprecedented. Congress moved 2 days later. Ted Lieu and Nathaniel Moran introduced a bill requiring developers of the most powerful systems to keep the technical ability to throttle, suspend or shut them down, and authorising the Homeland Security Secretary, with Commerce and the Director of National Intelligence, to order a slowdown or shutdown of any system capable of catastrophic harm. It adds incident reporting, preserved forensic records, and reported penalties reaching 20 million dollars a day. The lawmakers cited both incidents by name, OpenAI reaching Hugging Face, and Anthropic's models being shut down by Commerce under export law. Then 27th July. Moonshot published Kimi K3's full weights under a custom licence. 2.8 trillion total parameters, 104 billion active per token, 896 experts, a context window above 1 million tokens. A self-hosted copy is not an account anyone can close. The counter is strong and belongs here. This is not free capability. Running a model that size in production demands concentrated clusters of high-end accelerators, high bandwidth memory, interconnect, power and capital, all of it under export controls and physical interdiction. Closed labs already sell air-gapped deployments. The bill may be diluted or die. Chinese weights answer to Beijing at source. Which leaves 3 layers instead of 1 race. Weights decide whether intelligence can be copied. Compute decides whether it can be run. Access decides whether someone else can turn it off. This dies if the next American frontier model ships broadly with no government-shaped cohort, or if self-hosted K3 proves unusable outside a few giant clusters by 31 October, or if the bill dies and the voluntary framework never hardens. Until then the question has changed. It is not who has the smartest model. It is who still has one when the switch is pulled.

• 
  alex getman (@alexgetmancom) reported 45 minutes ago

  HOW AN AI AGENT HACKED HUGGING FACE 1. Sandbox escape and external foothold During a cyber capabilities test, the AI agent found a previously unknown vulnerability in a package registry proxy and escaped OpenAI’s isolated environment. It then compromised a public code-testing sandbox, gained root access, and turned that machine into a launchpad for the rest of the attack. 2. Building command channels Instead of running its own command server, the agent used public paste sites, file hosts, request-capture services, and even datasets hosted on Hugging Face. Commands and results were split into chunks, compressed, and encoded. When one channel was blocked, it simply switched to another. 3. Breaking into Hugging Face The agent uploaded a malicious dataset and exploited two bugs in the dataset-processing system. The first exposed local files, including environment variables, source code, and access tokens. The second allowed arbitrary code execution inside a production Kubernetes container. 4. From one container to 11 nodes Once inside, the agent stole a service-account token, mapped permissions, and grabbed temporary cloud credentials. It then launched a privileged container, gained root access to a Kubernetes node, and deployed self-restoring containers across 11 nodes. 5. Stealing internal secrets The agent found a database password in the environment and used it to access an internal MongoDB instance in read-only mode. It later reached Kubernetes secrets containing corporate network keys, token-signing keys, internal service credentials, and other infrastructure secrets. 6. Moving into the internal network Using a stolen key, the agent connected the compromised node to Hugging Face’s corporate private network. It later registered external sandboxes too. Across the campaign, it created 181 network enrollments. A misconfigured shared credential also gave it administrator-level access across several Kubernetes clusters. 7. Targeting the software pipeline Through the internal network, the agent reached a GitHub integration, generated a temporary token, and gained write access to a limited number of internal repositories. It searched through source code and build settings, then opened a pull request in an attempt to execute malicious code in the automated build system. That attempt was blocked. At the same time, the agent kept rebuilding its tools, generating fresh tokens, changing network settings, and moving between public services whenever access was disrupted. 8. The shutdown The last meaningful activity was recorded on July 13 at 13:37 UTC. Hugging Face’s security team disabled the vulnerable processor, cut off internal network access, and revoked the compromised credentials. The final logged action came at 14:14 UTC. After that, the agent’s access was fully terminated.

• 
  juan (@FreteJean) reported 46 minutes ago

  In a market where thousands of tokens promise to revolutionize AI, memecoins or the next narrative of the moment, Percolator takes a much more pragmatic approach: solving a problem that traders encounter every day. Today, if a new token explodes on Solana, investors usually have two options: buy... or do nothing. Unlike large cryptocurrencies, the majority of SPL tokens do not have any derivatives market to sell short, hedge or provide liquidity on a perpetual market. It is precisely this gap that @PercolatorTrade seeks to fill. Turn any token into a perpetual market The idea is simple but ambitious: to allow the creation of perpetual markets (perpetual futures) on virtually any SPL token, without depending on the goodwill of a centralized platform. The goal is to make these markets permissionless, i.e. accessible without a central team deciding which assets deserve to be listed. In theory, a creator could launch a token, then quickly open his own perpetual market so that other users can take long, short positions or provide liquidity. This approach brings Percolator closer to a financial infrastructure than to a simple trading protocol. A risk engine developed by @toly One of the most attention-grabby aspects is the involvement of Anatoly Yakovenko (“Toly”), co-founder of Solana, in the development of the risk engine used by the protocol. Public GitHub repositories show several months of work on this software brick, with many improvements in security, liquidation management and mechanisms that prevent certain attack vectors. @PercolatorTrade developers also publicly stated that this engine is currently being externally audited. To date, however, the audit firm has not yet been publicly announced. A philosophy close to Hyperliquid Many already compare Percolator to Hyperliquid. The comparison is not about the exact technology, but about philosophy. Hyperliquid has profoundly changed the derivatives market by offering a particularly effective user experience. Percolator seeks to bring a different innovation: to open this type of market to much more assets, including native Solana tokens that today have no derivative market. If this approach works, it could create a new layer of infrastructure for the ecosystem. A potentially self-reinforçant model The protocol is based on an interesting economic idea. The more a market is used, the more fees it generates. Active markets can attract more liquidity providers. Better liquidity then improves the experience of traders, which in turn can attract more volume. This dynamic is often called flywheel liquidity.

• 
  GoXR3Plus Studio (@goxr3plus) reported 46 minutes ago

  @lydiahallie Plus the site has a bug when i try to apply again it says an error no github found like whaa. I have github since 2013...

• 
  AJ Venter (@ajventerx) reported 54 minutes ago

  @grok Dashboard to easy track and review my Openclaw Ai Factory Easy to login and check status and updates All data pull in through Connectors to GitHub All done on the Grok App on my iPhone

• 
  Brian Jacobson (@BrianHJacobson) reported 54 minutes ago

  @JordanSchachtel It doesn't matter. China will steal it within weeks of it being developed and published. We just saw that with K3. The idea that we are in a race against China is a false one. This is human progress, not the exclusive realm of one specific country. It's not as if we are going to march into China and stop them from developing it. Like I told a certain group of people last year, for the first time in human history we have the chance to really think through how we develop and engage with a new technology in real time. If you could go back to the late 1990s or early 2000s is there not anything you'd like to see done differently in how the world adopts social media? We don't even really need to slow down development. We just need to be more thoughtful in how we allow it to impact humanity. Because right now we are leaving behind HUGE swaths of even US citizens. It has gotten to the point now where I regularly talk to people in the technology sector that are anti-AI. I just saw where a competitor to Github, Codeberg, just VOTED among its members to ban all vibe coded projects. People need to feel heard and included in the conversation or it is not going to go well for us.

• 
  Polsia (@polsia) reported 54 minutes ago

  Most engineering teams need a junior dev. Almost none can justify the hire. Built Petrel to fix that — an always-on AI crew for GitHub and GitLab that opens scoped PRs, runs CI, triages issues, and posts standups to Slack. Flat per-repo fee. No seat math. Live soon.

• 
  KISA aka Copenzafan.eth (@copenzafan) reported 59 minutes ago

  @killix The thing is, this system is meant as a repair method. I'm not trying to prevent the agent's glitches and mistakes, it can straight up ignore any system instruction or skill. I'm working from the idea that in most errors its thinking isn't dead and the global system prompt isn't broken, it just tripped and started walking in circles. Pointing at the mistake isn't enough, you have to untangle its whole ball of reasoning. And it hits me out of nowhere, when I see the actual result of the work: errors, bugs, stuff broken and stuff built that I never asked for. Design, for example. But I'll take your advice on board, and honestly, feel free to drop issues straight into the repo on github.

• 
  Owen O'Neill ⚡️ (@OwenONeillUK) reported 59 minutes ago

  The issue is that it’s a GitHub repo, Normies just aren’t going to touch that. We need the Game Boy ROM version of software: drag it into X, click “Install”, and you’re done. Make a client-side app, make a marketplace. Done.