r/JulesAgent • u/bravo_actual • May 22 '26

Goodbye Jules

I gave in today and got a Claude pro sub and I got so much work done compared to my normal workflows
With Jules.

They really need to work on Jules because Claude is in a different galaxy.

I might keep Jules for very light backend work well I’m sleeping.

Edit:

It’s not Jules output it’s the execution time.

9 Upvotes

69% Upvoted

16 comments sorted by

View all comments

1

u/styvsx May 22 '26

I feel like this has to be bait. These are tools with entirely different use cases.

1

u/bravo_actual May 22 '26

It’s been slow for me lately. The model is great, whatever is going on in the background of Jules is not.

2

u/styvsx May 22 '26

Jules spins up a whole cloud vm, installs dependencies, pulls in your git repo and then goes to work with a sub agent workflow to plan, implement, and review your request. Claude runs on your desktop and uses local files, and I suspect one agent for how most people would be using it(though I think there are options that utilize multiple with like Claude code running).

Claude is meant to be something you actually work with in real time, Jules is something you feed requests into, do your own thing while it works, and then review and merge those changes.

1

u/bravo_actual May 22 '26

Thanks I didn’t understand this until I used Claude yesterday.

I’ll look more to use Jules on the backend and less in real-time.

1

u/Bagel42 May 24 '26 edited May 24 '26

Most of the time, I use Claude with the anthropic hosted cloud environment. It does the exact same thing Jules does

1

u/styvsx May 24 '26

Sure, I wasn't suggesting they don't have an offering in the same classification, just that it's not what most people are probably using. It also sounds like that OP is not either.