> 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/overview/get-started/help-and-feedback.md). # Help and feedback How to reach the Intangible team when something is wrong, and where the same flow lives inside a project. The fastest way to reach a human at Intangible. Two surfaces – one on the homepage, one inside any project – that route to the same team. ![Help menu open from the top-right help icon, showing First Steps, Keyboard Shortcuts, 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-eba883d3c14595958fd8f7c4b75ae06bf22893fa%2Fhelp-menu-01.png?alt=media) ## How to reach us The help icon (question mark) lives in the top-right toolbar of every Intangible page – homepage, project editor, settings. Click it to open the help dropdown. ### What's in the menu | Item | What it does | | ---------------------- | ----------------------------------------------------------------------------------------------------------------------- | | **First Steps** | Relaunches the guided onboarding tour. Useful when a teammate joins and you want to walk them through the basics again. | | **Keyboard Shortcuts** | Opens the in-app shortcuts panel. See [Keyboard shortcuts](/overview/reference/keyboard-shortcuts.md). | | **Updates** | Opens `studio.intangible.ai/updates`, the public changelog. | | **Help Docs** | This documentation site. | | **Report an Issue** | Send a bug report directly to the support queue. Auto-attaches project context. | The help menu is the canonical place to start. From inside a project the same menu is available, with the advantage that **Report an Issue** auto-attaches the project ID and last-render context. Feature requests and general feedback go through the same Report an Issue panel, tagged accordingly, rather than through their own menu entries. For peer conversation, the Intangible Discord is linked from [intangible.ai](https://www.intangible.ai). ### 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) | 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) | What went into each numbered release | By release | 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. ## Report an issue Report an issue (from the help menu, or the bug icon directly in the top-right toolbar) opens a structured report panel: ![Report an Issue panel docked on the right side of the editor with a "Hey, found a bug?" greeting, a "What went wrong?" textarea, and two action buttons: Mark the bug and Record screen](https://1179478100-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FSWrjIqlgVAblx6vHGJiM%2Fuploads%2Fgit-blob-37e06462fdc2c0b61ffacbd08355e42333dc161e%2Freport-an-issue-panel-01.png?alt=media) Two actions support what you describe in the text field: * **Mark the bug** lets you click directly on the part of the UI that's broken so the report carries an annotated screenshot of the exact element. * **Record screen** captures a short video of the issue. Useful when the problem only shows up in a sequence of actions. The bug icon in the top-right toolbar is a shortcut to the same panel – you don't have to open the help menu first. ## Messages The chat-bubble icon next to the help icon opens **Messages**, a real-time support thread with the Intangible team: ![Messages panel open from the chat-bubble icon, showing recent message threads with team members, plus a "Send us a message" action and Home / Messages / Help / News tabs at the bottom](https://1179478100-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FSWrjIqlgVAblx6vHGJiM%2Fuploads%2Fgit-blob-7b8161062398081951fd127ec15ddbf9bca306e3%2Fmessages-panel-01.png?alt=media) Use Messages for general support conversation, follow-ups on a previous thread, or quick clarification questions. Use **Report an issue** for structured bug reports where the team needs to reproduce. ## What gets a fast response Specific reproduction steps and recent context. The team can chase a vague "the visualizer didn't render right" report, but it takes a day; *"In project Lambo Commercial, scene Manhattan Street, shot 3, Nano Banana Pro at 2K – the cop car keeps showing up despite the negative-prompt edit"* takes ten minutes. What helps: * The project name and a link if the project is shared * The exact scene and shot * The model and resolution * A screenshot of the unexpected behavior * What you expected to see instead What doesn't help: * "It's broken" * "The AI is wrong" * A description of the entire week's work ## Reporting a bug Same form. Pick the **Bug** tag in the subject. The form auto-uploads a recent renders log so we can correlate against logs on our side. ## Suggesting a feature Same form again. Pick **Feature request**. We read every one. We don't ship every one. ## Related * [First Steps and onboarding](/overview/get-started/first-steps-and-onboarding.md) * [FAQ](/overview/faq.md) * [Common questions](/overview/faq/common-questions.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, and the optional `goal` query parameter: ``` GET https://help.intangible.ai/overview/get-started/help-and-feedback.md?ask=&goal= ``` `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.