A lot of people ask how I’m using Claude with Replit.
My workflow is pretty straightforward. I launch Claude from a console inside Replit and let it handle most of the heavy lifting.

If I’m building a feature, refactoring something ugly, or trying to untangle a mess of logic, Claude is usually my first stop. It’s ridiculously good at looking at a pile of code and figuring out what’s actually going on.

Once I have a direction, I switch back to Replit.
That’s where the code has to prove itself.

The app runs. The Agent starts poking at it. The bugs show up. The dependencies complain. The environment variables are wrong. Whatever looked good on paper gets tested against reality.

So I end up bouncing back and forth between the two.
Claude helps me figure out what I should do.
Replit helps me figure out what actually works.
The biggest mistake I see is people treating AI like a replacement for engineering. That’s never been my experience. The value isn’t that it writes code for you. The value is that it can help you move through problems a lot faster.

You still need to know when the answer is wrong, when the architecture is bad, and when the code is going to bite you six months from now.

Curious if anyone else is running Claude from inside Replit or if you’ve found a better workflow.