> For the complete documentation index, see [llms.txt](https://help.rechat.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.rechat.com/this-week-in-rechat/week-36-in-rechat.md). # Week 36 in Rechat Fri Sep 11, 2026 ### Agent-only showing details and private remarks on listing pages {% embed url="" %} Agents can now access important Showing Details and Private Remarks directly from Rechat web listing pages when that information is provided by the MLS. This helps agents work from a more complete listing view on desktop while keeping sensitive MLS-only information protected from public visitors and non-agent users. *** ### Dynamic QR codes for more personalized Studio templates {% embed url="" %} Enhance your design workflow with built-in QR code support directly inside the studio! While agents can easily drag and drop standard static QR codes into their print templates, designers can now set up dynamic rules for how QR codes should be generated when a template is used later. Specify dynamic variables—such as directing actions directly to the agent's actual email address—so the proper details automatically populate when an agent applies the template. Expanding beyond existing Figma support, this powerful feature is now natively available inside the studio to streamline template creation. --- # 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.rechat.com/this-week-in-rechat/week-36-in-rechat.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.