> ## Documentation Index
> Fetch the complete documentation index at: https://docs.comet.rpamis.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Installation, distribution, and upgrades

> Preview application targets, confirm platform delivery, and retain versions required by active Runs.

Your local report application has passed validation and your team needs platform entries. Distribute its complete package so the workflow, entry Skill, rules, and pinned dependencies install together.

Prepare local-report/application.json using the [application guide](/en/sdk/applications.md). This page uses Comet CLI; see [comet application](/en/cli/application.md) for all options.

## Preview installation

```bash theme={null}
comet application distribute ./local-report/application.json --project . --platform codex --preview --json
```

Inspect paths, platform capabilities, conflicts, and the confirmation hash in the response. Project scope is the default; explicitly set --scope user for user entries. Address missing execution or Hook capabilities before continuing.

A preview reads the current target and content without writing installation files. A confirmed application plan still needs a separate decision on this installation target.

## Confirm and install

After the user confirms, substitute the returned hash:

```bash theme={null}
comet application distribute ./local-report/application.json --project . --platform codex --confirmation-hash <current-preview-confirmation-hash> --json
```

Changed package content or target configuration invalidates the old hash and requires another preview. Activate platform capabilities as instructed, then start the original application and verify actual output. Written files do not prove real Skill execution.

## Export to another device

```bash theme={null}
comet application export ./local-report/application.json ./exports/local-report --project . --json
```

Export includes the complete package and pinned dependencies. Recipients review modules and dependencies, then preview and confirm installation in their project. Sending only `SKILL.md` omits the definition, module, and acceptance conditions.

## Upgrade an application

Create a new version after business changes and add --upgrade to the same preview flow. Confirmation updates platform entries while retaining old versions required by active Runs.

Identity, version, and content must agree. Do not replace a Skill or module inside an existing version and resume an old Run with different content.

## Remove a platform entry

```bash theme={null}
comet application uninstall local-report --project . --platform codex --json
```

Inspect the uninstall preview and submit its --confirmation-hash. Shared Rules/Hooks, other applications' dependencies, and required versions remain. Specify --platform when removing only one platform entry.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.