Maintain a repository-level worklog.md as durable operational memory whenever an…

Brief

quasa0's agent worklog policy (2026-08-06) requires creating and maintaining a repository worklog.md as durable operational memory for any material agent work, preferring explicit repo instructions or a root-level worklog.md with "# Worklog." Agents must read the worklog before editing, preserve entries verbatim, update after each coherent unit of work, and record factual decisions, failures, verification, assumptions, and blockers; multi-repo changes need per-repo updates unless a parent worklog owns history.

Why it matters

Maintain a repository-level worklog.md as durable operational memory whenever an agent performs material work; prefer explicit repo instructions for name/location, otherwise create worklog.md at the repository root with a leading "# Worklog" header; read-only inspection or advice does not require creation or changes.

Key details

Operational rules: always read the worklog before starting material work and immediately before editing; keep newest entries on top; preserve existing entries verbatim and never overwrite another agent's fresh entry; update the worklog after each coherent unit of work and before handoff, commit, a long pause, or final response whenever project state changed; treat commits as completed-state snapshots and worklog.md as between-commit history.

Content and scope: record what changed, why, key decisions, failed attempts that redirected the work, verification results, runtime assumptions, and genuine remaining blockers; keep entries factual and concise and omit routine command output, speculation, secrets, and unrelated discussion; if multiple repositories are materially changed, update each repo's worklog unless a parent workspace worklog explicitly owns cross-repository history.

ask codex to save this in the global agents.md

In every project where an agent performs material work, maintain the project's own worklog.md as durable operational memory. Prefer explicit repository instructions for its name and location; otherwise use worklog.md at the repository root and create it with # Worklog if it is absent. Read-only inspection or advice alone does not require creating or changing a worklog.
Read the worklog before starting material work. Keep newest entries on top. Re-read it immediately before editing and merge with concurrent agent changes; preserve existing entries verbatim and never overwrite another agent's fresh entry.
Record what changed, why it changed, key decisions, failed attempts that redirected the work, verification results, runtime assumptions, and genuine remaining blockers. Keep entries factual and concise; omit routine command output, speculation, secrets, and unrelated discussion.
Treat commits as completed-state snapshots and worklog.md as between-commit history. Update it after each coherent unit of work and before handoff, commit, a long pause, or the final response whenever project state changed.
If multiple repositories are materially changed, update each repository's worklog unless a parent workspace worklog explicitly owns the cross-repository history.