---
schema: 1
type: term
title: agents.md
description: >-
  A conventional markdown file that holds agent-facing instructions and project
  context in the repo, part of Compound Engineering's file-based knowledge layer
  so multi-agent, multi-model sessions start from a shared source of truth.
canonical: 'https://liquidgold.cc/channel/everyinc/explore/term/agents-md-a59b61d3efa2'
markdown: 'https://liquidgold.cc/channel/everyinc/explore/term/agents-md-a59b61d3efa2.md'
llms: null
parent: 'https://liquidgold.cc/channel/everyinc/llms.txt'
channel: everyinc
updated: '2026-10-23T22:12:35.346Z'
language: null
children: []
---


# agents.md

Canonical: https://liquidgold.cc/channel/everyinc/explore/term/agents-md-a59b61d3efa2

Parent: [Channel index](https://liquidgold.cc/channel/everyinc/llms.txt)

## Definition

A conventional markdown file that holds agent-facing instructions and project context in the repo, part of Compound Engineering's file-based knowledge layer so multi-agent, multi-model sessions start from a shared source of truth.

Compound Engineering is built on **file-based knowledge accumulation**: instead of keeping everything in chat history, project context lives in files the workflow reads and writes [^38395538]. The **agents.md** file sits in that layer as the agent-facing instruction file — the place where the guidance and context agents need to do their work is captured, so that multi-agent, multi-model sessions start from a shared source of truth rather than from scattered conversation.The v3.20 release discussion frames the whole system around a multi-model workflow, where different models handle planning, work, and review, and the goal is to **accumulate knowledge rather than burn tokens** [^38395538]. A file like agents.md is what makes that possible: because instructions are persisted in the repo, any model or skill in the loop — from core planning skills to newer ones like ce-pov and ce-explain — can consult the same accumulated project knowledge [^38395538].- agents.md belongs to Compound Engineering's file-based knowledge layer, holding agent-facing instructions and context.- Persisting that guidance in a file lets multi-agent, multi-model sessions share one source of truth.- Keeping agent guidance in the repo supports the compounding plan-work-review cycle instead of relying on chat history [^38395538].