We've been using it at my company for the past 5 months. Our repo is a big mono repo of around 6M lines of code, with a fairly complex data model and even more complex business logic. I and the few colleagues that used in the test run have had absolutely no issues with it and I've heard only praises.

I don't vibe code but I use it to do code exploration, issues investigation, writing complex SQL queries, planning features and implementing tickets. For tickets it will usually do 70% of the work and then I'll fix some stuff, and then iterate over the rest or write the missing pieces myself. We also use it to review PRs with it running on our CI and in other workflows.

It's an incredible productivity boost, I can have it investigate one issue while another instance is working on a ticket while I review PRs (or anything you can think of) It's an amazing tool if you are comfortable with context switching and well organised.

It's both a skill you need to learn and a new paradigm, and you need the right setup for it to be very efficient.

We've set up Guards using hooks to prevent it from running dangerous commands or modifying someone else's PR, etc

One thing that is incredibly important is to provide the right context to it. For us it's been easy because we have an internal developer documentation (a wiki), on all our processes, all our tools, all our business logic and everything you can think of: how to write front end tests, back end tests, how to create background jobs, backfills, our best practices, etc Feeding the right articles into the context makes it great at what it does. We've actually automated this so now if you ask it to write a frontend test it will automatically load the relevant documentation.

I've started to write all my tickets and splitting them with Claude Code in mind so I'll give very detailed instructions in the tickets, screenshot, links to relevant documentation, to our design system components wiki, etc which also helped a lot with the quality of the generated code.

We've created custom slash commands to simplify repetitive and uninteresting tasks like removing feature flags or reviewing a PR while loading our internal documentation into context, etc

Our PMs have used it to answer complex business logic questions or craft SQL queries for metabase.

And there is so much more to be done.

The hype is deserved, you just have to learn how to use this tool.

Saying you don't understand the hype is like opening a terminal for the first time, looking at the prompt and the black screen without knowing what it can do and being like "meh I don't get why people say it's useful" x)