> For the complete documentation index, see [llms.txt](https://docs.patcher.xyz/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.patcher.xyz/core-workflows/patches.md).

# Patches

Patches are the memory layer of Patcher.

Use them when you need more than a loose note or a photo on your phone. A good patch entry lets you reopen a session later and still understand what mattered.

![Patches browser on iPad Pro](/files/xnhmlzGTK3lEEoeXnE22)

## What a patch can hold

A patch can bring together:

* the modules involved
* cable routing
* notes and descriptive text
* naming that makes recall easier later
* sharing choices for public visibility

## Create a patch

1. Go to **User Area**.
2. Open the **Patches** section.
3. Click **Create patch**.
4. Name it clearly.
5. Add the modules you need.
6. Start documenting routing and notes.

## Why collection-first matters here

Patches work best when your collection is already accurate.

That gives you a reliable source list for module assignment and keeps your patch notes grounded in the hardware you actually use.

Read more: [Collection](/core-workflows/collection.md)

## Add modules to a patch

Before you can document routing well, the relevant modules need to be part of the patch.

The practical flow is:

1. keep your collection up to date
2. create the patch
3. add the modules involved
4. document the signal path

## Add connections

Once the patch contains the right modules, add the routing step by step.

This is where Patcher becomes especially useful for recall:

* inputs and outputs can be documented intentionally
* repeated modules remain distinct
* the patch stays readable later instead of turning into guesswork

If a module is missing useful I/O data, improve the module data first when possible. That pays off elsewhere too.

## Repeated modules and instance clarity

When the same hardware appears more than once in a patch, Patcher keeps those instances distinct.

Use that deliberately. Give repeated modules names or notes that make the role obvious later, especially when one module is doing more than one job in the same session.

## Edit without fear

Patches are meant to evolve while you work.

Patcher is built around fast iteration, including auto-save for patch state and edits, so it stays useful during an active session instead of only after it is over.

## Naming and notes

The more patches you save, the more naming matters.

Good patch names and notes should answer:

* what the patch does
* what makes it different
* what you would need to remember under pressure

## Public and private use

Not every patch needs to be shared.

New patches currently start public, so check the sharing toggle if you want to keep a patch private while it is still a working draft.

For public discovery, the patch itself needs to be public and your profile also needs to be public.

## Best practices

* save patches while the session is still fresh
* keep names specific
* note unusual routing or settings
* treat repeated modules as distinct voices, not interchangeable placeholders
* share only the patches you actually want attached to your public profile

## Related pages

* [Collection](/core-workflows/collection.md)
* [User Area](/core-workflows/user-area.md)
* [Public Profiles](/core-workflows/public-profiles.md)


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.patcher.xyz/core-workflows/patches.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.