> 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/development-status.md).

# Development status

This page is a snapshot of what Patcher already does, not a roadmap.

## Shipping today

### Public browsing

* public module browsing
* public rack browsing
* public patch browsing
* public profile pages

### Personal workspace

* module collection tracking
* rack creation and editing
* patch creation and editing
* global search across the user area
* manuals gathered from your saved modules
* contributor stats and workspace stats

### Rack workflow

* visual layout planning
* duplicate / delete / blank-panel actions
* multi-panel support where available
* power analysis and balance analysis

### Patch workflow

* module-based patch capture
* connection documentation
* notes and naming for recall
* instance-aware handling for repeated modules
* auto-save for patch state and edits

### Project shape

* open-source codebase
* public data browsing without an account
* mobile-friendly product direction

## Still actively improving

Patcher is still evolving. Areas that continue to move include:

* module data coverage and detail quality
* docs and onboarding
* discovery and browsing surfaces
* contributor tooling
* overall polish across core workflows

## Best way to track changes

For detailed release history, use:

* [Changelog](/project/changelog.md)
* [Main GitHub repository](https://github.com/Polyterative/Patcher)
* [Discord community](https://discord.gg/N6Z32xJR)


---

# 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/project/development-status.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.