> For clean Markdown of any page, append .md to the page URL.
> For a complete documentation index, see https://docs.nvidia.com/docsfab/llms.txt.
> For AI client integration (Claude Code, Cursor, etc.), connect to the MCP server at https://docs.nvidia.com/docsfab/_mcp/server.

# Update or Uninstall DocsFab

> Update or reinstall your DocsFab source checkout, repair a packaged installation, or remove the global command.

For internal testing, update the source checkout linked to your global DocsFab
command. Development builds follow `main` and can be unstable.

## Before Changing Versions

Stop DocsFab processes and back up the configuration and run state. Follow
[Recover a Local CLI Installation](/docsfab/manage/recover-local-state#recover-a-local-cli-installation)
for backup and restore checks.

## Reinstall or Change the Version

To update an existing checkout on `main`, run these commands from its root:

```bash
git pull --ff-only origin main
npm --prefix packages/runtime ci
npm install --global ./packages/runtime
docsfab --version
```

The pull command fetches `main` from `origin` and fast-forwards your local
branch; it stops if the histories diverge. `npm ci` installs the updated
runtime dependencies from the lockfile. The global install links the CLI to
that checkout.

To reinstall without pulling new changes, repeat the npm commands in
[Install DocsFab](/docsfab/get-started/installation#install-docsfab).
Run `docsfab setup` again when you want to change the model configuration.

After installation, `docsfab --version` confirms the installed version and
checks that the CLI starts on the current Node.js version. Use
[Check DocsFab Readiness](/docsfab/manage/check-readiness) to inspect the configuration and
connection for your intended operation.

## Repair an Installed Package

If doctor reports damaged packaged assets, stop DocsFab processes and follow
its printed reinstall command. Replace `<tarball URL>` with the exact release
artifact URL from your installation record or authenticated package metadata.
Do not substitute an unpinned registry package.

The repair command uses `npm i -g` to reinstall the global CLI from that
artifact. `--ignore-scripts` disables package lifecycle scripts because the
release already contains compiled assets. `--engine-strict` makes npm reject
an unsupported Node.js version before reinstalling. Then rerun the command
that reported the integrity error.

For source checkouts, follow doctor's pack-regeneration command instead.
Refer to [Runtime Readiness and Doctor Checks](/docsfab/manage/check-readiness)
for the integrity diagnostics.

## Uninstall

To remove the global command, run:

```bash
npm uninstall --global docsfab
```

Uninstalling leaves your DocsFab configuration, run records, and patches in
place.

## Related Topics

Use these topics for the supporting contracts and next actions.

- [Install DocsFab](/docsfab/get-started/installation)
- [Manage Local Configuration and Credentials](/docsfab/manage/local-configuration)
- [Install a Development Build](/docsfab/manage/development-installation)