I signed in, but I cannot see my organisation
- Confirm you are signed in with the correct Frigga account.
- Confirm your account has CodeZero access.
- Confirm you have been added to the correct organisation.
- Sign out and sign in again.
- Restart VS Code.
- If the organisation is still missing, contact hello@frigga.cloud.
Sign-in keeps failing or returning me to the login screen
- Confirm your internet connection is active.
- Retry sign-in from the CodeZero panel.
- Sign out of Frigga and authenticate again.
- Restart VS Code.
- Check the CodeZero Output channel for authentication errors.
- Contact support if the issue persists.
CodeZero is connected to the wrong organisation
- Sign out of CodeZero.
- Sign in again with the correct Frigga account.
- Select the intended organisation.
- Reopen your repository.
- Start a new CodeZero session.
My repository is not appearing in CodeZero
- Confirm you are signed in to the correct organisation.
- Confirm the repository has been connected to your organisation.
- Confirm repository indexing has completed.
- Refresh the CodeZero panel.
- Restart VS Code.
- If the repository should already be available, contact support.
CodeZero says my repository is still indexing
- Wait for indexing to complete.
- Refresh the CodeZero panel after indexing finishes.
- Reopen the repository if the status does not update.
- Restart VS Code if the repository remains stuck.
- Contact support if indexing does not complete.
CodeZero cannot find Claude Code
- Confirm Claude Code is installed.
- Open a terminal and run claude.
- Confirm the claude binary is available on your PATH.
- Restart VS Code after installing or updating Claude Code.
- Reopen CodeZero and start a new session.
Claude Code is installed, but CodeZero still cannot detect it
- Run claude from the same environment used to launch VS Code.
- Confirm there are no PATH differences between your terminal and VS Code.
- Restart VS Code completely.
- Re-authenticate Claude Code if required.
- Start a new CodeZero session.
The agent cannot find context from another repository
- Confirm the repository is connected to the same organisation.
- Confirm indexing has completed.
- Confirm you are working in the correct organisation.
- Start a new agent session.
- Retry the request with the relevant feature, service or repository named explicitly.
- Contact support if the repository is indexed but still unavailable.
Git history, diff or blame is not displaying correctly
- Confirm the folder open in VS Code is a Git repository.
- Confirm the repository has a valid Git remote and history.
- Refresh the CodeZero panel.
- Restart VS Code.
- Check the CodeZero Output channel for errors.
CodeZero is showing an unsupported version message
- Update CodeZero to the latest available version.
- Run code0: Check for Updates from the Command Palette.
- Reload VS Code after the update.
- If automatic updating fails, install the latest .vsix manually.
CodeZero is not updating automatically
- Check the code0.autoUpdate setting.
- Run code0: Check for Updates manually.
- Confirm VS Code can access the CodeZero update endpoint.
- Restart VS Code.
- Install the latest .vsix manually if required.
Where can I find CodeZero logs?
- Open View → Output in VS Code.
- Select CodeZero from the output channel dropdown.
- Reproduce the issue.
- Include the relevant output when contacting support.
I am using a local or self-hosted CodeZero deployment
- Confirm code0.backendUrl points to the correct backend for your environment.
- Confirm code0.identityUrl points to your identity service.
- Confirm code0.accountsUrl points to your sign-in page.
- Restart VS Code after changing these settings.
CodeZero is still not working
- Confirm you are on the latest CodeZero version.
- Restart VS Code.
- Re-authenticate with Frigga.
- Start a new CodeZero session.
- Check the CodeZero Output channel.
- Contact hello@frigga.cloud with the issue and relevant logs.