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

# Docs TODO

1. Better docs on using with 3rd party platform SDKs like AltSpace, VR Chat, Mona etc
2. Better docs on SDK/Toolkit especially with regard to Unity 2020 and URP/HDRP
3. Better docs on importing to Blender etc
4. Improve docs on video generally.
5. 3d model import needs a lot of work explaining the pitfalls - although fixing the importer would also solve this!
6. Make it clear in the docs when a feature is PC only. Especially stuff [here](https://docs.google.com/spreadsheets/d/1QQVGQr8PTWNBYWj1hiE807CBUgbhlD1gcsm25ZZKP7E)
7. Missing docs on new features [here](/differences-between-open-brush-and-tilt-brush.md) and [here](/release-history.md)
8. Investigate limits to model import complexity and document them
9. Document "Simplification" and check for other missing settings docs
10. Add a "Case Studies" page
11. user-guide/monoscopic-mode page - better download links ( use nightly.link )
12. Add docs for spectator camera (should be on the [Labs](/user-guide/check-out-labs-or-experimental-features.md) page. If it's mentioned anywhere else I didn't find it)
13. Document differences between Quest and PC versions
14. Clarify Quest standalone vs Quest + Link
15. Document Mixed Reality capture: <https://creator.oculus.com/mrc/> vs Liv vs Mixcast
16. Document the Labs/camera button (which seems to be mobile only)
17. Settings
18. 2.0 new features (maybe check if we missed anything in earlier release also)
19. Update info on "Sharing" page to be clear about Quest differences. Document how to access sketches on the Quest.


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.openbrush.app/docs-todo.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.