> 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.7.0/package-management/private-packages.md).

# Private Packages

ForgeBox allows you to publish packages that only you can see and install. You'll be able to view your private package from the CLI, in the ForgeBox.io search, and in your ForgeBox.io profile, but these packages will now show up for any other users.

## Publishing private packages to ForgeBox

To create a private package, set the `private` property to `true` in your `box.json` prior to publishing.

```
package init
package set private=true
package set slug=my-slug@forgeBoxUser
etc...
publish
```

## Installing private packages from ForgeBox

Replace `forgeBoxUser` with your actual ForgeBox username. When you install the package, you'll need to use the full slug like so:

```
install my-slug@forgeBoxUser
```

You can install specific versions or version ranges as you would expect:

```
install my-slug@forgeBoxUser@1.0.0
install my-slug@forgeBoxUser@be
```

> Private packages will be a paid feature for ForgeBox Pro subscribers, though the feature is currently available to all users for free.


---

# 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.7.0/package-management/private-packages.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.