Lookio Docs
Lookio websiteOpen Lookio
WidgetWidget troubleshooting

Widget troubleshooting

What to check when the bubble does not show, the chat refuses to load in a frame, or visitors read that the assistant cannot answer.

The bubble does not show

  • The chat bubble is off. Open the Install tab and turn Chat bubble on. The script then draws nothing, and says so in the browser console.
  • The domain is not allowed. Open the browser console on your site: the widget says when the domain is not in the widget’s Allowed domains. Add it in Allowed domains, in the Config tab.
  • The widget is paused. Turn Live on.
  • Its assistant reads no resource. A widget whose assistant has nothing to read does not show at all: the bubble is not drawn and the console stays quiet. The widget’s sheet says “Not showing: its assistant reads no resource” with a link to the assistant. Connect resources to the assistant (and wait for them to be ready).
  • The script is missing or blocked. Check that the page loads https://widget.lookio.app/v1/widget.js, and that a content security policy on your site allows it (script-src and frame-src for https://widget.lookio.app).

The in-page chat or the hosted page says “not found”

That format is off. Open the Install tab and turn on In the page or Hosted page. A new widget has the chat bubble only.

”Refused to display in a frame”

The page that frames the chat is not an allowed domain. Add its host, including subdomains such as docs. or www. if you list them one by one.

Visitors read “The assistant cannot answer right now”

One of these is true: the widget reached its monthly credit ceiling, the workspace has no credits left, the widget is paused, or its assistant was deleted. A widget whose assistant reads no resource is not shown at all, rather than answering. Check the widget’s Config tab and your credits.

Visitors read “Too many questions”

A visitor reached their hourly or daily limit, or many questions came from one network address within a minute. Raise the visitor limits in Config if real visitors meet them.

Answers say the sources do not cover the question

The widget answers from its assistant’s resources only. Check what the assistant reads in Assistants, and that those resources are ready.

Use these docs with your AI tools

An AI agent can read this documentation directly. You do not need an account or an API key. Everything here is public and read-only.

Query these docs via MCP

Recommended

Add this server to Claude, Claude Code, Cursor, Mistral, or any tool that supports MCP. Your agent can then search Lookio Docs documentation and read it in full, instead of answering from memory.

https://lookio.app/docs/mcp
  • searchFind the passages that answer a question.
  • fetchRead one page in full, as Markdown.
  • list_pagesSee every page in this documentation.

Query these docs over HTTP

The same tools also work as plain web requests. Use this for scripts, or for any tool that does not support MCP. There is one endpoint per tool. Arguments go in the query string, and the answer comes back as JSON.

https://lookio.app/docs/api/docs/search?query=custom+domain

Read the OpenAPI description. It is built from the same definitions as the tools, so it always matches what the endpoints do.

Read these docs as Markdown

Add .md to any page URL to get its Markdown source. You can also send the headerAccept: text/markdown to the page URL itself.

To read the whole documentation in one file, open llms-full.txt. For a short index of every page, open llms.txt.