Tusk (YC W24)

Tusk is an AI agent that helps product teams complete UI changes from ticket to pull request. Automate away grunt work like minor bug fixes and copy changes to increase customer NPS without bothering your software engineers.Hey everybody!

@sohil_kshirsagar, @jytan and I are proud to launch Tusk, an AI agent that helps PMs and product engineers make UI improvements without needing to write code. 🐘 🎉

We launched our beta earlier this year with a select group of companies while we were going through the YC W24 batch. We’ve since battle-tested our AI across a variety of production tasks in mature, complex codebases.

It’s been incredibly exciting working on the frontier of what LLMs can do in the wild. We’ve put a lot of R&D cycles into getting LLMs to make the right changes in the right files. Our state-of-the-art agent refers to an abstract semantic graph of your codebase and learns from your past PRs and code reviews to generate high quality code.

💨 Tusk integrates with ticketing software like Jira, Linear, Notion, and GitHub so it takes one click to create a pull request for your UI tickets

🐛 Tusk comes with out-of-the-box Figma, Loom, Jam, and Bird Eats Bug integrations that pull context from external apps to generate high-quality code

🧑‍🔬 Our agent runs your CI checks on its code output and automatically iterates on a branch until it passes all your checks

🧠 Our agent addresses and remembers feedback from any code reviews left by human software engineers

We’re a firm believer that you shouldn’t need to bother your software engineers to fix padding on a modal or change the text of a header. Evidently we’re not alone. Tusk is now helping high-growth companies, backed by the likes of Y Combinator, Andreessen Horowitz, General Catalyst and Tiger Global, save $36K in engineering hours a year.

Try Tusk for free on your own repo today: https://usetusk.ai/

Feel free to ask your questions here or reach out to me at marcel@usetusk.ai. :)@sohil_kshirsagar @jytan @marceltan sounds like a lifesaver for product teams! automating those small but crucial ui tweaks can really free up devs for more impactful work. does tusk handle more complex ui changes like interactive elements or is it mainly for straightforward fixes?@sohil_kshirsagar @jytan @dash4u thanks for the kind words! Yes, we do support more complex UI changes like adding a net new component or changing the interaction of an element. The popular use case is fixing bugs since that has more of an impact on customer NPS.

If you go to https://usetusk.ai/ and click on "Customers" in the website header, you can see real examples of customer tickets that Tusk has created a merged PR for.@sohil_kshirsagar @jytan @marceltan Well done on the launch! Wishing you continued success and growth. How did you come up with the idea?@sohil_kshirsagar @jytan @kjosephabraham thanks for the support Joseph! We had the idea while working as a PM and product engineer at our previous jobs.

As a PM, I'd want to get UI polish tickets resolved before a launch or fix a minor bug to make a customer happy. But as Sohil and Jun Yu can attest, these types of tasks often take time away from already over-burdened engineers. We'd been experimenting with LLMs since GPT-3 (I was a PM at an AI company) and we saw a clear use case for having an agent automate away these engineering chores.I use cursor everyday for stuff like this. but It needs a lot of handholding for smaller tweaks, as the edge specific cases are not usually something general knowledge LLMs are gd at solving. But the LLM will often give some nice ideas that can be tweaked and made to work. I guess Tusk could be useful in the scenario as well. Maybe not 100% solves it, but gd enough for an engineer to take it further? Whats the experience here. I know the marketing will want to say its a one stop solution that solves it all 100%. but that's just not feasible with todays level of LLM's. Whats would the honest marketing say? 😬@sentry_co hey André, thanks for the question! Our unassisted PR merged rate for smaller tickets is 71% for codebases of a good fit. You're right that there are tasks where Tusk creates a draft PR that's 80% of the way there. An engineer can then checkout the branch and complete the rest.

In-IDE tools are great for writing code faster; we use them ourselves. Tusk is different in that we intentionally live outside of the IDE. We believe that humans shouldn't have to be in the loop when using LLMs for frontend grunt work. Our customers have Tusk running on their chore tickets in the background while they work on other tasks.Whoa this is pretty sweet! As a PM, I can see how this can take care some technical debt and small bugs, so engineering team can stay on top of the big rocks. Love how the AI agent actually does QA work and will tell you if an issue is too complex! Knowing the boundary is so important for AI.

I can see that over time, as the AI learns from the CR, and reading commits and notes, it will get smarter and fine tuned for the codebase.

What does the future look like for Tusk? Running Tusk proactively to discover issues and suggest fixes? I can see many use cases extended from taking care of simple tasks today.

Congrats on the launch @marceltan and team!@marceltan @tonyhanded Thank you Tony! 100% agree, uncertainty estimation is one of the biggest technical challenges when scaffolding reliable AI products. And yes, Tusk learns from its merged and closed PRs on your tickets.

Proactively discovering issues is not on our roadmap at the moment, but Tusk already has an “auto-triaging” feature, suggesting actionable tickets from your Linear/Jira/Notion board for you to assign to it! The idea is to make solving simple UI tickets from your growing backlog as seamlessly as possible.

Next up, we’re making strides to improve testing — writing unit tests alongside your test suite, automated sanity checks with preview environments so that you can be more confident that changes are correct and spend less time reviewing PRs. We’re also advancing Tusk’s codebase-understanding ability so we can better localize faults and solve them 🚀Very cool! We're using it at Formbricks (https://formbricks.com) for some of our smaller tickets :)@jobenjada It's been a pleasure working with you and Matti! Thanks for the support Team Formbricks :)