RE: More Adventures in AI SysAdmin fixing with Warp

You are viewing a single comment's thread from:

RE: More Adventures in AI SysAdmin fixing with Warp

brianoflondon in #v4vapp • 15 days ago

It wrote a shell script for me and I literally watched it pull my dev server Hive active key out of an .env file and happily paste it into a shell script.

I absolutely knew that this folder wasn't on github and I knew I'd never let this get out of my control, but when it got finished I pointed out to it that it had hard coded a crypto key into the .sh file! It apologized and set about fetching the key from the .env at run time like it should have done.

But you really have to know some basics before you just let this thing rip!

15 days ago in #v4vapp by brianoflondon

0.00 ALIVE

2 votes

Sort:

Trending

[-]

thecrazygm 15 days ago

I think that's the key people forget to mention with the whole "ai is going to take all the jobs" you almost have to have a human in the loop that at least has an understanding of what is going on. Else it ends up deleting production databases etc.

0.00 ALIVE

1 vote

[-]

brianoflondon 15 days ago

I can't imagine using this if I didn't understand what it was doing.

0.00 ALIVE

1 vote

[-]

theindianguy 15 days ago

Watching it hard code a secret feels like wizardry then a mini heart attack' . You handled it right by moving to read from env at run time, that's defnitely safer. Locking perms and scrubbing outputs before saving scripts helps keep surprises out.. Would a simple grep check for key patterns before execution fit your flow?

0.00 ALIVE