Support

Sign-in problems

Confirm that you are using the same email account used to create LoveCode. If your session expires, sign in again. Repeated authentication failures can indicate a temporary service or connectivity issue.

GitHub connection

Open Connections or Account in LoveCode and reconnect GitHub through the secure OAuth flow. If authorization was revoked on GitHub, reconnecting is required. Advanced personal access tokens should only be entered in LoveCode’s dedicated secure credential field.

Repository not visible

Confirm that the connected GitHub account has access to the repository and that the authorization scope permits LoveCode to read it. Organization repositories can require separate organization approval.

Agent task is waiting

LoveCode can pause work when a provider is unavailable, required configuration is missing, or a sensitive action needs approval. Open the task timeline for the current stage and follow the displayed recovery or approval action. LoveCode intentionally avoids reporting completion when verification has not passed.

Diff, test or build does not match

Check the task’s evidence and current workspace state. If a task was restarted or the repository changed outside LoveCode, rerun verification before publishing changes.

Offline or unstable connection

Some safe actions can queue while offline. Reconnect to the internet, return to LoveCode and allow the app to refresh. Do not repeat destructive actions unless the current task state confirms the previous request did not execute.

Delete your account

In the LoveCode app, open Account → Delete account. Read the confirmation notice and confirm deletion. This is the supported in-app account deletion path for LoveCode 1.0.

Privacy and terms

Read the Privacy Policy and Terms of Use for details about data processing, connected providers, AI-generated work and account responsibilities.

When reporting a problem

Include the LoveCode app version, the affected screen, an approximate time of the problem, a non-sensitive task/project identifier if available, and the exact user-visible error text. Remove repository secrets and credentials from screenshots or logs before sharing them through any developer support channel listed on the App Store product page.