Deleting things
What deleting a resource, an assistant, a tag, a conversation, a member or an API key removes, what it keeps and what cannot be undone.
Deleting is permanent. Lookio has no trash. This page says what each deletion removes and what it leaves.
| You delete | It removes | It keeps |
|---|---|---|
| A resource | The resource, its stored files, every version and the passages indexed from it. | Assistants. Past conversations. |
| An assistant | The assistant and its settings. | Its resources. Its conversations, as read-only history. |
| A widget | The widget, its visitors’ conversations and its link. Every page that embeds it stops showing it. | The assistant. What the widget cost, in your usage. |
| A tag | The tag from every resource and every assistant. | The resources. |
| A conversation | The conversation and its messages. | Everything else. |
| A member | That person’s access to the workspace, and their connections. | Their Lookio account. The workspace’s knowledge. |
| An API key | The key’s access, immediately. | Nothing the key created. |
Deleting a resource
Lookio first removes the resource’s passages from the search index, then deletes the resource and its files. If the index cannot be cleaned, the deletion is refused and nothing changes: try again in a moment.
A resource an assistant uses by name cannot be deleted. If an assistant’s knowledge is Selected resources and the resource is on its list, remove it from the assistant first. You get a conflict error otherwise.
An assistant that reads All resources, or a tag, does not block the deletion. It simply reads one resource fewer.
After the deletion, the words of the resource no longer count against your word allowance.
Deleting a website deletes all of its pages.
Deleting an assistant
An assistant that a widget answers for cannot be deleted: delete the widget, or point it at another assistant, first. Its resources stay. Conversations people had with it remain readable, under Deleted assistants in the chat, but nobody can continue them.
Deleting a widget
Deleting a widget removes it, its link and the conversations visitors had through it, and every page that embeds it stops showing it. What it cost stays in your usage. To stop it without losing it, set it to paused. Deleting a widget needs the right to delete assistants. See Access and limits.
Deleting a tag
The tag is removed everywhere. An assistant that followed it stops reading the resources the tag brought to it, so check which assistants follow a tag before you delete it. Only admins can delete tags.
Deleting a conversation
You can delete your own conversations from the chat. It removes the conversation and all its messages. Nobody else can delete them for you.
An API key deletes the conversations it started with Delete a conversation. That also removes them from the workspace’s logs and from their figures. Lookio deletes any conversation 90 days after its last message.
Removing a member or revoking a key
A removed member loses access at once, and so do the CLI logins and MCP clients they connected. A revoked API key stops working at once. Both can be undone only by creating a new access: a new invitation, a new key.
Confirmation in the CLI and MCP
The CLI asks you to confirm lookio resources delete and lookio assistants delete. With no terminal, it exits with an error that names --force instead of waiting. The MCP tools that delete are marked destructive, and AI clients are told to confirm with the person first. See Safety and permissions.