A research tab evaporates. A page does not.

ChatGPT will answer. Notion will search your pages. Confluence will ask Rovo. Kraken research is a run you can follow, with citations, that you can file as a document next to the client.

The useful part of a research answer is rarely the chat. It is the paragraph you needed three weeks later, with the link still attached, filed where the rest of the client’s work lives. A tab does not do that. A page does.

You pick a model the workspace is allowed to use. Kraken either answers in a short turn or starts a longer research run and gives you the page back. The browser does not have to stay open. Come back later and the run is where you left it, including a failure you can read instead of a spinner that died.

Follow it, then keep it

• The run has phases: preparing, search, read, results, think, write, memory, done. You can see which one you are in.
• Citations stay with the run. They are not a footnote you have to reconstruct from memory.
• Save as document turns a useful answer into a real page: headings, lists, tables, links and the citations. You choose where it is filed.
• From there it is a Kraken document. Searchable, editable, and linkable to a client, a project or a task.

Sources that are already yours

Connected apps can be read-only sources on the same run. The search stays bounded. A hit comes back as a citation, not as a dump of the mailbox into the prompt. The connection itself never reaches the browser. If you only needed to ask your own wiki a question, you do not have to start a web run at all.

Research that only lives in a chat log is a meeting you forgot to write down.

Use Kraken research when the answer has to outlive the session. Use a chat tab when you will not need it again.