Tusk (YC W24) - Make UI improvements with AI

@yash3 thanks for the questions! Tusk works well with popular frontend frameworks like React, Angular, and Vue.js. We've typically seen that B2B2C or consumer marketplace companies get the most mileage out of Tusk because these companies get a constant stream of customer-reported bugs and feature requests flowing into their sprints. Their PMs/engineers will offload these chores to Tusk so they can focus on higher-priority work.

@ken_jyi_lim thanks for asking! For our most active customers, Tusk is contributing 48.9% of all monthly merged PRs. Caveat here is that we're creating smaller PRs. Across ICP customers, we've seen that 45.5% of Tusk's PRs are merged without any human commits at all. The remainder consist of PRs where an engineer will checkout the branch and work off of it manually.

@rachpradhan thanks for the support Rach! We've been shipping a whole bunch since YC and leading up to this launch to get our agent reliability up as high as possible. Couldn't have done it without @sohil_kshirsagar and @jytan :)

@skolsuper appreciate the support James! That's a solid analogy. Bringing LLMs into the IDE has already changed so much of how we write code within just 3 years. We want to go up one level of abstraction when it comes to software development and make it so that writing plain English is the new way to write code.

@gab_rodriguez thanks for your support Gab! Definitely drew from my own experience when building Tusk haha. To answer your questions: 1. Tusk does best on codebases that use a typed language and in-line styling. The agent is language-agnostic and works well across popular frontend frameworks because we use an abstract semantic graph of the codebase that isn't syntax specific. With that said, we've tailored the agent for common FE languages like TypeScript, JavaScript, etc., and frameworks like React, Angular, and Vue. 2. Tusk does best on bug fixes that can be traced from the UI as well as product quality tasks like adding input fields, disabling buttons, and changing a variable name across multiple files.

@danielwchen thanks for the kind note Daniel! Please do try it out on your repo and let me know your thoughts. My line is always open at marcel@usetusk.ai.

@donald_wu2 thanks for the note, Donald! You have the right idea of automating away P3 bugs. As of now, we're still mostly limited to bugs that originate from the frontend. We're releasing a way for Tusk to do automated sanity tests on preview environments this month, which will enable us to debug more accurately. We're set on achieving the former, i.e., debug and understand problems without concrete solutions. It's a problem that's twofold: we need to 1) provide Tusk more sources of context, and 2) get Tusk to reason through that context better. Would be fair to say that we can always do better on both fronts. But that's the beauty of a hard problem I guess. :)

@ke5havrao Thanks for the support - totally agree. Instead of PM asking for a fix, they just need to ask for a green check! ✅

@yanika_magan thanks for the support Yanika! Great questions: 1. We will not use your source code to train our models nor will it be accessible to any of our other customers. Tusk stores non-readable embeddings of your files in your synced repos, not the files themselves. If requested, we can block specific directories from being synced such that Tusk never gets access to embeddings of files in those directories. When Tusk needs to view a full file, our agent fetches the file from the GitHub API at runtime without permanent storage on our servers. More details here: https://usetusk.ai/privacy 2. Yes, Tusk will reference existing components as much as possible when making UI changes. The agent is also able to reference a component library that lives in a separate repo. 3. Our Team Plan is most popular for teams midmarket and up. It's $495/month for 100 PRs per month, 5 synced repos, agent customization, integration with CI/CD, and more. We have a Product Hunt launch promo ("PHLAUNCH24") that gets you 50% off for your first 3 months. But these engineering leads can try Tusk out for free first!

@matthiasnannt thanks for your support Matti! It's been a joy to work with you and Johannes. Love the Formbricks UX by the way :)