Skip to main content

Documentation Index

Fetch the complete documentation index at: https://sherlock-osint.vercel.app/docs/llms.txt

Use this file to discover all available pages before exploring further.

A workspace is the primary organizing unit in Sherlock. Every investigation, research project, or monitoring effort lives inside one. When you start working on a new topic — a company, a policy question, a threat actor, a geopolitical event — you create a workspace to hold everything related to it: the AI-generated reports, your chat sessions, the research boards you sketch ideas on, timeline events, live signals, and any notes, links, or files you collect along the way.

​
What a workspace contains

Each workspace acts as a self-contained context for your research. Inside it you’ll find:

Artifacts

Structured investigation reports generated by AI runs, plus saved timeline snapshots. Each artifact has sections, key findings, evidence records, entities, and follow-ups.

Runs

The AI analysis sessions that produced your artifacts. Runs record the topic, scope, model, and configuration used so you can trace how a report was generated.

Chat history

Workspace-grounded conversations with the AI. Chat sessions are scoped to the workspace so the AI has context about your research when you ask follow-up questions.

Research boards

Multi-page canvas boards built on tldraw. You can place artifacts, entities, signals, notes, links, files, and promoted chat excerpts on a board to map out connections and build presentations.

Timeline

A chronological view across runs, artifacts, signals, item events, and chat actions. You can save named timeline views and take snapshots as artifacts.

Signals

Live monitor results and saved feed items scoped to the workspace. Signals can trigger new investigation runs or be promoted onto research boards.

Canonical items

Notes, links, files, media, and excerpts promoted from chat that belong to the workspace library. Items appear in Files and can be placed on research boards.

Network graph

A D3 relationship graph of entities, concepts, and sources associated with the workspace, with support for manual nodes and links.

​
Workspace identity

Every workspace has a display title — the name you see in the header and workspace grid. It keeps the top-level interface clean and human-readable. Separately, Sherlock stores launch metadata that carries the investigative context used when the workspace was created — the primary topic, the investigative angle, and a note about which sources were prioritized. This context is used in run prompts, exports, and the workspace-home summary. This separation means your workspace can have a short, readable title (e.g., “Apex Corp Due Diligence”) while the underlying prompt context retains more precise structured detail. Workspaces also support an optional icon to help you visually distinguish them in the workspace grid.

​
Browsing and navigating workspaces

The Files surface is your workspace home base. It opens to a grid of all your workspaces, where you can:
  • Create a new workspace
  • Open an existing workspace
  • Browse artifacts and canonical items across workspaces
  • Delete or export individual workspaces
Selecting a workspace takes you to the workspace home, a lightweight overview showing:
1

Summary counts

At-a-glance totals for artifacts, runs, chat sessions, signals, and canonical items in the workspace.
2

Recent activity

A feed of recent artifacts, runs, and chat sessions so you can pick up where you left off.
3

Saved timeline views

Named timeline snapshots you’ve saved from the Timeline surface, accessible directly from the workspace home.
4

Quick links

One-click navigation into Artifact view, Chat, Research Board, Timeline, Network Graph, and Files for that workspace.

​
Workspace isolation

Each workspace maintains its own isolated context across three surfaces:
  • Chat grounding — when you open a chat inside a workspace, the AI draws on that workspace’s artifacts, signals, and items for context. A question asked in one workspace does not pull data from another.
  • Board canvases — boards and their contents are scoped to the workspace. Canonical items placed on a board belong to that workspace’s library.
  • Timeline — the workspace timeline only shows events originating in that workspace.
This isolation means you can run parallel investigations on related topics in separate workspaces without their data bleeding together.

​
Using the omnibox to jump between workspaces

The shared header omnibox gives you fast access to your workspaces, saved timeline views, artifacts, items, chats, runs, and signals from anywhere in the app. Recent destinations are stored durably so your most-used workspaces are always a keystroke away.
Workspace data is stored locally in your browser using IndexedDB. Clearing your browser’s site data or storage for the Sherlock origin will permanently delete all your workspaces and their contents. Use Settings → Data → Export to save a backup before clearing browser storage or switching devices.