Lookio Docs
Lookio websiteOpen Lookio
WidgetCustomize a widget

Customize a widget

The words, colours, launcher, position, language and behaviour of a widget, designed next to a live preview in the app.

Open the widget’s Appearance tab. It shows a summary of the look, and an Open the designer button. The designer is a large window. The brand, launcher, words and footer settings are on the left. On the right is the live widget on a mock page, shown as a chat bubble, in the page or as the hosted page, on desktop or on mobile.

Every change saves on its own and shows at once in the preview. The preview is the real widget: questions asked there are real answers and are charged. It also shows a format that is off, so you can design it before you turn it on.

Words

The Words group of the designer.

SettingWhat it does
TitleThe chat’s heading. Empty, it shows the assistant’s name.
GreetingThe first message a visitor reads.
Suggested questionsUp to four, shown as buttons before the first question.
PlaceholderThe text in the empty question box.
Notice under the boxA short word on how answers are made. Empty, nothing shows.
Language of the buttonsThe language of the widget’s own words. Answers always follow the language of the question.

Look

The Brand and Launcher groups of the designer.

SettingOptions
ThemeLight, dark, or auto (follows the visitor’s system).
ColourAny colour. Text on it switches to black or white for contrast.
CornersSquare to round.
LauncherA round button, a button with a label, or a centered bar (chat bubble format). The centered bar sits at the bottom centre of the page, shows the placeholder, and opens the chat in the middle of the screen; on a phone the chat takes the whole screen.
IconThe launcher’s icon: chat bubble, message, question, sparkle, assistant or search. On paid plans, your own image instead (a logo or a face, shown round): PNG, JPEG, WebP or GIF, 256 KB at most. Also through the API and lookio widgets set-image.
FaviconThe hosted page’s tab icon. By default it is drawn from your colour and icon. On paid plans, upload your own (PNG, JPEG, WebP, GIF or ICO, 256 KB at most), in the app, through the API or with lookio widgets set-image.
PositionBottom right or bottom left (round button and button with a label).

Behaviour

These settings are in the widget’s Config tab, under Visitors, and Sources under Answers. The footer link is in the designer. Visitor and limit changes apply together when you select Save preferences. Reset discards unsaved changes.

SettingWhat it does
SourcesHow answers show where they come from. See below.
Remember the conversationFollow-up questions see the previous ones. Off, each question stands alone. Messages stay in Logs and become context again when enabled.
Visitors’ chat historyOn (the default), a visitor who comes back on the same browser finds their past chats in a Past chats list. Off, past chats are hidden and every visit starts fresh. A widget-specific browser proof remains for visitor limits; re-enabling restores access to retained chats. In the API it is settings.visitor_history. See Visitors’ conversations.
FeedbackOn (the default), visitors see a thumbs up and a thumbs down under each answer, and can add a few words about what was wrong. Off, no thumbs are shown and new ratings are refused. Existing ratings and comments are kept. A visitor can change their mind or take a thumb back. In the API it is settings.feedback. Read the thumbs in Visitors’ conversations.
Powered by LookioA small link under the chat. Shown on the free plan; paid plans can hide it.

Sources

Choose how answers show where they come from. Lookio applies the choice on its servers: an address you turned off never reaches the visitor’s browser.

ModeWhat visitors see
Numbered, with linksAnswers cite [1], [2]. A tap on a number shows the passage; web pages link to their address. The default.
Numbered, no linksThe same numbers, titles and passages, without any address, so visitors stay on your site.
Links in the textThe answer links its own words to the source pages, as a person writing would, with no list. Only sources with a web address can be linked. Describe the style you want in the assistant’s context or answer guidelines, for example “link at most once per paragraph”.
HiddenNo source at all.

You can review every source in the widget’s conversations in Logs, whatever the mode.

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.