# Manage installed applications



Since Pear v3, applications are installed with [`pear install`](/pear/reference/pear/cli#pear-install) directly into your operating system's application folder, and each app keeps its peer-to-peer data in a local corestore (described in [Storage and distribution](/pear/explanation/storage-and-distribution)). This guide covers finding what's installed and resetting an app's storage.

<Callout type="info">
  `pear data apps` and `pear drop` were removed in Pear v3. Applications now live in the OS application folder, and local corestore data is cleared with [`pear gc cores`](/pear/reference/pear/cli#pear-gc).
</Callout>

<Callout type="info">
  **Need the `pear` CLI?** Install it from **[install.pears.com](https://install.pears.com)**, or prefix any command below with `npx`. See [Install & upgrade](/pear/reference/pear/cli#install) for details.
</Callout>

## Find installed applications [#find-installed-applications]

`pear install pear://<key>` places apps in the standard OS location:

* **macOS** — apps in `/Applications`, binaries in `/usr/local/bin`
* **Linux** — apps in `~/Applications`, `~/AppImages`, or `~/.local/bin`; binaries in `~/.local/bin`

Browse that folder to see what's installed, the same as any native application. To inspect a specific application, pass its link to [`pear info`](/pear/reference/pear/cli#pear-info):

```console skip="machine-state"
pear info pear://<application-link>
```

Run `pear info` with no argument to view Pear platform information instead.

## Reset an application's storage [#reset-an-applications-storage]

There is no `pear uninstall`—remove the app from your OS application folder to uninstall it. To wipe an application's **local peer-to-peer storage** (its corestore) without touching the copy on the swarm, use [`pear gc cores`](/pear/reference/pear/cli#pear-gc) with the app link:

```console skip="destructive"
pear gc cores pear://<application-link>
```

From Pear 3.3.0 the application's name works in place of the link, taken from the `name` field of its staged `package.json`:

```console skip="destructive"
pear gc cores <application-name>
```

Names are not unique—if two staged applications share one, both are cleared. An unmatched name fails with `No cores found with name <name>`.

This clears the corestore cores tied to your local copy. Anything stored only locally (chat history, drafts, user-generated content) is gone afterwards. Use it when you want a clean slate for testing or to recover from a corrupt drive.

<Callout type="warn">
  From Pear 3.3.0, if any of the cores are **writable**—which they are for an application you stage yourself—`pear gc cores` stops and asks you to type `CLEAR` before it removes anything. Pass `--force` to skip the prompt in a script—without it a piped stdin loops on the prompt indefinitely rather than failing. On 3.2.0 and earlier writable cores were skipped instead of cleared. See [Writable-core confirmation](/pear/reference/pear/cli#gc-cores-confirmation).
</Callout>

The application binary itself stays available on the swarm; only the local storage is cleared. Re-running the application against the same link rebuilds an empty storage.