Troubleshooting
Something not working? Most Kite hiccups are temporary and easy to fix. This section walks you through the most common issues, what usually causes them, and what to try first. In most cases your site and your work are safe. The problem is just getting in the way of seeing it.
In this section
- Preview Won't Start: the preview shows "Preview couldn't start" or stays blank.
- Chat Stuck or Page Crashed: a turn that never finishes, a stream error, or the "Something went wrong" screen.
- Undo Changes & Version History: restore your site to an earlier version.
- Form Emails Aren't Arriving: contact form notifications do not reach you.
Problems in Slack
- Kite is not responding. Make sure Kite has been invited to the channel, then mention it directly. If the channel is set to respond only when tagged, Kite waits to be tagged. See Add Kite to Slack.
- Kite is waiting on you. With the propose-first setting, Kite asks before work that changes public messaging or spends money. Read its last message in the thread and reply. See Approvals and autonomy.
- Kite keeps repeating the same failed step. Stop, rephrase, and if it continues, contact support. See When Kite loops.
Older sites are read-only
Sites built on Kite's earlier HTML stack can no longer be edited. They stay published, and the editor shows an Upgrade to Next.js offer that rebuilds the site on the current stack so you can edit it again.
How to contact support
Open the Chat with us button inside Kite (it is also on kite.ai). There is no support email address. When you write, include:
- Your Slack workspace name and the channel where you were working with Kite, if the problem involves Slack.
- Your site URL or project link, so the team can find the project.
- What you were trying to do and what happened instead. For example, "I asked Kite to change my homepage header and the preview went blank."
- What you already tried, such as refreshing, reopening, or a different browser.
- Any error message you saw, copied exactly or as a screenshot.
- A screenshot of the issue whenever possible.
- Your browser and device, for example, "Chrome on a Windows laptop."