> For the complete documentation index, see [llms.txt](https://help.dscout.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.dscout.com/product-updates/2026/june-2026.md).
# June 2026
What's been released, changed, and improved across the Dscout platform
{% updates format="full" %}
{% update date="2026-06-26" tags="feature,fix,improvement" %}
## Skip logic and piping logic added to auto-recruit screeners
Auto-recruit screeners can now use skip logic and piping logic, allowing you to build a more customized participant experience. Skip logic lets you pass participants over parts of a screener that aren't relevant to them. And piping logic lets you recall a participant's previous answers within later questions.
For more information, see [Skip logic](/study-basics/design-a-study/skip-logic-in-screeners.md) and [Piping logic](/study-basics/design-a-study/piping-recall-logic.md).
{% endupdate %}
{% update date="2026-06-04" tags="improvement" %}
## A smarter Explore your data
Explore your data has a new workspace layout for a more consistent Dscout AI experience, and it now remembers your conversations. Pick up a chat where you left off instead of starting over each time.
Additionally, citations in Explore your data now take you straight to the moment they came from, instead of the top of the entry. Click a source and land on the exact response, or the exact point in a recording, that the answer is based on.
For more information, see [Explore your data](/dscout-ai/dscout-ai-studio/explore-your-data.md).
{% endupdate %}
{% endupdates %}
---
# 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.dscout.com/product-updates/2026/june-2026.md?ask=&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.
