---
summary: When and how to update the docs and skills Flow installed in your project.
---

# Updating Flow

The docs and skills Flow installed in your project come from your version of `@adonisplus/flow` and from the packages in your `package.json`. Update them when either one changes.

## When to update

- After a new release of Flow, which adds and changes docs and skills. The [changelog](/changelog) lists what changed in each release.
- After you upgrade a package to a new major version, such as `@adonisjs/inertia` from 4.x to 5.x.
- After you add a package that the [Knowledge base](/docs/flow/knowledge-base) covers, or remove one.
- After you clone the project. `.flow/docs/` and the skills are in `.gitignore`, so a new clone has none of them.

## How to update

For a new release, update the Flow package first.

::code-group{sync="pm"}
```sh [npm]
npm i -D @adonisplus/flow@latest
```

```sh [pnpm]
pnpm add -D @adonisplus/flow@latest
```

```sh [yarn]
yarn add -D @adonisplus/flow@latest
```

```sh [bun]
bun add -d @adonisplus/flow@latest
```
::

Then run the install again. If you only upgraded, added or removed a package, or cloned the project, this is the only step.

```sh
npx @adonisplus/flow install
```

Flow reuses the answers saved in `flow.lock`, and does not ask about your agents or your stack again. It asks only about packages it finds for the first time, and drops the packages your `package.json` no longer has, along with their docs.

## Starting over

To answer all the install questions again, delete `flow.lock` and run the install.

```sh
rm flow.lock
npx @adonisplus/flow install
```

See [Installation and setup](/docs/get-started/installation) for what the install writes.
