> For the complete documentation index, see [llms.txt](https://help.intangible.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.intangible.ai/get-started/help-and-feedback.md).

# Report a bug or get help

Found a bug? Report it from inside Studio in a few clicks: Help (?) > Report an Issue, describe it, click Send report and share the Studio tab for a screenshot.

Found a bug? Tell us from right where you are. Reporting one takes a few clicks, you never leave your project, and a screenshot of the Studio tab can go with it. Every report goes straight to the Intangible support team. Reports are how fixes start, so send the small ones too.

## Report a bug

1. **Click the help icon (?)** in the top-right toolbar. It is on every Studio page, in a project and on Home. Pick **Report an Issue** at the bottom of the menu. In a project window narrower than 800 pixels, help folds into the **More** menu (three dots): open **More**, then **Help**.

   ![The help menu, opened from the ? icon in the top-right toolbar: First Steps, Keyboard Shortcuts and Updates, then Help Docs and Report an Issue below a divider](https://1179478100-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FSWrjIqlgVAblx6vHGJiM%2Fuploads%2Fgit-blob-5071a31dad7be2c39b2763e2384e98741ad2e8bb%2Fhelp-menu-01.png?alt=media)
2. **Say what went wrong.** The **Report an issue** form opens with one box, **Issue description**. One or two sentences is enough: what you did, what happened, and which scene and shot. It takes up to 2,000 characters.

   ![The Report an issue form: "Tell us what happened and we'll look into it.", the note that your browser will ask to share a tab for a screenshot, an empty Describe the issue box, and Cancel beside a greyed-out Send report](https://1179478100-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FSWrjIqlgVAblx6vHGJiM%2Fuploads%2Fgit-blob-bd60c01006f7429143aad5a4a4e5823bc117241f%2Freport-an-issue-form-01.png?alt=media)
3. **Click Send report.** It turns on once the box has text.
4. **Share the Studio tab.** Your browser asks which tab to share for a screenshot. Choose the Studio tab. Cancel instead and the report still goes, as text only. Close anything sensitive on that tab before you share it.

A toast confirms it: "Your report was sent to our support team." Without a screenshot it reads "Your report was sent without a screenshot."

Each report also carries the page URL and, when one is available, a link to a replay of your session, so the team can see the steps that led there. In a browser that can't capture a tab, the form says so and sends text only.

{% hint style="success" %}
Not sure it's a bug? Report it anyway. A report that turns out to be expected behavior still tells the team where Studio was confusing.
{% endhint %}

### What makes a report quick to fix

The team has to see what you saw. These help the most:

* The scene and shot, and the mode you were in
* What you did just before it happened
* What you expected instead
* For a render: the model and resolution
* A screenshot of the Studio tab with the problem on screen

"The render is wrong" is hard to act on. "Shot 3 in Manhattan city street, Nano Banana Pro at 2K: the police car comes back after I removed it from the prompt" points straight at the problem.

## Request a feature or send feedback

Studio has one form, **Report an issue**, and it has no separate feature-request or feedback option and no message thread inside Studio. For peer conversation, the Intangible Discord is linked from [intangible.ai](https://www.intangible.ai).

## The help menu

The help icon (?) opens the same menu everywhere in Studio.

| Item                   | What it does                                                                                                                                                                                                                                                          |
| ---------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **First Steps**        | Opens the **First Steps** window: a carousel of six tutorial videos: an overview, one per mode, and importing your own 3D models. It does not start the Canvas tour; see [Take the tour](https://help.intangible.ai/get-started/sign-up-and-set-up.md#take-the-tour). |
| **Keyboard Shortcuts** | Opens the in-app shortcuts panel. See [Keyboard shortcuts](https://help.intangible.ai/learn-more/reference/keyboard-shortcuts.md).                                                                                                                                    |
| **Updates**            | Opens `studio.intangible.ai/updates`, the public changelog.                                                                                                                                                                                                           |
| **Help Docs**          | This documentation site.                                                                                                                                                                                                                                              |
| **Report an Issue**    | Opens the **Report an issue** form.                                                                                                                                                                                                                                   |

### Updates and release notes

A setting moved after an update, or support told you a fix landed and you want to see it written down. There are two public pages for that, and they answer different questions.

| Page                                                                                                                                                                                       | What it lists                                                                        | How it is organised                                              |
| ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | ------------------------------------------------------------------------------------ | ---------------------------------------------------------------- |
| [`studio.intangible.ai/updates`](https://studio.intangible.ai/updates?utm_source=help.intangible.ai\&utm_medium=docs\&utm_campaign=inline-link\&utm_content=help-and-feedback)             | Feature announcements, one per thing that shipped                                    | By feature, newest first. **Updates** in the help menu opens it. |
| [`studio.intangible.ai/release-notes`](https://studio.intangible.ai/release-notes?utm_source=help.intangible.ai\&utm_medium=docs\&utm_campaign=inline-link\&utm_content=help-and-feedback) | What went into each numbered release                                                 | By release                                                       |
| [What's new](https://help.intangible.ai/get-started/whats-new.md)                                                                                                                          | The changes you can see in each release, each linked to the help page that covers it | By release, newest first                                         |

Reach for Updates when you want to know what a feature is. Reach for release notes when you want to know whether a given release contains it.

**Both pages deep-link.** Every entry on Updates has its own anchor, named after the feature, so `studio.intangible.ai/updates#drag-and-drop-cameras` opens the page at that one. Release notes anchor by release: `studio.intangible.ai/release-notes#release-2-0-70`. Read the anchor off the entry rather than guessing it from the title.

Neither page requires signing in. Paste either link into a client thread or a Slack channel and it opens for whoever you send it to, account or not.

## Related

* [Common questions](https://help.intangible.ai/learn-more/faq/common-questions.md)
* [Troubleshooting Intangible agents](https://help.intangible.ai/learn-more/faq/troubleshooting-the-agent.md)
* [Troubleshooting rendering](https://help.intangible.ai/learn-more/faq/troubleshooting-rendering.md)
* [Known limitations](https://help.intangible.ai/learn-more/faq/known-limitations.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 by asking a question.

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

```
GET https://help.intangible.ai/get-started/help-and-feedback.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.
