> For the complete documentation index, see [llms.txt](https://commandbox.ortusbooks.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://commandbox.ortusbooks.com/6.0.0-1/release-history/3.x-versions.md).

# 3.x Versions

In this section you will find the release notes for the 3.x version of CommandBox. 

* [Version 3.9.0](/6.0.0-1/release-history/3.x-versions/whats-new-in-3.9.0.md) - Nov 2017
* [Version 3.8.0 ](/6.0.0-1/release-history/3.x-versions/whats-new-in-3.8.0.md)- Aug 2017
* [Version 3.7.0](/6.0.0-1/release-history/3.x-versions/whats-new-in-3.7.0.md) - Jul 2017
* [Version 3.6.0](/6.0.0-1/release-history/3.x-versions/whats-new-in-3.6.0.md) - Mar 2017
* [Version 3.5.0](/6.0.0-1/release-history/3.x-versions/whats-new-in-3.5.0.md) - Jan 2017
* [Version 3.4.0](/6.0.0-1/release-history/3.x-versions/whats-new-in-3.4.0.md) - Nov 2016
* [Version 3.3.0](/6.0.0-1/release-history/3.x-versions/whats-new-in-3.3.0.md) - Oct 2016
* [Version 3.2.0](/6.0.0-1/release-history/3.x-versions/whats-new-in-3.2.0.md) - Jul 2016
* [Version 3.1.1](/6.0.0-1/release-history/3.x-versions/whats-new-in-3.1.1.md) - Jul 2016
* [Version 3.0.1](/6.0.0-1/release-history/3.x-versions/whats-new-in-3.0.1.md) - Feb 2016
* [Version 3.0.0](/6.0.0-1/release-history/3.x-versions/whats-new-in-3.0.0.md) - Feb 2016


---

# 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://commandbox.ortusbooks.com/6.0.0-1/release-history/3.x-versions.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.