👍

> A problem with this solution is that it disables the Google Toolbar (for those who are still using this no longer supported tool, especially for its "I fell lucky" button and its personalized buttons).

Thanks for the heads up, we have a fix in the pipeline!

Yoof that sounds like a nightmare to maintain. Typically every repo at Airbnb has some sort of platform team behind it, but the large repo runs into issues around getting reviewers and tooling around that which I think would be easier for more focused repos

Though in all likelihood I would probably clone before and just FS across repos when necessary because clones take a long time for us and our repos tend to be sufficiently large that migrations tend to be in a few repos

This is all in one repo, our TS / web repo. Most our repo groupings tend to be around language

There’s also Roo Code or Cline which are excellent for smaller migrations where you want more interactivity (or Cursor if you have that legally approved)

Happy to chat some more, I’ll clear what I am able to share with someone with a bigger wig

I think the impressive part is how unimpressive and ad hoc the setup is. You have an endpoint to talk to an LLM, write a js async function around it, you tell Claude to output XML, you have a fault-tolerant XML reader to get the output out of the response and you fs your way to glory

It’s not cheap though, because the most capable LLMs are pricey, but luckily our leadership was receptive to the cost benefit analysis of $10s of K’s for LLM costs vs keeping two people on the project for a year and a half

LLMs have been a godsend for us at Airbnb. I basically only write codemods these days just to gather data and context for the LLMs.

The problem with the LLM approach though is that you spend lots more time in verification vs a codemod where you can be 80% sure it’s correct.

My team is also looking for a manager if that's your thing

careers.airbnb.com/positions/64...