Changelog

Lookio is live

The new Lookio replaces the previous version: the app, the API, the MCP server and the widget are on their final addresses.

• The app is at dashboard.lookio.app, the API at api.lookio.app/v1, the MCP server at mcp.lookio.app/mcp and the widget at widget.lookio.app.
• Nothing to change on your side: the addresses used during the beta keep working, so connected MCP clients, scripts and installed widgets go on as before.
• CLI 2.0.1 and SDK 1.0.1 use these addresses by default.

Four logs, and widget formats you turn on or off

The Logs page of a workspace now holds four logs, and a widget's formats, tabs and designer changed.

• Answers. Every answer Lookio gave, from the app, Lookio AI, API keys, the MCP server and widgets: the assistant, who asked, the mode, the credits, the time and whether the resources held an answer. Metadata only, no question or answer text. GET /v1/logs/answers, list_answer_logs, lookio logs answers and logs.answers, with usage:read.
• Indexing. Every file, page or text read and indexed, with its status, what reading found and the reason of a failure. A site sync’s unchanged pages are left out unless you ask. GET /v1/logs/indexing, list_indexing_logs, lookio logs indexing and logs.indexing, with resources:read.
• Activity. Who changed what in the workspace, through which door (app, API, CLI, MCP, Lookio AI or Lookio itself), kept a year. Names of fields only, never content. GET /v1/logs/activity, list_activity_log, lookio logs activity and logs.activity, with admin.
• The Logs page. Four tabs, filters kept in the address of the page, and a See all logs link from an assistant, a widget, a resource and an API key.
• Figures. The answer and indexing logs have their own figures: GET /v1/logs/answers/stats and GET /v1/logs/indexing/stats.
• Widget formats. The chat bubble, the in-page chat and the hosted page are now each on or off, with three settings: bubble (on by default), embed and hosted_page (both off). In the API, the CLI and MCP they are settings.bubble, settings.embed and settings.hosted_page. A format that is off does not exist: its frame or hosted page answers 404, and the script draws no launcher when bubble is off. A new widget starts with the chat bubble only. See Install a widget.
• Widget tabs. A widget’s side sheet now has four tabs: Install (the formats, each with a switch, and how to install the selected one), Config (assistant, answer mode, sources, allowed domains, visitors and limits), Appearance and Logs (this month’s figures, the latest conversations and links to the Logs page filtered on the widget). They were Install, Appearance, Access and Chats.
• Widget designer. Appearance opens a large window with the brand, launcher, words and footer settings on the left and the live widget on a mock page on the right, as a chat bubble, in the page or as the hosted page, on desktop or mobile. See Customize a widget.
• Create a widget. The dialog asks for the widget name, then the assistant (searchable), then the allowed domains.

Changes to be aware of:

• The figures of the conversation log moved from GET /v1/logs/stats to GET /v1/logs/conversations/stats. The SDK method is logs.conversations.stats (it was logs.stats), and the CLI command is lookio logs conversations --stats.
• lookio logs list is now lookio logs conversations, and lookio logs stats is lookio logs conversations --stats.
• Three MCP tools were renamed: list_logs is list_conversation_logs, get_log_conversation is get_conversation_log and get_log_stats is get_conversation_log_stats.
• The usage:read, resources:read and admin scopes now also cover the answer, indexing and activity logs. See Logs.
• settings.hosted_page now defaults to false, where it was true. A widget that does not set it has no hosted page: set it to true, or turn on Hosted page in the Install tab, to get the link back.

Conversations, end users, feedback and logs

An API key now keeps its conversations, names the people who use your product and forwards their thumbs, and the workspace reads what people asked.

• Conversations with an API key. An answer returns a conversation_id and a message_id. Ask the next question with the conversation_id and Lookio reads the history itself. The done event of a stream carries both ids. See Conversations and end users.
• End users and storage. end_user names the person asking in your product and binds their conversations. store: false keeps nothing. Kept conversations are deleted 90 days after their last message.
• Feedback. Forward your users’ thumbs, with a comment, on an answer with POST /v1/conversations/{conversation_id}/messages/{message_id}/feedback, send_answer_feedback, lookio conversations feedback or conversations.feedback. See Feedback on answers.
• Logs. What people outside the workspace asked, from widgets, API keys and the MCP server, with filters and figures, in the API (/v1/logs), list_logs, lookio logs and logs.conversations. A member’s own chats stay personal. See Logs.
• Widget. A new Feedback setting turns the visitors’ thumbs on or off, and a thumbs down can come with a comment.

Changes to be aware of:

• An API key’s answers are now kept by default, where before nothing was stored. Send store: false to keep the earlier behaviour.
• The conversation endpoints, tools and commands now work with an API key, and the conversation tools are offered to keys over MCP.
• A widget’s conversations now have the shape of the logs: end_user replaces visitor, message_count replaces questions, and citations use resource_id like in an answer.
• Reading the logs needs assistants:write, the scope that manages assistants and widgets; query also sends feedback.

The new Lookio, in public beta

The new Lookio is open in public beta: the web app, the REST API, the CLI and MCP, built on one service layer.

The new Lookio is a rebuild of the platform. You add resources, give them to assistants and get answers with sources.

• Resources. Add texts, files (PDF, Word, PowerPoint, Excel, CSV, images and more), web pages and whole websites, with rules and a weekly sync. Importing is free. See Resources.
• Assistants. A context, answer guidelines, and three ways to choose what an assistant reads: all resources, selected ones or tags. See Assistants.
• Three query modes. Eco (10 credits), Flash (30) and Deep (80), one price per answer whatever its length, charged even when no answer is found. See Core concepts.
• Citations. Every answer names the passages it relied on, with their section and page.
• Workspaces, members and permissions. Admins and members, with per-member permissions on the Pro plan. See Members and permissions.
• REST API. Everything the app does, with scopes, idempotency keys, one error format and streamed answers. See the API overview.
• CLI. The lookio command, with JSON output for scripts and agents. See the CLI overview.
• MCP. A server for Claude, Cursor, ChatGPT and other clients, with OAuth, and a Code Mode for agents that write scripts. See the MCP overview.

Not available yet: the TypeScript SDK, the embeddable widget and webhooks.