basicmachines-co-basic-memory/plugins/codex/schemas/codex-session.md

title, type, entity, version, schema, settings

title	type	entity	version	schema	settings
Codex Session	schema	CodexSession	1	summary? changed_file?(array) verification?(array) decision?(array) blocker?(array) next_step?(array) produced?(array) string, one-paragraph what happened in this Codex thread string, files created, edited, deleted, or inspected string, checks run and their result string, decisions surfaced or created during the thread string, unresolved blockers or failed approaches string, explicit cursor for the next Codex thread Entity, notes or artifacts created or updated	validation frontmatter warn project started ended? status?(enum, lifecycle of the checkpoint) cwd? codex_session_id? codex_turn_id? trigger? model? capture?(enum, how this checkpoint was produced) string, the Basic Memory project this session belongs to string, when the session began or checkpoint was created string, when the session was checkpointed open resumed closed string, working directory for the Codex thread string, Codex session identifier string, Codex turn identifier string, compaction trigger or deliberate checkpoint source string, active Codex model slug when known extractive deliberate summarized

Codex Session

A CodexSession note is a resumable engineering checkpoint. It captures the thread cursor: what changed, what was verified, what decisions matter, and what the next Codex thread should do first.

Codex sessions are found by structured recall: search_notes(metadata_filters={"type": "codex_session"}, after_date="7d").

What Goes In A CodexSession

• summary - what happened.
• changed_file - changed or inspected paths that matter to resume.
• verification - commands actually run and their outcome.
• decision - choices made or surfaced.
• blocker - open failures, constraints, or rejected approaches.
• next_step - the next concrete action.

Validation is warn so checkpointing never blocks the user's flow.