Live data from Hacker News

We put a coding agent in a while loop

github.com

311–317 of 317 posts

Re: We put a coding agent in a while loop

#311
post #261

Earlier quoted context omitted.

I’ve literally asked Claude Code to look at and fix an issue on a cluster and it knows to use the cli utils.

Because Claude has that as a built-in tool. Try Claude on web and see how useless AI is without tools. And don't even get me start with giving AI your entire system in one tool, it's good for toying around only.

Why would I use Claude on web to do that? Why would I use the wrong tool for the job?

Re: We put a coding agent in a while loop

#312
post #169

hi simon, will the vue3 version of assistant ui be maintained? that would be awesome! p.s.: funny to meet again here. Last time we met was 2022 in Berlin! congrats to your journey so far!!

Hey, thank you! We are working on refactoring the codebase to support both React and Vue in the same repo, official support for Vue is still a few months out

great, looking forward to testing it out. hit me up if I can help in vue related ways.

Re: We put a coding agent in a while loop

#313
post #261

Earlier quoted context omitted.

Because Claude has that as a built-in tool. Try Claude on web and see how useless AI is without tools. And don't even get me start with giving AI your entire system in one tool, it's good for toying around only.

Why would I use Claude on web to do that? Why would I use the wrong tool for the job?

I am not saying you should. I am pointing out AI without tools (which I believe is what you think of when you refer to MCP) is useless.

Re: We put a coding agent in a while loop

#314

Earlier quoted context omitted.

Any pointers which forums do these people hang out?

I wish. He said that in the beginning he built a core group just with direct contacts but then he started a YouTube channel to drive traffic to the discord. He paid my buymeacoffee.com link because I showed him my windowfied.com tool I made to let you have dir commands on osx instead of ls. I hope you can meet him on a plane too.

Why would anyone want dir

Re: We put a coding agent in a while loop

#315

Earlier quoted context omitted.

What about a sales person interacting with an LLM that is already authz'd to spin up various cloud resources? I don't think that scenario is too far-fetched...

I imagine something along the lines of cloud platforms rolling out functionality that caters to vibe-coding crowd - one stop shop: you enter your prompts and it spins up your code along with the infra. I mean why wouldn’t they - seem like a goldmine.

Given how easy it is to spin up GCP resources with a text file, I'm surprised Gemini doesn't already offer this service. The prompt below gave me a 167-line file that uses Cloud Run, Cloud Built, Artifact Registry, Firestore, Maps, and IAM.

>I'm creating an app for dog walkers to optimize their routes. It should take all client locations and then look for dog-friendly cafes for the walker to get lunch and then find the best route. I'm vibe coding this on GCP. Please generate a Terraform file to allocate the necessary resources.

Re: We put a coding agent in a while loop

#316
post #136
post #81

Earlier quoted context omitted.

i spend a lot of time thinking about this. At humanlayer we have some OSS projects that are 99% written by AI, and a lot of it was written by AI under the supervision of developer(s) that are no longer at the company. Every now and then we find that there are gaps in our own understanding of the code/architecture that require getting out the old LSP and spelunking through call stacks. It's pretty rare though.

> It's pretty rare though. It will only get more common with time.

interesting - what makes you say that?

Re: We put a coding agent in a while loop

#317

Earlier quoted context omitted.

this is more about the service account than the runtime environment i think. you put your admin service account in docker the agent can still wreak havoc. Docker lets you hide the admin service account on your host FS from the agent.

Keeping the powerful credentials where the agent can't reach them does buy you a bit of safety. But I still think its a bit loose when compared with exposing an API to the model which can only do what you intend for that model to do.

sure fair enough. I guess i'm mostly being pragmatic here.

Plus i'm not convinced that generating "kubectl"...json..."get"...json..."pod"... is easier for most models than "bash"...json..."kubectl get pod"...

Post reply on HN