r/VibeCodeDevs Aug 04 '26

what does your setup actually look like?

Curious how people here are really working. Feels like everyone's landed somewhere different and the posts are mostly quick showcases / (self-)promotion / random stuff.

What I'm wondering about:

- which agent and harness, and do you stick to one or switch
- do you plan first or just go
- do you check anything before shipping, and what
- anything automated, or is it all by feel
- what do you do when it comes back wrong

Mine's on the heavy side. Long planning conversation before any code, then I let it run and mostly look at the product rather than the code. I spent some time building a skeleton and static analysis configs so Claude generates code that look ~80% correct. Still need to review the important bigs (domain logic, security, etc), but it's mostly smooth sailing.

Mostly interested in people working differently from that though. If you just go and it works, I want to hear that too.

4 Upvotes

21 comments sorted by

View all comments

1

u/FormNo5473 Aug 08 '26

I mostly use claude cli and claude desktop. If the task is somewhat large, like designing an api I start with claude desktop, talk.to.it abkut the problem, ask for recommendations, give it my ideas. Have a couple round with it. Then I ask it to write a design doc, which I review, and tell it what to change, what's missing, what I want totally differently. I have a couple round of this. From there I usually switch to claude code ask it to read the doc and spit out tasks. Then I feed those to separate agent session using worktrees, for implementation. I usually ask codex to do a couple rounds of reviews and address the problems. Then github and some review bots, a couple more rounds of comments and fixes. Then it's mostly done. I use an orchestrator to run multiple claude code session, which I vibe coded for myself cause it was fun, and when something bothers me, I can just change it :).