> For the complete documentation index, see [llms.txt](https://mind-expression-docs.gitbook.io/home/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://mind-expression-docs.gitbook.io/home/concepts/sandbox.md).
# Sandbox
While building your conversational AI with Subjects, Sandbox allows you to test your AI as if your customers were interacting with it. It uses the same API internally, so all the features that are available for API users will be shared. You can open Sandbox from the Scope details page and Subject details page. To learn more about how to test in Sandbox, see [How-to Guides: Test and debug](/home/how-to-guides/test-and-debug.md).
### Audit Test Sessions
Every interaction in Sandbox will also be logged in Conversation History as well as live sessions so that you can audit your test sessions anytime. In Conversation History, you can trace how AI is reasoning and you can look into the conversation models. To learn more about Conversation History, see [Concepts: Conversation History](/home/concepts/conversation-history.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://mind-expression-docs.gitbook.io/home/concepts/sandbox.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.