> 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/project/the-project.md).

# FAQ

## What is Patcher?

Patcher is a digital twin workspace for Eurorack musicians.

It combines a public module database with workspace tools for collection tracking, rack planning, patch capture, manual access, and selective public sharing.

## Do I need an account to use it?

No. You can browse public modules, racks, patches, and documentation without signing in.

You only need an account when you want to save your own collection, racks, patches, or public profile.

## Is Patcher only for patches?

No.

Patcher is useful across the whole modular workflow:

* discovering modules
* tracking what you own
* planning rack layouts
* documenting patches
* sharing selected work publicly

## Why should I add modules to my collection first?

Because the collection powers the rest of the workspace.

Once your modules are saved there, they become the source for rack planning, patch capture, and manual shortcuts.

## Can I use it privately?

Yes, but review the sharing controls early.

Public sharing is optional, but new racks and new patches currently start public until you change their sharing setting.

## What becomes public?

Public browsing only shows racks and patches that are marked public and belong to a public profile.

If your profile is private, your public profile page is not available and your public racks or patches are not discoverable through the public browsing surfaces.

## What is a public profile?

A public profile is the shareable page tied to your username.

It can show the racks and patches you have chosen to expose, along with profile stats and contributor stats.

## Does Patcher support repeated modules in patches?

Yes. Patcher is instance-aware, which matters when the same hardware appears more than once in a patch.

That keeps documentation clearer and more reliable.

## Can I add missing modules?

Yes. If something is missing from the catalogue, use **Submit New Module**.

That helps both the project and your own workflow.

## Can I upload or improve panel images?

Yes, where the relevant contribution surface is available for the module. Improving panel coverage makes rack planning better for everyone.

## Can I import data from ModularGrid?

Not directly.

If you need something that is missing, the practical path today is to add or improve the relevant data in Patcher.

## Where should I ask for help?

Start here:

* [Contact us / Help / Community](/project/contact-us-help-community.md)
* [Discord](https://discord.gg/N6Z32xJR)
* [GitHub issues](https://github.com/Polyterative/Patcher/issues)

## Where should I suggest features?

Discord is usually the fastest place for product discussion. GitHub issues are also useful for concrete, trackable technical proposals.


---

# 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, and the optional `goal` query parameter:

```
GET https://docs.patcher.xyz/project/the-project.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.
