Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Jules, remote coding agent from Google Labs, announces API

jules.google

Post reply on HN
Print view View original

41–50 of 81 posts

Re: Jules, remote coding agent from Google Labs, announces API

#41

Post by block_dagger »

mattmanser wrote: post #39
onion2k wrote: post #21

Earlier quoted context omitted.

My experience with coding agents leads me to believe using something like this will end up being more noise and work than ROI I think that depends on how far out your horizon is. If you're only looking one task out, or maybe a few weeks out, then it's not worth investing the time yet. On the other hand, if you're looking at how your engineering team will work in 3 years time it's definitely worth starting to look at…

Why? In 3 years time this won't be how these tools work. So it feels like you're saying we should invest time in something that doesn't work and will be redundant in 6 months. Worse, your example is one that AI agents are notoriously bad at. Give them an error like that and they're more liable to break the existing functionality to fix it, after littering the code with tons of log statements. When most of the time th…

And in five years time all human engineers will be replaced. Why not just quit now?

Re: Jules, remote coding agent from Google Labs, announces API

#42

Post by mattmanser »

helsinki wrote: post #13

Would anyone at Google be willing to tell me how many people are working on this project? I’ve been building something functionally similar for my employer, but it’s a nights and weekends project with only one contributor (me).

Why would you build something for your employer in your personal time?

You're literally putting your own money in the shareholders pockets.

Re: Jules, remote coding agent from Google Labs, announces API

#43

Post by nl »

versteegen wrote: post #20
tecoholic wrote: post #9

Earlier quoted context omitted.

There is a free plan with 15 tasks/sessions. It doesn’t count tokens AFAIK. There would obviously be a runtime limit of some sorts for sure. But it’s not the same as API keys and token situation

The free tier is 15 tasks per day (of gemini-2.5-pro) which is EXTREMELY generous. I've had plenty of tasks run for 1-2 hours. I do think that after 1 or 2 hours it's told it needs to wrap up and just present what it's done; I couldn't get it to keep going longer than 2 hours. But Jules is very slow as it seems to be batch processing on spare capacity, so 15+ hours a day is not quite as absurd as it sounds. I haven't…

> I've had plenty of tasks run for 1-2 hours.

I think they throttle it - they note it is an asynchronous service

I agree that is is generally a pretty useful service.

Re: Jules, remote coding agent from Google Labs, announces API

#44

Post by gjvc »

andrethegiant wrote: post #25

I am so sick of these anthropomorphized names that have nothing to do with anything that we’re all supposed to remember now. Why are we giving products first names? The worst offender is probably Amazon Rufus. It’s all so dumb and I hate it. At least attempt to be clever and name it something that relates to the product itself. Even Google Wave, despite its shortcomings, made sense as a product name.

Claude is named after Claude Shannon. And Google Wave was the future we needed, even if we did not deserve it.

Re: Jules, remote coding agent from Google Labs, announces API

#45

Post by michaelt »

bonoboTP wrote: post #30
yoavm wrote: post #3

I have an old Django site I'm maintaining for a long-time customer of mine. They often want to make small changes - things that are only a few lines of code, but would take an hour to just spin up the system, remind myself how it works, commit, push, update the server and all that. Last week I've moved the whole infrastructure to Railway, and taught the customer to use Jules. They make their own PRs now, and Railway…

Do they still pay you the same amount?

I can't speak for the OP, but I have customers I still support, because they supported me many years ago when I was a teenager taking my first steps into industry.

Does it make me money? Barely a cent. But I can spare a hour or two a year for the guy who gave me a leg up and trusted a teenager who probably shouldn't have been trusted. And I like the feeling of having something I worked on still going strong 20+ years later, when so much of my later work has been thrown away by the endless corporate rewrite treadmill.

Re: Jules, remote coding agent from Google Labs, announces API

#46

Post by yoavm »

f311a wrote: post #38
yoavm wrote: post #26

Earlier quoted context omitted.

Jules has access to the codebase, not the database. It doesn't see any user data.

I was talking about potential security problems introduced in the code by LLMs. It's pretty easy to introduce something like IDOR when asking LLMs to write the code.

I review the PRs Jules makes just like I review any PR.

Re: Jules, remote coding agent from Google Labs, announces API

#47

Post by lupusreal »

andrethegiant wrote: post #25

I am so sick of these anthropomorphized names that have nothing to do with anything that we’re all supposed to remember now. Why are we giving products first names? The worst offender is probably Amazon Rufus. It’s all so dumb and I hate it. At least attempt to be clever and name it something that relates to the product itself. Even Google Wave, despite its shortcomings, made sense as a product name.

My friend, letting yourself be bothered by this is just pissing into the wind. Humans have been anthropomorphizing machines and other objects for as long as we've been making them, it's a fundamental aspect of human nature. Thousands upon thousands of ships and trains given human names. Tanks, guns, cars, anything that is at least moderately complex or that people find themselves relying on and forming relationships with. AIs have been getting human names since at least 1966 with Eliza, probably earlier, and certainly with many earlier examples in fiction.

There's no stopping it. Just roll with it.

Re: Jules, remote coding agent from Google Labs, announces API

#48

Post by danielbln »

block_dagger wrote: post #41
mattmanser wrote: post #39

Earlier quoted context omitted.

Why? In 3 years time this won't be how these tools work. So it feels like you're saying we should invest time in something that doesn't work and will be redundant in 6 months. Worse, your example is one that AI agents are notoriously bad at. Give them an error like that and they're more liable to break the existing functionality to fix it, after littering the code with tons of log statements. When most of the time th…

And in five years time all human engineers will be replaced. Why not just quit now?

Especially odd for someone working in IT. If I'd only learn what doesn't change in a few years I'd have to find new work.

Re: Jules, remote coding agent from Google Labs, announces API

#49

Post by kelvinjps10 »

michaelt wrote: post #45
bonoboTP wrote: post #30

Earlier quoted context omitted.

Do they still pay you the same amount?

I can't speak for the OP, but I have customers I still support, because they supported me many years ago when I was a teenager taking my first steps into industry. Does it make me money? Barely a cent. But I can spare a hour or two a year for the guy who gave me a leg up and trusted a teenager who probably shouldn't have been trusted. And I like the feeling of having something I worked on still going strong 20+ years…

I think that he meant in the sense that now AI it's making all the changes
Post reply on HN