Skip to main content

Documentation Index

Fetch the complete documentation index at: https://mintlify.com/XxYouDeaDPunKxX/CSBP-Codex-Shared-Best-Practice/llms.txt

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

CSBP (Codex Shared Best Practice) is a lightweight protocol that solves a specific problem in long-lived Codex setups: recurring best practices either stay buried in chat history, get promoted too quickly into AGENTS.md, or worse — persist silently without any review. CSBP gives you a controlled middle layer where practices are explicit, reviewed, and operator-approved before they ever influence future behavior.

Quickstart

Install CSBP and wire it into your Codex setup in minutes.

Three-File System

Understand the entry point, runtime store, and compiler layers.

Authority Model

Learn how CSBP fits into the Codex authority hierarchy.

Practice Lifecycle

Follow a practice from raw observation to promoted runtime instruction.

​
Why CSBP?

Long-lived Codex sessions accumulate operational knowledge — patterns that keep working, mistakes that keep appearing, defaults that keep being rediscovered. Without a controlled persistence layer, this knowledge either disappears or bleeds into AGENTS.md without enough review. CSBP sits deliberately below the rest of the authority stack: 
operator instruction
  └── AGENTS.md
        └── local project instructions
              └── CSBP  ← here
Practices in CSBP are never invented silently, never promoted automatically, and never applied against higher-authority instructions. The operator decides what enters the runtime layer.

​
How it works

1

Install the three files

Copy CSBP-entry-point.txt, shared-best-practice.txt, and shared-best-practice-compiler.txt into your .codex/memories/ directory.
2

Wire the entry point into AGENTS.md

Add a bootstrap directive to your .codex/AGENTS.md so every fresh Codex session reads CSBP-entry-point.txt before using CSBP.
3

Run Codex normally

During normal work, Codex loads the entry point and the runtime practice file. Active practices apply when their applies_when condition matches the current work. No compiler, no formation logic.
4

Form practices intentionally

When a recurring pattern deserves to persist, ask Codex to evaluate it. The compiler layer activates, the candidate is normalized, and you approve or reject the proposal before anything enters the runtime file.

​
Key principles

No automatic capture

CSBP never writes itself. No background memory, no silent rule creation.

Operator approval required

Every practice promotion, revision, deprecation, and removal requires explicit operator sign-off.

Strict authority hierarchy

CSBP never overrides operator instructions, AGENTS.md, or local project guidance.

Build docs developers (and LLMs) love

Get started for freeTalk to us