terms.

Last updated: 6 November 2026

Who we are

Patch is run by New Save Labs, Inc., 131 Continental Dr, Suite 305, Newark, DE 19713. "Patch", "we" and "us" mean that company. "You" means you and, if you use Patch for a team, the team too.

These terms cover patch.gg, Patch Desktop, the pch command line tool, Patch's API and MCP server, Patch's git host, and games and files served from patchusercontent.com. Our privacy page says what we keep about you.

Making an account, by signing in for the first time, means you agree to these terms. If you use Patch without an account, they still apply to what you do here.

Who can use Patch

You need to be 18 or older to have a Patch account.

If we learn that an account belongs to someone under 18, we close it.

You can browse patch.gg without an account. Games, browser games included, play in Patch Desktop. You need an account to publish, to get a mod, to keep a Library and to have your play counted.

Your account

You sign in with Google, Discord or GitHub, or with a link and code sent to your email. Patch has no passwords. Your first sign-in makes your account.

You pick a username. It's public, and it's the name people see you by on Patch. It can't be a name Patch has reserved.

What happens under your account is your responsibility. That includes your API keys, and the agents and tools you give them to. A key acts as you, and so does an agent using it. In a Patch Desktop chat, your agent gets a key like that while it works. You can revoke a key at any time. Signing out of Patch Desktop stops its chats and revokes the keys it made.

Patch can ban an account that breaks these terms, or that puts Patch or the people on it at risk. A ban signs you out everywhere, stops you signing in and refuses your keys. We'll tell you why, unless the law or someone's safety stops us.

You can take your work with you at any time by cloning your repos with git.

To delete your account and what we keep about you, write to founders@patch.gg. There's no button for it in Patch yet.

What Patch is

Patch is a place to make, publish, find and play browser games, mods and blocks. A block is any piece of a game: a mechanic, a character, an asset or a tool. Every game and block lives in its own git repo. A release is a version people can get, with the commit it came from when it names one.

Patch doesn't build your work. You or your agent build it, on your PC or in your own CI, and upload what comes out.

Patch hosts, you publish

People publish their own work on Patch, and each person answers for what they publish. Patch hosts it.

We review what you release for things that could harm players or their PCs. The review doesn't decide who owns what's in a release. If it finds something that plainly isn't yours to share, such as a game's own files, we won't release it.

If you think something on Patch breaks your rights, tell us and we'll take it down quickly. See "Copyright and takedowns".

Your agent

Patch Desktop runs your own coding agent on your PC, on your own account with the company that makes it. That company's terms apply to your agent and to what it writes, and any bill for it is yours. Setting an agent up runs its maker's own installer, and Patch Desktop keeps your agents up to date, checking once a day.

By default, a chat in Patch Desktop starts your agent in Auto, where it works on its own and a safety check can stop a step, or, for agents without Auto, in a mode where the agent's own rules decide what it asks you first. If you pick full access, Patch tells the agent it has your permission for every command and edit the work needs, and that nothing will ask you first, except where Patch's instructions say to ask. Some agents offer narrower modes for a chat, such as asking first. In Auto or with full access, the agent can change files, run programs, install a mod and start a game on your PC. It asks before publishing, unless you told it not to ask.

Your agent works for you, and as far as the law allows, Patch isn't responsible for what it does on your PC. Each chat shows what your agent did, and you can undo the changes it committed to a project. Changes it makes anywhere else on your PC may not be undoable, so back up what matters to you.

Patch keeps a copy of your chats, to fix problems and improve Patch. You let Patch and its service providers process a copy for this. Our privacy page says what a copy holds and how long we keep it.

Your work

You keep whatever rights you have in what you make, including what your agent makes for you. Patch claims none of them. The law may give nobody rights in the parts an agent wrote by itself, so we can't promise that anyone owns those.

You can publish your own work anywhere else too, at the same time. Patch asks for no exclusivity.

