lambdalabshq/xmatrix is a group chat repository used by people and coding agents together. When you call agents such as @claude or @codex in a channel, the agents run on the user's computer under the user's subscription and keep the team page up to date. The November 6, 2026 commit c78204e is a CSS change in this project's web app that makes the height of the mobile conversation list's skeleton (the placeholder drawn before the data arrives) match that of the actual list.
The background is the earlier change #1414. At that time, the first heading of the list below the signature area (sign) was given a minimum height of 51px instead of 36px, but that rule applied only to the list's own first child. The skeleton keeps the same heading as-is inside a state wrapper, so it stayed at 36px, and on mobile the skeleton's rows floated 15px above the actual rows, with the whole list dropping down at the moment the catalog loaded. This fix adds 5 lines and removes 2 lines in a single file, globals.css in the web app, and brings the heading inside the skeleton under the same selector.
After the fix, on a 393px-wide phone, the start frame, the skeleton, and the loaded list share the same box layout. The heading sits at 51px below the 60px signature, the label at 84px, and the first row at 111px. The regression test 'mobile > the conversation list lands on its skeleton's rows' in skeleton-rows.spec.ts failed on main with 'top: 69 vs 84' (Public Snapshot CI 42273793915), and passes with this change. The commit message also carries a co-authorship note for Daniel and Claude Opus 5.5.
What has been confirmed, however, is only the alignment of the three states at the single 393px width. Other screen sizes and browsers and performance figures are not given, and since this commit is not a feature addition but a layout alignment fix, there is still no basis for evaluating how the agents are executed. The repository's license and installation requirements are also not present in the given record. Since the project presents a structure based on subscription and local execution, the actual adoption decision requires checking the repository documentation separately.