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

> ## Agent Instructions
> The docs are served at https://docs.devias.io. Every path in these docs is relative to that root: /llms.txt is https://docs.devias.io/llms.txt.
> Devias is an open-source platform that works as an operating system for a business: a core (records, views, workflows, agents, permissions) with installable modules.
> Pages are typed by folder. concepts/ explains what things are, guides/ gives procedures, reference/ is exhaustive (SDK, CLI, HTTP API), operate/ covers hosting. Use /start/glossary for exact terms.
> Every id in a module (module, object, field, view, action, workflow, step, connection, variable, event, policy) is a uuid. Generate them with `devias id <count>`. Never invent dotted or readable ids.
> Run `devias plan` and read its output before `devias apply`. Apply only what the plan says.
> The OpenAPI document, including the routes of the modules in the reference setup, is at /reference/api/openapi.json.
> Devias is young and changes quickly. If a page and the source repository (github.com/devias-io/devias) disagree, the repository is right.

# devias uninstall

> devias uninstall shows what would be removed and asks before doing anything. Records in the module objects are removed with them, so it is destructive: --allow-destructive is required for a module that owns data. It removes only what the module owns. Core studio modules cannot be uninstalled.

`devias uninstall` removes a module and everything it owns from a workspace.

```bash theme={"dark"}
devias uninstall -w <workspaceId> -m ./src/manifest/index.ts
```

It shows what would be removed and asks **Uninstall?** before doing anything. Records stored in the module's objects are removed with them, so removing an object is a **destructive** change.

| Flag | What it does |
| - | - |
| `-y, --yes` | Skip the question. |
| `--allow-destructive` | Allow the deletions. Without it, a module that owns data is not removed. |

It removes only what the module owns. Anything the workspace created, such as its own fields on the module's objects, is not part of the module's plan.

Core parts of the studio cannot be uninstalled.

## Related

* [devias plan](https://docs.devias.io/reference/cli/plan.md): preview first.
* [Install and connect modules](https://docs.devias.io/guides/studio/modules.md): uninstall from the studio instead.


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