Tusk
Turn your production traffic into tests
Start new thread

Tusk (YC W24) - Make UI improvements with AI

by•
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.

Add a comment

Replies

Best
This is such an interesting launch, ! I love the idea of automating UI changes without taking up engineers' time. Quick question: how does Tusk handle edge cases or more complex UI changes that might not fit the usual patterns found in your codebase? Also, I'm curious about the learning process from past PRs—how quickly does it adapt to changes in coding standards or team preferences? Looking forward to seeing how Tusk evolves!
Maker
thanks Emma! For more complex UI changes that require new patterns, we recommend that people add more context to their ticket descriptions. Rule of thumb is to write the ticket as if you're giving it to a newly onboarded junior engineer. Re: speed of Tusk adapting to changes, it depends on how relevant previous PRs and code reviews are to the team's coding standards and preferences.
Wow this looks incredible! I've been using Cursor, but noticing it has a hard time maintaining the context of both the codebase and documentation simultaneously - are you able to link outside docs or give Tusk direction on what technologies you want it to work with/implement?
Maker
thanks Grant! We pull context from external links like Loom, Figma, Jam.dev, and Bird Eats Bug, as well as any public GitHub links. Supporting links to outside docs is on the roadmap. We recommend that users add the relevant snippet from the docs to their issue description in the meantime.
This looks really interesting, ! I’m curious about how Tusk handles edge cases in coding. Does the AI provide an opportunity for manual review before finalizing the PR, especially for complex UI changes? Would love to hear more about the decision-making process!
Maker
hey Alex, good question! Tusk currently does a self-review and runs your lint/build/test checks on a branch before creating a PR. If it determines that the change required is too complex, or encounters errors and can't address them, Tusk will create a draft PR or branch instead. In this event, the agent will also leave engineering advice on the ticket as a jumping-off point for the assigned engineer. Idea here is to fail gracefully.
Congrats on the launch Marcel!! Definitely going to try this out for Blue Whale when we have code to write!
Maker
thanks for your support from day one, Gabe! Definitely, will reach out to onboard you once you have software to build. :)
Excited to see how Tusk can streamline UI improvements and free up engineers for more impactful work. Great job!
Maker
thanks for the kind note, Ilya!
Congratulations on the launch! What kinds of companies benefit the most from Tusk? I think a lot of companies could benefit from using this.
Maker
thanks for the support Nikos! B2B2C or consumer marketplace companies at a late seed to Series C stage get the most mileage out of Tusk. We have been particularly successful with fintech and ERP companies.
A killer product with a killer team, congrats on the launch! Super curious where you see this heading for languages that fall somewhat out of the major distribution such as Swift?
Maker
thanks for the kind words, Vatsal! Candidly, optimizing for Swift is not a focus for Tusk right now. With that said, we are looking into incorporating external docs as context for Tusk if an issue requires it, which would boost the agent's ability to generate Swift.
Amazing Product. Well done on the launch! Wishing you continued success and growth. Just curious to know if y'all are planning to integrate Tusk with Bitbucket as well
Maker
thanks for the well wishes Ayush! No plans to integrate with Bitbucket in the short term but it is on our roadmap. You can migrate repos from Bitbucket to GitHub fairly easily though.
Hi Marcel and Team, congrats for the launch! I'm curious, can Tusk integrate with my existing component library when implementing UI changes? We are using Tailwind and thinking of Ant Design library in future too. Me and my FE team would love to learn more! - CC
Maker
thanks so much CC! Yes, Tusk is able to reuse existing components in your repo when generating code for UI changes. For any design patterns that are net new, it helps to specify which Tailwind UI or Ant Design component(s) you'd like to use. If you want to go one step further, we've seen users copy-and-paste boilerplate code snippets from those component libraries into their issue descriptions to make it even more prescriptive for Tusk.
Impressive 💡 Congrats on the launch guys!
First
Previous
•••
8910
Next