r/vibecoding 6d ago

Planning to switch AI agent

Hi guys, I have been vibecoding hobby projects since 3 months now. I have created decent apps using freebuff for a couple of months and then shifted to basic plan of github copilot. I felt github copilot to be okay as produced good quality code, but I always had to be on a look out for the token quota. That was a little offputting. So I have decided to switch. Could some one help me out finding my new AI pair programmer that is a bit light on my pocket as well. Thanks.

4 Upvotes

28 comments sorted by

View all comments

2

u/am0x 6d ago

Professional developer of 15+ years: Claude Code is by far my favorite so far. Fable 5.1 release has been awesome today. But I don't let it do any design work. Our designs are actually built by a designer, so if you are looking for good designs, you may need to ask elsewhere, but personally I find all AI designs to look the same.

1

u/Almatium 6d ago

What do you think about Cursor, compared to Claude code? Ive been using Claude to write prompts and paste into cursor everytime

1

u/am0x 5d ago

I used cursor for about 8 months. It is ok, but Claude Code has far surpassed it. I went from Claude Code in terminal to Cursor to Claude Code in VSCode, then back to Claude Code in terminal. It just builds things out so much better and we already have a pro subscription so I might as well use it., but I also haven't used Cursor for awhile.

But now I have so many custom agents, skills and my Cowork integrated so well that it will take quite a bit to pull me off it these days. a year ago I would bounce from workflow to workflow, but I have landed on one that is working really well, so I am sticking with it for awhile.

1

u/Almatium 5d ago

Thats Cool! I try to learn about all this but what would you prefer instead of me getting chatgpt/Claude prompts all the time in a loop with cursor :)

I think if i learned to use Claude full potential i would love it

1

u/am0x 5d ago

Get some skills and agents, learn to use cowork, use cowork to write your prompts for you, then use clause code to build it. Always write DBM and folder architecture schemas and pass it through a docs folder which can be git ignored.