Nothing to try yetTier: how much it should matter to you
1Useful: my rating, 1 to 5
3Signal: worth watching, 1 to 5
Cloud SessionsArea: what it touches
In DevelopmentKind: in v2.1.228,
In DevelopmentSection of the release
The sync registry only attaches for container-sync git roots with an existing remote, so most sessions never reach it.
What
New code keeps one directory sync per session, shutting down an existing one before replacing it and releasing the oldest once a cap is reached. It only attaches when the session's git root resolves to container sync mode and a remote already exists, so most sessions never reach it.
Details
Each entry pairs a status publisher with a bounded backlog and a lane row client, keyed by session id.
Evidence
container_sync
Strings lifted out of the shipped bundle, so the claim above can be checked against them.
