Getting Started

Project Structure

Learn more about the structure of a Lore project

Lore Library

You can access your Lore Library by clicking on the Library tab in the dashboard.

Your library is structured as follows

Projects

Your library is composed of Projects. A Project is always linked to a version control repository.

Currently, Lore only supports Git, and provides batteries included integrations for Github and Gitlab.

A Project allows Lore to tie into common Git events, where it can update it's Tasks according to actions taken in the repository.

Tasks

A Project is composed of several tasks. A Task is a high-level grouping category. Functionally, these operate like tags, and allow different related Events to be grouped together. Tasks are hierarchical, and can have parent / child relationships (task and subtask).

Events

Events are anything that happens in the codebase. They are divided into two subgroups

Actions

Actions are changes carried out against the codebase. These result in code changes

Decisions

Decisions are conceptual agreements made between the agent and the developer.

Threads

A Thread is a chain of Events. Functionally, these represent a continuous line of Action and Decision nodes. Threads also track their own progress, which can be Active | Abandoned | Complete A subagent instance can only be in one Thread at a time.

Usage

Normally, the Lore subagent takes care of all of this for you.

However, you can also create Threads, Actions, Decisions and Tasks manually.

lore thread new

See the cli command api for more info

Copyright © 2026