Unclear The finding does not say what sets peerWritesLinks or when the container writes link bundles.
What
Cloud sessions copy your project between your machine and a remote container (an isolated machine running the session) using git, the version-control tool. This sync gained a way to receive link bundles, packages of commits, that the container itself wrote. Other changes came with it:
- Received links are stored under a
receivingnamespace asin/<generation>refs, checked for a two-parent shape, then moved into place. - When
peerWritesLinksis set, the sync prefers these received links as its starting point (its basis). - The seed start commit no longer counts as a basis.
- The side repository, a separate git copy used for syncing, now deletes stray
indexandsharedindexfiles. - A new worker-init log line reports
claude_code_version,warm_spareand a summary of tools. - A refusal caused by
.git/info/attributesnow explains that filter or macro rules are the problem.
Why
Changes made on the container side can now flow back through git sync. If sync refuses because of .git/info/attributes, the message now points at the filter or macro rules in that file.
Something disagreesSomething we can check disagrees with this entry, or the writer said they could not settle it.
The writer flagged doubt
The finding does not say what sets `peerWritesLinks` or when the container writes link bundles.