When you publish, you promise that you made the work or have the rights to share everything in it, and that it follows these terms.

What you let Patch do. You give Patch a worldwide, non-exclusive, royalty-free licence to host, store, copy, run, review, show and promote your work, to make previews and versions for other devices from it, and to let people use it as these terms allow. Patch may show your work anywhere it shows things, on Patch and in its own posts, films and ads, without naming you every time. Your name always shows on your work's own pages. Private work is never shown or promoted. Where the law gives you a right to be named, you agree not to use it against Patch for this, as far as the law allows.

This licence ends when you take your work down. Copies other people already made under these terms, such as remixes, stay. So do backups, for a while.

Other people's work inside yours, such as libraries and assets, keeps its own licence. Follow it, and keep its notices and credits. Assets from Patch's asset library come with their licence and a credit line.

Shared notes. When you or your agent suggest a shared note, you let Patch use, edit and publish it.

Open, Closed source and Private

Each repo has one of three settings.

A repo you make on purpose is Open. Your first push doesn't make it public straight away: Patch keeps it Closed source until a scan of its history finds no secrets, then opens it by itself. If the scan finds secrets, it stays closed until they're gone. A remix of an Open repo starts Open, since it copies what's already public. A repo made by a chat in Patch Desktop starts Private, and goes further only when you choose.

Going Open publishes the repo's whole history. There's no fresh start. Before a repo hosted on Patch goes Open, Patch scans its history for secrets and shows you what will become public.

Closing an Open repo doesn't take back what's already out. Remixes keep their copies, and clones and installed copies stay where they are.

Going Private hides a project on Patch. A browser game that was already published still plays from its link, and its page says so.

None of these settings stops Patch's review reading what you release, or Patch's team and AI agents reading kept chats. See "How Patch reviews what you release".

Building on other people's work

Each repo lists its licence on its page and in its LICENSE file. New repos start under the Patch licence, and this section is that licence.

On Patch. Anyone can play, read and remix work under the Patch licence on Patch. A remix is a copy in your own account that you can change. You own what you add, and the work you started from stays its maker's.

Off Patch. Nobody may take someone else's work under the Patch licence, or a remix of it, off Patch without its maker's OK. That includes putting it on another site or store, and copying it to train AI models elsewhere. A remix starts with the licence of the work it's built on, and stays under the Patch licence until that work is opened up.

Opening it up. A maker can give that OK to everyone at once by picking an open licence for a repo, such as MIT or CC BY 4.0. Then anyone can take the work anywhere, on that licence's terms, which usually means keeping the maker's name on it. Changing the licence later doesn't take it back from copies already made.

Your own work is always yours to take anywhere. These rules only limit what other people do with it.

Older repos. A repo from before the Patch licence keeps the licence it lists, until its maker changes it.

Credit. A remix shows what it was made from and links to it.

Change requests. When you suggest a change to someone's repo, you license your change under that repo's licence, so its owner can merge it.

Training

Patch may train its own models on Open work, and the licence you give Patch covers that. It's on by default, and each Open repo has a switch for it, on the repo's page.

Turning it off covers every training run after that. A model that's already trained can't unlearn what it saw.

Patch never trains on Closed source or Private work, or on your chats. Patch never gives or sells anyone's work to others for training. Work taken down for breaking someone's rights is left out.

Patch doesn't train any models today.

How Patch reviews what you release

Before a release reaches anyone, Patch checks it for malware and for code that does something harmful or that the release doesn't disclose. Releases by Patch's staff, and the asset library's own conversions, skip this.

• File checks. Patch checks your files against the rules below.
• A test on your PC. A browser game, or a mod Patch can install, is tested on your PC by Patch Desktop, and your own agent reviews the recording. This shows that it works. It can't stop someone set on cheating, so the next step does the checks that can't be faked.
• Patch's review. Patch scans every file for known malware. Then an AI model that service providers run for us reads the code. We send the model the release's files and, if the release names a commit, the source at that commit and what changed since your last release.

