Having completed the 5th cycle of 2025, the team started working on the last cycle of the year, which will be shorter than usual (3 weeks). If you want to check out demos from the last cycle, have a look at this video 
. The team plans to work on the following pieces:
Productizing cache nodes
We’ve extracted cache into an independent server, which we currently run in several regions across the globe (with more added as needed), and we want to take a step further by turning it into a piece that you can host to ensure it runs as close to your environments as possible. Why, you might guess… Latency will matter a lot, especially in the world of the content-addressable protocol that Xcode 26’s cache builds upon. Therefore, it’s crucial that it runs as close as possible to where the binaries are needed to overcome the inefficiencies that physics might impose (i.e., latency). You’ll be able to run the server where you want, but obvious places are:
- Co-located with your CI runners such that the interaction between Xcode and the server happens through a local network.
- In the office or in a company’s network such that the connection from developers’ dev environments is as fast as possible.
- Co-located with AI agents’ infrastructure
. A lot of what’s happening in AI is still TBD, but AI coding environments are becoming a thing, and the cache server needs to run there.
The core Tuist server will continue to be responsible for the analytics, dashboard, and the source of truth for authenticating users and accounts, and authorizing the access to resources.
Did you notice the importance of environment & cache? Keep that in mind, because it’ll help you understand what we are planning for 2026 
Module binaries and registry packages through the cache nodes
So far the cache node only serves Xcode 26 cache CAS data, but we’d like to take that further and also serve Tuist module cache binaries and package registries. The node will act as a warmer and lower-latency piece of infrastructure to push the optimizations even further.
Test flakiness detection
In the 5th cycle we took the first step in the area of test analytics by adding test insights, which parse and report test results to the server, allowing you to see in a more accessible way all the data from your test runs across environments and time. In this cycle we want to take one step further and address another pressing issue that teams have and that’s strongly connected with slowdowns: flakiness.
We’d like teams and developers working with Swift and Xcode to have a place where they can see which tests are the most flaky and therefore would benefit from being fixed. Because if they are not, and flakiness keeps accumulating, it causes retries on PRs in the aim of making CI pass, which doesn’t fix the flakiness but ignores it and potentially makes it worse.
Previews improvements
We built previews a long time ago drawing inspiration from platforms like Vercel, Netlify, or Cloudflare, and Shopify’s Tophat. Previews are a solution for previewing people’s (or agents’) work directly as part of reviewing someone’s work by making it as easy as clicking a link, running a command, or launching the preview from a device.
Since its implementation, we haven’t done much work on it, but it’s time to get back to it. Some of our customers have started using it more actively and requested a couple of features that we believe can be extremely useful, so we want to focus on those.
We are going to add the concept of tracks as a tool to group previews. Tracks, for example, can represent a major feature that’s being implemented. Then, we’ll provide developers with an SDK that they can use at runtime in their debug builds to detect if there are newer versions in their track, or in the base track. They can then use that information to prompt the user to update.
Tuist keeps getting better and better and becoming the productivity platform that we always dreamed of building 
. Towards the end of the year we’ll share an update with all of you touching on how the year has gone, and what our plans are for 2026 (spoiler: we are very ambitious about what we want Tuist to become) 