> For the complete documentation index, see [llms.txt](https://docs.bugbug.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.bugbug.io/your-account/forgot-password.md).

# Forgot password

Reset your BugBug password: request a reset link, set a new password, and what to do if the link has expired.

1. Go to the sign-in page <https://app.bugbug.io/sign-in/>.
2. Click **Forgot password?**.
3. Enter the email address of your BugBug account.
4. Click **Reset password**. BugBug shows **Check your e-mail**.
5. Open the email from BugBug and click the reset link.
6. Enter the new password twice and click **Change password**.
7. Sign in with the new password. BugBug doesn't sign you in automatically after the reset.

After the reset, BugBug sends you an email confirming that your password was changed.

A new password must have at least 8 characters, can't be too similar to your email address or name, can't be a commonly used password and can't consist of digits only.

## Good to know

* **You signed up with Google, GitHub or Microsoft.** If your account doesn't have a password, BugBug can't reset it and tells you to sign in with the service you used to sign up.
* **The link has expired.** A reset link works only once and expires after some time. If BugBug shows **Link expired**, click **Request a new link**.
* **Too many failed sign-in attempts.** After you reset your password, you can sign in again right away.
* **Two-factor authentication.** If you turned on [two-factor authentication](https://docs.bugbug.io/your-account/two-factor-authentication.md), BugBug still asks for the code from your authenticator app after you reset your password. If you lost your phone, use one of your recovery codes.

If you're signed in and know your current password, change it in [Account settings](https://docs.bugbug.io/your-account/account-settings.md#change-password).


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.bugbug.io/your-account/forgot-password.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
