Reference
Get back to building.
A practical checklist for installation, sign-in, agents, terminals, and voice.
The app will not install or open
Confirm that the installer matches your operating system and architecture. Read its release status: a local test artifact is not a signed public release. Windows and Linux candidates still require platform testing.
If a verified installer is not available, use the browser demo. Do not bypass an operating-system warning to treat an unverified artifact as a production release.
Desktop sign-in is not completing
- Use the same account you created on the website.
- Start a fresh connection from the desktop app if the code expired.
- Check that the browser connection code matches your app.
- Check your account’s subscription status; website login and desktop entitlement are separate.
An agent is missing or returns an error
- Check that the CLI is installed and runs in your normal terminal.
- Sign in through the provider and confirm that the account can run a request.
- Select the intended account in the workspace.
- Read the exact provider error. Authentication, model access, and usage limits have different remedies.
Voice does not start or produces no text
- Check that you are using a macOS build with voice controls.
- Review microphone and speech permissions in system settings.
- Confirm that the selected engine and any required local model are available.
- Check the selected destination and recording status before retrying.
Share a useful report
Include your app version, operating system, the steps to reproduce, and what you expected. Remove credentials and private project content from logs or screenshots.