---
title: "Core concepts"
description: "A fast tour of the Trevize vocabulary — workspaces, sessions, automations, tasks, briefs, knowledge, and insights."
---

> Documentation Index
> Fetch the complete documentation index at: https://docs.trevize.dev/llms.txt
> Use this file to discover all available pages before exploring further.

# Core concepts

This is a quick orientation to the terms you'll see across Trevize. Each one has
a full page in [Concepts](/concepts) — this tour is just enough to get moving.

## Workspace

Your team's home. A **workspace** owns the GitHub repositories you connect, your
members and their roles, and your billing. Everything else — sessions,
automations, briefs, knowledge — lives inside a workspace and is scoped to it.

## Session

A **session** is a live, collaborative run where you and your teammates work with
an agent in real time. You send messages, the agent takes turns implementing your
requests, and everyone sees progress as it happens. Sessions are ideal when you
want to explore and steer as you go.

## Automation

An **automation** is an autonomous loop bound to a repository and a schedule
(for example, hourly or daily). When it triggers, it runs an agent against your
repo to make progress toward a goal you defined, opening pull requests without
anyone having to be present.

## Task & implementation

A **task** is a single unit of work. Under the hood it becomes an
**implementation** — one autonomous run that takes a prompt (and an optional
brief) from start to a pull request. Sessions, tasks, and automations all
ultimately produce implementations that land as PRs.

## Brief

A **brief** is a specification: a document describing what to build. You draft it,
refine it (optionally attaching GitHub repos or Linear issues for context),
approve it, and then start an implementation from it — so the agent works from a
clear, reviewed spec rather than a one-line prompt.

## Knowledge

**Knowledge** is the durable memory agents carry across runs. As agents work,
they record observations — decisions, bug fixes, discoveries — that are stored
and semantically searchable, so future runs start with relevant context instead
of relearning your codebase every time.

## Insights

**Insights** show Trevize's impact on your workspace: how many pull requests it
opens, what share of your team's PRs it authors, merge rates and times, and cost
over time — so you can see the value it's delivering.

## How they fit together

- A **workspace** contains your repositories, members, and everything below.
- A **brief** describes work; starting it creates an **implementation**.
- **Sessions** (live) and **automations** (autonomous) also create
  implementations.
- Every implementation runs an agent in a sandbox and opens a **pull request**.
- **Knowledge** accumulates across runs; **insights** summarize the results.

Ready to try it? Head to the [Quickstart](/get-started/quickstart).

Source: https://docs.trevize.dev/get-started/core-concepts/index.mdx