This happens whatever your repo's setting, including Closed source and Private. Those settings stop other people on Patch reading your source. They don't stop our review and its providers processing it.

The same model reads a change request for the repo's owner, as advice.

What you allow. You let Patch and its service providers copy and process your work as far as this review needs. We ask them to use only services that say they don't keep it after answering and don't train on it. A provider may still keep material its safety systems flag, or where the law requires, and one may sort requests into topics, anonymously. You let Patch give them the rights they need for all of this.

Who sees the result. The review's findings can quote your code. Your team and Patch staff can read them. If the review flags a release, a person at Patch looks at it. A person also looks at any mod Patch can't test on a PC.

The model doesn't reject a release by itself. It adds warnings, which send the release to a person. A release with no warnings goes live with no person looking at it. No review catches everything, and a release that passed isn't a promise that it's safe.

What isn't allowed

Patch refuses or holds a release for these. So can a person at Patch.

• Malware, or code that does something harmful or that the release doesn't disclose: stealing credentials, tokens or saves from other apps, downloading and running code, autostart or persistence, reaching outside the game's and the mod's own folders without reason, disabling security software, mining, keylogging or screen capture, sending data to hosts the release doesn't need, or anything a player wouldn't expect from what the release says it is.
• Text in your files that tries to give instructions to the reviewer.
• Sending players' data elsewhere, phishing, collecting credentials or misleading players.
• Secrets: keys, tokens and private keys, in a release.
• In a browser game: a native program, loading from or sending to another host, or more than 500 MB.
• Files that don't match what the release says they are.
• Code Patch can't read where it matters, such as packed or obfuscated code. This holds a release for a person. It doesn't reject it.

A secret in a push to an open repo isn't refused: it closes the repo until it's taken out.

You also can't publish:

• A game's own files, or its code, decompiled or not. Publish your own work, and let players bring their own copy of the game.
• Cracks, key generators, or anything that gets around copy protection.
• Cheats for online play, or anything that gets around anti-cheat.
• Anything else that breaks someone's copyright, trademark or other rights.

And nothing on Patch may be illegal, sexualise anyone under 18, or harass, threaten or impersonate someone.

Don't scrape, mirror or collect what's on Patch in bulk to publish it elsewhere, sell it, give it to others or train AI models, whatever its licence. This is about collecting from Patch: an open licence still lets you take the works you choose, and use your copies as it allows. It doesn't cover your own work, search engines, or an agent reading what it needs for a project. To ask for an exception, write to founders@patch.gg.

Don't try to get around Patch's rate limits and storage limits. They can change. Don't attack Patch or the people on it, or try to get into accounts or work that aren't yours.

Games Patch doesn't own

Many mods and mashups are built on games made by other companies. Patch doesn't own those games, and isn't affiliated with or endorsed by their makers unless it says so.

You can make and publish mods and mashups of any game, as long as:

• They're free. Nobody charges for them, and Patch makes no money from them, unless the game's owner agrees.
• They never include the game's own files or code. Players need their own copy of the game.
• Online play goes through the mod's own servers, never through a game's official online service where its owner or anti-cheat doesn't allow mods.
• They come down quickly when the game's owner objects. See "Copyright and takedowns".

This is what Patch allows. It isn't permission from the game's owner, which Patch can't give. That's between you and them.

Patch doesn't sell you the game. Patch Desktop finds the games on your PC and installs a mod into its game, keeping a backup of any game file the mod replaces. Between plays the mod is switched off, and you can remove it.

A mod can run its own code on your PC. Patch reviews it first, but review isn't a guarantee. Run mods you're willing to trust.

A game's maker has its own rules about mods, and can act against your account with them if a mod breaks those rules. For some games, Patch starts the game with its anti-cheat off for that session so that mods can load. Don't take a modded game into official online play where its owner or anti-cheat doesn't allow mods.

