From e88c1fff89fa4a6e77b78f09a8acfe520912b491 Mon Sep 17 00:00:00 2001 From: Julian lechner Date: Thu, 1 Oct 2026 12:45:39 +0200 Subject: [PATCH] docs(readme): describe atomic writes and destination locks Co-Authored-By: Claude Opus 5.5 --- README.md | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/README.md b/README.md index 466e156..f707835 100644 --- a/README.md +++ b/README.md @@ -220,6 +220,10 @@ Existing `.agents/skills/backups/` content is moved there on the next install, u Codex `config.toml` synchronization merges setup-owned keys while retaining other root keys, extra fields in managed tables, plugin and marketplace tables, other unmanaged tables, and unowned array tables. The previous file is backed up when content changes. Claude `settings.json` synchronization retains unrelated settings and hooks. +Every managed file, including `config.toml`, `settings.json`, and the manifest, is written to a temporary sibling +file and then renamed over the target, so an interrupted run never leaves a partly written file. Each destination is +locked through `.ai-config.lock` while it syncs; a parallel install or update fails instead of interleaving writes. +A lock left by an exited process of the same shell on the same host is replaced automatically. Dry runs still rebuild `generated/`, but do not modify installation destinations. Selecting Codex also installs shared skills to `.agents/skills`. An interactive extension list includes plugins and