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

> What you see when WednesdayAI publishes a new version, and what to do if an update misbehaves

# How WednesdayAI updates reach you

# How WednesdayAI updates reach you

You do not publish WednesdayAI yourself. Your administrator installs a version, and you keep chatting in Telegram, Discord, WhatsApp, or whatever app you already use.

## What you can expect

* A normal update keeps your chats, memories, and saved settings.
* The assistant still answers in the same chat thread after the gateway (the always-on WednesdayAI process) restarts.
* Version lines and status text should say **WednesdayAI**, not the older OpenClaw name.

Most people should stay on the **stable** channel. That is the `latest` package on npm.

## Choose how much change you want

Ask your administrator if you are unsure which channel you are on.

<Steps>
  <Step title="Stay on stable">
    Everyday use. Lowest chance of breakage. This is the default.
  </Step>

  <Step title="Try beta only if asked">
    Preview of the next stable release. Useful for one spare install, not your only production chat.
  </Step>

  <Step title="Leave dev to contributors">
    Dev is for people building WednesdayAI. It can change without warning and is not for an unattended home or office install.
  </Step>
</Steps>

## If a new version feels wrong

1. Tell your administrator which chat app you use and what changed (no replies, old product name, login loop).
2. They can pin the last good version, for example `wednesdayai@<last-good-version>`, then restart the gateway.
3. Start a new chat if an old thread still quotes outdated instructions.

<Warning>
  Do not delete your workspace or config files to "fix" a bad update. Those folders hold your memories and credentials. Ask your administrator to roll back the package instead.
</Warning>

## Related

* [Updating](/admin/install/updating)
* [Release channels](/admin/install/development-channels)


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