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

# Update Policy

> Manual update policy for the current BRIK64 CLI beta.

BRIK64 updates are manual in the current public local workflow. This keeps local CLI behavior explicit while the product is in public beta.

The public CLI beta is installed through the public installer. Use `brik64 --version` after installation and compare with [GitHub Releases](https://github.com/brik64/brik64-cli/releases) when you need the exact resolved version.

Install or update:

```bash theme={null}
curl -fsSL https://brik64.com/cli/install.sh | bash
```

Verify after updating:

```bash theme={null}
brik64 --version
brik64 help
```

## Current Update Model

| Surface                 | Update behavior                                                               |
| ----------------------- | ----------------------------------------------------------------------------- |
| CLI beta                | Manual install or reinstall through `https://brik64.com/cli/install.sh`.      |
| Release notes           | GitHub Releases and this changelog.                                           |
| Documentation           | Live documentation pages and `.md` routes update through the docs deployment. |
| SDK packages            | Not a current public update path unless a release note lists the package.     |
| Platform/cloud features | Updated through their own release note when publicly available.               |

## Update Checklist

After updating:

1. Run `brik64 --version`.
2. Run `brik64 help`.
3. Confirm the install source used.
4. Check the relevant release note.
5. Re-run the local workflow you depend on.

Login is not required for local CLI use. Hosted platform features can require authentication when the specific feature documents that requirement.

## What Changes Later

Future release channels may introduce opt-in checks or platform-managed updates. Those behaviors will be documented in [Channels](/releases/channels) before users are expected to rely on them.