Troubleshooting
The five most common difficulties with an AI assistant, their cause and the solution.
The assistant doesn’t see TOWeb
Cause: the conversation started before TOWeb was added, or the assistant was not quit completely.
Solution: check that Allow AI assistants is turned on, quit the assistant completely, start it again and open a new conversation. In TOWeb, the button should show Connected to….
Permission requests keep coming
Cause: the assistant asks permission for every action.
Solution: allow TOWeb once and for all, with Always allow in Claude, or automatic approval in Codex.
The assistant stops partway
Cause: your assistant’s quota has been reached, which happens quickly on a free plan.
Solution: what has been done stays in TOWeb. Pick up later in a new conversation, for example: “Continue the site open in TOWeb: the Contact page is still to do.” For a whole site, prefer a paid subscription and work page by page.
TOWeb doesn’t show the changes
Cause: TOWeb is open on a different site from the one the assistant is working on.
Solution: open in TOWeb the site the assistant is working on. It joins you right away, and you see its changes live.
The assistant shows toweb as failed
Cause: an update or a reinstallation of the assistant reset its configuration.
Solution: in TOWeb Settings › AI, click Add to… again, then quit the assistant completely and restart it.
Gemini searches the web for TOWeb
Cause: TOWeb’s styles and templates are not on the web, and Gemini looks for them there by reflex.
Solution: write in your request “Use only the tools of the toweb server: no screen control, no web search, no file reading.” Also start Gemini from an empty folder.
Still having trouble? Contact support from TOWeb.