4l3x4f1sh3r
For now, you can simply re-run kait2en-install to fetch the latest updates.
You’re actually the first person we know of to have used the installer script. Has it been smooth sailing so far?
Happy to see you on Discord or Matrix, details are on the GitHub readme.
You can also join our Discord or Matrix server (details on GH) and we're more than happy to help you out!
While this brings much choice to the users, a lot of problems come with that approach, too. You can't easily rule out bugs, since every distro configuration is totally different. There are so many different repos and quirks needed to make things work, on I believe 16 different T2 Mac models? This can lead to frustration at the developer side: When we offered code changes and wanted them tested, we had to deal with not directly comparable results and a lot of distro-specific "noise".
Asahi has shown the value of concentrating development around a single reference platform. So we decided to do the same here and created KaiT2en. That is our clean reference platform based on Fedora. We rewrote the necessary t2linux kernel patches into DKMS modules. Yes, we're using the vanilla Fedora kernel. We've only included what's really necessary.
We've already fixed suspend, the shutdown path and the touchbar. We did a major overhaul to the audio driver. We included a brand new touch bar daemon and wrote an automatic installer to get this installed as smooth as possible.
We're working on open problems like better dGPU or Thunderbolt support.
Our long-term goal is to upstream as much code as possible. Until then, we want to give users and developers alike a smooth and consistent linux experience on T2 Macs.
Then for execution: Use plan mode. Let it always write a plan first, check it, correct it and only then allow it to implement it.
Try to break big tasks down in small substeps. As small as possible. Let it implement changes iteratively. Let it do a lot of local git commits. Both Codex and Claude Code use this as documentation as well.
Basically, treat it like a junior developer working under you.
Make sure appropriate tests are written for every code change.