> For the complete documentation index, see [llms.txt](https://docs.flxbl.io/flxbl/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.flxbl.io/flxbl/codev/development/packages.md).

# Packages

**Dev > Modularize > Packages** lists every package directory in your project with its type, the domain it belongs to, and a marker when the package has uncommitted local changes.

<figure><img src="/files/kwCTfe6Y0CdV7G0var4T" alt="The Packages page listing the project&#x27;s package directories with type chips, domain assignments, and per-row actions"><figcaption><p>Packages — the project's package directories with their types and domains.</p></figcaption></figure>

Filter by name, type, or domain; each row offers **Edit Package**, **View Versions**, and **Transfer to Domain**.

## Creating a package

**Create** walks through the package name, its folder, a description, the DevHub to register it with, and options such as org-dependent and no-namespace. Creation runs as a background task — registering the package with the DevHub takes a few minutes, and a notification arrives when it is done. The new package directory is added to the project on your current branch.

## Editing and organising

**Edit Package** opens the package's project configuration in a full-screen editor; saving writes the change back to the project file, where it shows up as a workspace change to commit. **Transfer to Domain** moves the package into a domain — see [Domains](/flxbl/codev/development/domains.md).

## Installing a package version

**Install** deploys a built package version into an org. Pick the package and version, the target org — prefilled with your [target org](/flxbl/codev/development/development.md#the-status-bar) and checked for a live connection — and the DevHub. Use it to bring a freshly fetched org up to a specific version, or to install a hotfix candidate for verification.

## Versions

**View Versions** on a package (or the **Versions** breadcrumb page) lists every version codev has built for it, with its status, stage, and publish date. The list comes from the codev server, so versions appear once a package has been built through [codev's CI/CD](/flxbl/codev/ci-cd/overview.md).

<figure><img src="/files/UCaJIbFcUv3pTzIBEdW6" alt="The package versions page listing versions of a package with status, stage, and date columns"><figcaption><p>Versions — every built version of a package, with status and stage.</p></figcaption></figure>

Click a version to open its artifacts. Select two versions to enable **Compare Selected**, which opens a diff of the two — including a content diff of what changed between them.


---

# 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://docs.flxbl.io/flxbl/codev/development/packages.md?ask=<question>&goal=<endgoal>
```

`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.