Tailwind Labs said 75% of its engineering team had lost their jobs, describing the cuts as a consequence of artificial intelligence’s severe effect on the business. The disclosure appeared in a GitHub discussion after a contributor proposed adding a text-only version of Tailwind CSS documentation for use by large language models.
The proposed pull request would have created an `/llms.txt` endpoint by combining documentation pages into a format optimized for machine consumption. A Tailwind representative posting through the @adamwathan account closed the request, saying the company could not prioritize work that did not immediately help pay its bills. The response argued that making documentation easier for AI systems to consume could further reduce visits to Tailwind’s own documentation, where users learn about its commercial products.
That decision prompted criticism from participants who contended that easier automated access could make Tailwind more useful and expand the pool of potential customers. One participant also questioned whether the rejection was connected to material offered through Tailwind sponsorship. The Tailwind account rejected that suggestion, saying its sponsored AGENTS.md material was a short file expressing personal practices rather than a substitute for the full documentation.
In explaining the company’s position, the Tailwind account said documentation traffic had fallen about 40% from early 2023 even though the framework was more popular than ever. It also said revenue was down close to 80%. The account stated that the layoffs had occurred the previous day and that remaining time needed to go toward making the business sustainable and ensuring continuing employees received their monthly pay.
The comments did not reject LLM-friendly documentation permanently. The Tailwind representative said the feature had value and expressed interest in finding a way to provide it without worsening the company’s commercial problem. For the moment, however, the pull request was closed because that business model question had not been solved.
The GitHub exchange provides a direct account from the project side, but it does not include payroll records, financial statements or comments from the employees who lost their jobs. The supplied evidence also does not specify the team’s size before or after the cuts, the roles affected or the terms offered to departing staff.
What the discussion does show is a sharp conflict between two open-source goals: reducing friction for developers using AI tools and maintaining the traffic and product discovery that fund framework development. Tailwind’s representative warned that without a workable connection between adoption and revenue, the project could eventually become unmaintained. The closed proposal became the setting for a broader disclosure about the project’s financial strain.
