Updating and reporting problems

Before updating

1. Read the release notes

   Check which platforms the release supports and whether it has migration steps.

2. Save and back up your work

   Commit your changes and back up anything you cannot lose.

3. Stop active tasks cleanly

   Let running agents and terminals finish or stop before replacing the desktop app.

4. Update the client too, if required

   Some releases need a matching client version. Update the client when the release notes say so.

5. Retest, on the computer and then the phone

   Open a project locally first, then try the same thing on your paired device.

Write a reproducible report

A report someone else can act on has the same seven lines every time:

Desktop version and operating system:
Client version and device:
Project type (for example, Vite or Next.js):
Connection: same network / different network
Steps to reproduce:
Expected result:
Actual result and visible diagnostic code:

1. Remove anything private

   Credentials, connection codes, personal file paths and private project content. Strip them from screenshots and logs too.

2. Include a small example when you can

   A tiny project that fails is far easier to fix than a description of a large one.

3. Narrow the failing step first

   Start with troubleshooting so you report one specific problem rather than a symptom.

Check the release boundary

Early access and full V1 have different gates. Accounts, billing, remote wake, broader extension execution and additional platforms each have their own acceptance work. A feature being described upstream does not mean it is in your build.

Follow release status rather than assuming an upstream feature is included in the Lyre build.