> 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/5.4.0/release-history/4.x-versions/whats-new-in-4.7.0.md).

# What's New in 4.7.0

Here's the full list of what we've packed into the 4.7.0 release.  Click any ticket link for more details.

### Bug

* \[[COMMANDBOX-962](https://ortussolutions.atlassian.net/browse/COMMANDBOX-962)] - CommandBox not recognizing implicit folder endpoint
* \[[COMMANDBOX-967](https://ortussolutions.atlassian.net/browse/COMMANDBOX-967)] - Update semver for fix in prerelease comparison
* \[[COMMANDBOX-970](https://ortussolutions.atlassian.net/browse/COMMANDBOX-970)] - Tokenizer breaks "run" command with odd syntax
* \[[COMMANDBOX-972](https://ortussolutions.atlassian.net/browse/COMMANDBOX-972)] - init-wizard command is incorrectly aliasing as init
* \[[COMMANDBOX-978](https://ortussolutions.atlassian.net/browse/COMMANDBOX-978)] - File watcher that modifies the file system triggers the watcher again
* \[[COMMANDBOX-985](https://ortussolutions.atlassian.net/browse/COMMANDBOX-985)] - bump command doesn't work on a submodule
* \[[COMMANDBOX-986](https://ortussolutions.atlassian.net/browse/COMMANDBOX-986)] - Text on standard input causes banner and prompt to be blank
* \[[COMMANDBOX-988](https://ortussolutions.atlassian.net/browse/COMMANDBOX-988)] - Inconsistent behavior of "run" command.
* \[[COMMANDBOX-989](https://ortussolutions.atlassian.net/browse/COMMANDBOX-989)] - Tab completion incorrect for some partial command names
* \[[COMMANDBOX-990](https://ortussolutions.atlassian.net/browse/COMMANDBOX-990)] - Interactive jobs are not thread safe

### Improvement

* \[[COMMANDBOX-956](https://ortussolutions.atlassian.net/browse/COMMANDBOX-956)] - Leading zeros in semver prevent them from being matched
* \[[COMMANDBOX-957](https://ortussolutions.atlassian.net/browse/COMMANDBOX-957)] - Allow --verbose flag on uninstall command
* \[[COMMANDBOX-958](https://ortussolutions.atlassian.net/browse/COMMANDBOX-958)] - Add --roundup flag to indents command
* \[[COMMANDBOX-959](https://ortussolutions.atlassian.net/browse/COMMANDBOX-959)] - JSON Schema for box.json
* \[[COMMANDBOX-968](https://ortussolutions.atlassian.net/browse/COMMANDBOX-968)] - Update JGit to 5.3.0.201903130848-r
* \[[COMMANDBOX-969](https://ortussolutions.atlassian.net/browse/COMMANDBOX-969)] - Update Jline to 3.10.0
* \[[COMMANDBOX-971](https://ortussolutions.atlassian.net/browse/COMMANDBOX-971)] - Remove Riaforge endpoint Rince riaforge is dead
* \[[COMMANDBOX-973](https://ortussolutions.atlassian.net/browse/COMMANDBOX-973)] - Modify default box.json from "init" command
* \[[COMMANDBOX-974](https://ortussolutions.atlassian.net/browse/COMMANDBOX-974)] - Add box: namespace for compat with Coldbox injection DSL
* \[[COMMANDBOX-976](https://ortussolutions.atlassian.net/browse/COMMANDBOX-976)] - Improve debugging and error messages for custom ForgeBox endpoints
* \[[COMMANDBOX-979](https://ortussolutions.atlassian.net/browse/COMMANDBOX-979)] - If the test runner produces a 500 exception during watcher no output is shown
* \[[COMMANDBOX-982](https://ortussolutions.atlassian.net/browse/COMMANDBOX-982)] - support for Environment variables in "Key" names
* \[[COMMANDBOX-983](https://ortussolutions.atlassian.net/browse/COMMANDBOX-983)] - Make env vars in CommandBox visible to native OS binaries
* \[[COMMANDBOX-984](https://ortussolutions.atlassian.net/browse/COMMANDBOX-984)] - Launching VSCode from ConEMU screws up the integrated terminal
* \[[COMMANDBOX-987](https://ortussolutions.atlassian.net/browse/COMMANDBOX-987)] - Keep relative installPaths in box.json


---

# 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/5.4.0/release-history/4.x-versions/whats-new-in-4.7.0.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.
