> ## 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 dev

> devias dev applies the manifest once, then watches the manifest folder and applies each change on save. It never applies a change that deletes data and never asks questions. Use devias apply --allow-destructive for deletions.

`devias dev` watches a module's folder and re-applies the manifest on every save.

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

It applies the manifest once, then watches the manifest's folder. On each save it reads the manifest again and applies the change, printing a line with the time.

## Only safe changes

`dev` never applies a change that deletes data and never asks questions. If an edit would delete something, it reports that and waits. `devias apply --allow-destructive` applies it.

The studio in development already applies safe changes to installed modules on start-up. `devias dev` applies changes the moment they are saved, against any server.

## Related

* [Create a first module](https://docs.devias.io/guides/modules/first-module.md): a procedure that can use it.
* [devias apply](https://docs.devias.io/reference/cli/apply.md): apply once.


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