Start Here
With Lore, we help teams organize AI work, instead of it living on one person's computer and disappearing. We gather every prompt, skill, and AI session and turn it into searchable, shareable infrastructure. Lore preserves the context behind useful threads and enables several use cases built on top of this data.
We initially built Lore to share our Claude threads with each other: as contextual links on PRs, snapshotting some research or investigating for someone else to pick up, or just "check out this cool thing I did." Since then, we've run into many other use cases, and built a whole product around this primitive.
Quickstart
On macOS, download the desktop app, sign in, and you're done: it captures your sessions in the background and installs the Lore plugin into your coding agents automatically. It supports Claude Code, Cowork, Claude Desktop, and Amp for now. See Using Lore → Desktop App.
Download the macOS app
Once you're set up, have your teammates join just by signing up; we'll automatically add users with the same email domain to your workspace.
For scripting and advanced workflows (lore threads fork and more), there's also an optional CLI: npm install -g @loredotlink/cli
For detailed guides on sharing, reading, forking threads, and managing privacy, see the Using Lore section.
Privacy
Lore threads can be in one of three privacy settings:
private is visible only to you.workspace is visible to your team (anyone logged in with your same email domain).public is visible to anyone with the URL.
New threads default to workspace if you belong to a team workspace and haven't turned off the Share new threads with my workspace setting (on by default). If you're not in a workspace, or you turn that setting off, new threads default to private.
If you use the CLI's background daemon, you can control which directories it watches with lore listen commands and fine-tune uploads with filter rules. See Privacy and Visibility for details.
Concepts
A quick tour of the nouns you'll see throughout these docs.
Sessions and threads
A session is the local transcript your coding agent produces as you work: the running record of messages, tool calls, and file edits inside Claude Code, Cowork, Claude Desktop, or Amp.
A thread is that session persisted to Lore. When you share or upload a session, Lore stores the transcript, parses it, gives it a title, and makes it searchable and shareable. Thread IDs start with th_, and every thread has a URL like https://lore.link/thread/th_....
In short: a session is the thing on your machine; a thread is the thing in Lore.
What a thread contains
Beyond the raw transcript, each thread carries:
- The messages and tool calls from the session, broken into blocks.
- The file paths touched during the session, so threads are searchable by code area.
- The harness it came from and the originating session ID.
- A title (auto-generated, or one you set when sharing), the author, and timestamps.
- The skills and slash commands invoked during the session.
- A visibility setting (
private, workspace, or public). See Privacy and Visibility.
Decisions
Lore extracts decisions from your threads: the moments where something was asked, requested, decided, corrected, shared, or set as a requirement. Decisions get their own summaries, they're what Ask your threads most often cites when answering a question, and the threads feed can filter by decision kind. They're how "why did we do it this way?" stays answerable months later.
Projects
A project is a hand-curated collection of threads and docs around one piece of work. Add the relevant threads to a project to give teammates a single place to start; Lore generates a short summary of what the project covers and keeps it fresh as threads are added. Projects are workspace-scoped, can be archived when the work ships, and are listable from the CLI with lore projects list.
Skills and the skills library
A skill is a reusable set of instructions your coding agent can invoke, like a slash command or a saved workflow. Skills are where a team's working knowledge lives: the prompts, conventions, and procedures you want every agent session to follow.
The skills library is your workspace's shared catalog of skills. From the Skills page (on the web or in the desktop app) you can publish a skill from your machine to the library or install a team skill locally; the CLI mirrors this with lore skills list, lore skills sync, and lore skills status. Threads also record which skills a session invoked, so you can see how a skill performs in real work.
Components
Lore is made up of a few components:
- A macOS desktop app that browses Lore in its own window, captures your coding-agent sessions in the background, and installs the plugin into your agents automatically.
- A plugin for Claude Code and Cowork that lets you share and read threads without leaving your session.
- A CLI for advanced workflows like forking and a scriptable interface to Lore's APIs.
- A web service for browsing your threads, managing sharing permissions, and hosting your team's skills library.
You don't need to install the plugin or the CLI yourself; the desktop app sets everything up.
Harnesses
A harness is the coding agent a session came from. Lore recognizes Claude Code, Cowork, and Amp, plus threads created directly in the Lore web UI. (Cowork sessions come from Cowork running inside Claude Desktop.) The harness is attributed at upload time so threads can be filtered and analyzed per agent.
Workspaces
A workspace is your team in Lore, keyed by a verified email domain. Workspace IDs start with org_. Anyone who signs up with the same company email domain is automatically added to the same workspace, with no manual invitations, and workspace-visibility threads are shared across everyone on the domain.
You can belong to more than one workspace and switch between them in the web UI. Public email domains (gmail.com, outlook.com, and the like) are excluded from auto-grouping, so personal-email signups don't get pooled into a shared workspace. See Privacy and Visibility for how workspace membership drives default visibility.