Git insufficient-permission-adding-object Git could not write a new object file because the object database denied the write.

Git writes objects through per-hash fan-out directories (the two-hex-digit prefixes). The failure names the database root because the denial happened while creating or opening one of those files — the object never reached disk, so the interrupted command leaves no half-written content in history.

The durable shape of the fix is ownership and sharing: aligning directory ownership with the accounts that commit, or declaring shared usage through core.sharedRepository so Git maintains group-writable permissions itself. Per-command workarounds, like repeated chown runs, decay as soon as the next mismatched account writes.