Live data from Hacker News

Jules, remote coding agent from Google Labs, announces API

jules.google

1–10 of 81 posts

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

#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 spins up an environment with the changes, so the customer can check it themselves. It works like 75% of the time, and when it doesn't, the customer see that it doesn't before it even reaches me. Only if they're happy with the changes, I step in to review the code and press merge. It's been a such a huge time saver so far.

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

#4
Do people trust these kinds of things to effectively work async and unsupervised?

My experience with coding agents leads me to believe using something like this will end up being more noise and work than ROI

I suppose it could be effectively the same loop I use in VS Code, but then why would I want an external tool over an integration?

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

#6
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…

How expensive are the API charges? Seems like it might be a bit too easy for a customer to rack up a big bill testing out minor changes if things weren't configured correctly.

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

#7
post #4

Do people trust these kinds of things to effectively work async and unsupervised? My experience with coding agents leads me to believe using something like this will end up being more noise and work than ROI I suppose it could be effectively the same loop I use in VS Code, but then why would I want an external tool over an integration?

VS Code is not a coding agent as much as it is code generation and completion

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

#8
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…

I hope they don't store any user data in their app. Trusting LLMs blindly is a bad idea.

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

#9
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…

How expensive are the API charges? Seems like it might be a bit too easy for a customer to rack up a big bill testing out minor changes if things weren't configured correctly.

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

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

#10
post #8
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…

I hope they don't store any user data in their app. Trusting LLMs blindly is a bad idea.

There is a human being (GP) reviewing the proposed code before merging. I wouldn't describe that as trusting the LLM blindly.
Post reply on HN