Tuist acts as a bridge between LLMs and your development environment, allowing you to decide who to share your data with. This is just the start; we plan to introduce more tools and resources based on your feedback. You can turn Claude into your virtual platform team and ask questions like:
- What are all the static products in the graph?
- Can you onboard me on the project?
- What are the direct and transitive dependencies of a specific target?
videos.tuist.dev/w/hnwUYxkba... Introducing Tuist 4.46.1, now with an MCP server that seamlessly integrates with LLM-powered tools, enabling you to incorporate your projects into contextual discussions. 
Having a data structure to represent Xcode projects is not only useful for reducing merge conflicts, optimizing compilation and test runs, and providing visualization tools for teams, but it also serves as an excellent resource for LLMs to understand your development environment. LLMs and Claude's MCP protocol have unlocked a game-changing way for teams to engage with their projects: now, you can chat directly with your Xcode projects. 
yay love to hear that! how would you use it? still figuring out use cases and UX, but it's been fun for me at least
so @val.town now has a lot of database queries that we share throughout the application and i'm starting to miss activerecord. is everyone building their own 'model-like abstractions' or big shared query library, or is there a cool solution here? why i ask
huh, i guess it wasn't priced in
so is there a replacement for serde_yaml? i stopped paying attention and could do with some cursed whitespace file stuff
You can read our announcement blog post:
tuist.dev/blog/2025/0... 5. What’s next?
We’ve launched the Tuist Security Center security.tuist.dev/ where you can:
🔹 See how we protect your data
🔹 Request our SOC 2 report
Security is a journey. We’re just getting started. 🚀🔒
#SOC2 #Security #DevTools #SaaS 4. Lessons learned
• Start early—security is easier when built-in
• Automate compliance where possible
• Work with auditors, not against them
• Compliance ≠ security—focus on what actually makes you safer 3. How we did it
• Chose Vanta to automate compliance
• Found an auditor who gets SaaS security
• Embedded security into how we work (not just for the audit)
• Made our policies public → handbook.tuist.dev/ 2. What’s SOC 2 Type II?
A security standard proving we:
✅ Protect your data
✅ Follow strict access controls
✅ Enforce security best practices consistently over time
It’s not a one-time audit—it’s proof of ongoing security. 1. Why SOC 2?
Teams trust Tuist to manage sensitive Xcode projects. Instead of answering endless security questionnaires, we got SOC 2 Type II—so our security speaks for itself. Security isn’t just a checkbox for us—it’s part of how we build. Here’s why we did it, how we got there, and what we learned. 🧵👇 where do you keep your bash scripts rn?
nice! another option is to use a browserbase/steel/browserless from val town
docs.val.town/integrations...
docs.val.town/integrations...
docs.val.town/integrations... wrote about little personal tools i've been tinkering with, mostly on macos macwright.com/2025/04/03/p... 
KubeCon day 2! Swing by the PlanetScale booth for: - a live demo with our solutions engineers - custom printed stickers - our new IOPS hat Booth N712 near section N6.
New patches (6.2.5, 6.1.4, 6.0.14, 5.4.17, 4.5.12) have been released to address moderate security vulnerabilities in vite's dev server. We want to thank the reporters for stress-testing Vite and creating security advisories for these issues.
github.com/vitejs/vite/...