@hn_61cb61
28 days ago
Same sort of stuff as the images on https://jules.google/ Looks nice enough but the pixels are not all the same size which is kinda upsetting.

Google Labs asynchronous coding agent that clones repos into a cloud VM, executes multi-step tasks, and returns diffs and PRs while you work elsewhere.
@hn_61cb61
28 days ago
Same sort of stuff as the images on https://jules.google/ Looks nice enough but the pixels are not all the same size which is kinda upsetting.
@hn_1c394a
30 days ago
At this point, I'm not sure whether Google is just full of people trolling the world, or people so smart and unworldly that they are trolling themselves. The website for Jules has a section for plans, yet it's neither mention the price, nor which actual plan they are talking about or where I can find those f**ing plans, not even a link. This is just ridiculous. Has Google already replaced all their people with AI?
@hn_920064
about 1 month ago
I have recently been working with Google Jules and it has a similar approach. It spins up VMs and goes through tasks given. It does not handle any infrastructure, so no hosting. It allows me to set multiple small tasks, come back and check, confirm and move forward to see a new branch on GitHub. I open a PR, do my checks (locally if I need to) and merge.
@hn_770ae4
about 1 month ago
Last week I tried Google's Jules coding agent and saw it requested broad GitHub OAuth permissions --essentially "full access to everything your account can do." When you authorize it, you're granting access to all your repositories. This is partly driven by developer convenience on the agent side, but it's also driven by GitHub OAuth flow. It should be easier to create a downscoped approval during authorization that still allows the app to request additional access later. It should be easy to let an agent submit an authorization request scoped to a specific repository, etc. Instead, I had to create a companion GitHub account (https://github.com/jmandel-via-jules) with explicit access only to the repositories and permissions I want Jules to touch. It's pretty inconvenient but I don't see another way to safely use these agents without potentially exposing everything. GitHub does endorse creating "machine users" as dedicated accounts for applications, which validates this approach, but it shouldn't be necessary for basic repository scoping. Please let me know if there is an easier way that Ip'm just missing.
@hn_5240c7
about 1 month ago
For work: only AI "on the side" used as interactive docs on whatever issue I'm working on. For hobby projects: All-in with extensive use of Google Jules to create/improve my stuff!