Copyright and takedowns

Patch follows the US Digital Millennium Copyright Act (DMCA), and acts on notices about illegal content from other places too.

Reporting something. Send a notice to our copyright agent: Copyright Agent, New Save Labs, Inc., 131 Continental Dr, Suite 305, Newark, DE 19713, founders@patch.gg. A notice needs:

1. your physical or electronic signature;
2. the work you say has been copied;
3. what on Patch you say copies it, with its full address;
4. your name, postal address, phone and email;
5. a statement that you believe in good faith the use isn't allowed by the owner, its agent or the law;
6. a statement that the notice is accurate and, under penalty of perjury, that you own the right or may act for its owner.

What happens next. We take the work down quickly and tell its maker why, with a copy of the notice. Taking a work down doesn't take down its remixes, unless the notice names each one too.

If you think we got it wrong, send a counter-notice to the same agent. It needs:

1. your physical or electronic signature;
2. what was taken down, and where it was;
3. a statement, under penalty of perjury, that you believe in good faith it was taken down by mistake or because it was misidentified;
4. your name, postal address and phone, a statement that you accept the jurisdiction of the federal court for your address (or, outside the US, any district where Patch can be found), and that you'll accept service from the person who sent the notice.

We pass it to the person who sent the notice. We put the work back 10 to 14 business days after we get your counter-notice, unless they tell us first that they've gone to court.

Repeat infringers. We close the accounts of people who keep publishing other people's work after valid notices.

False claims. Knowingly making a false claim in a notice or counter-notice can make you liable for damages.

Trademarks and other rights, such as a game's name or logo: write to the same address, and we follow the same steps.

Other problems, such as a harmful game, harassment or a security issue: write to founders@patch.gg.

If your work was taken down and you think that's wrong for any other reason, write to the same address, and a person will look at it.

What staff can do. Patch staff can unlist a project, so it leaves browse and search and only its link works. They can take a project down, so only its owners see it, nobody else can download it and a browser game stops playing. They can take down one release, so nobody but its owners can download it and a browser game falls back to the release before. They can remove a picture, and remove assets from the asset library. Each change staff make in Patch's admin is logged.

Money

Nothing on Patch costs money today, and Patch pays nobody. Your agent's maker and the stores that sell you games charge you separately.

Later, makers will earn when their work is played or built on. These terms will change before that starts. Nobody will earn from a mod or mashup of another company's game unless that company agrees.

Updates and changes

Patch Desktop updates itself. It looks for a new version soon after it starts, every hour and after your PC wakes, downloads it in the background and installs it when you quit, or when you restart it from Settings › About.

Installed mods follow the latest release, unless you keep the version you have.

A live release never changes.

We can change or stop any part of Patch. If we stop Patch, we'll try to give you time to take your work with you. We can change these terms too: we'll update the date above and tell you before a big change applies, and if you keep using Patch after that, the new terms apply.

If something goes wrong

Patch comes as it is, with no promise that it will work, stay up or suit what you want it for. Games, mods and blocks on Patch are made by the people who publish them, not by us.

As far as the law allows, we aren't liable for indirect or consequential losses, lost data or lost profits, for what other people publish, or for what your agent or a mod does to your PC, your files or your accounts with other companies. Our total liability to you is limited to the greater of what you paid Patch in the last 12 months and US$100.

If someone makes a claim against us because of what you published or did on Patch, you'll cover our reasonable losses and costs, as far as the law allows.

Delaware law governs these terms, and any dispute goes to the courts in Delaware. If you're a consumer somewhere that gives you rights these terms can't take away, such as the EU or the UK, you keep them, including going to your local courts.

Ending this

You can stop using Patch at any time, and take your work with you. Patch can close an account that breaks these terms. When an account ends, remixes other people already made stay, and "If something goes wrong" still applies.

Contact

Write to founders@patch.gg.